Use Ask Kato

Ask Kato is the assistant inside your workspace. Use it to understand tasks, meetings, and records, prepare for a conversation, or draft the next step. Start with a specific item and a question you can check against your work. Before you begin: open the correct workspace and make sure the information you want to use exists there. Connect your calendar first if your question requires synced meetings. Connect Google Calendar.

Ask Kato in the product is separate from the assistant on this documentation site. The docs assistant helps you find instructions; the product assistant works with your workspace context.

Open Ask Kato

Select Ask Kato in a page header where it is available. A conversation panel opens beside the current page. To return to a conversation later, use Chats in the sidebar or Recent chats in the assistant header.

Send your first question

Start a conversation

Open Ask Kato. Select the + button, labeled New chat, when you want to start a separate topic instead of continuing the current conversation.

Add the item you mean

Type @ in the composer and search for a record, task, or person. Select the matching result to insert a mention. You can also use the mention control in the composer. Available results depend on the context and your access.

Ask a focused question

Try “What open tasks are linked to this project? Group them by status and include due dates.” Mention your project so “this project” is unambiguous.

Send and review

Press Enter to send. Use Shift + Enter for a new line. Read the response and open relevant records or tasks to check the names, dates, and status before using the answer.

Expected result: the answer discusses the selected project and the work available to the conversation. If Kato cannot find a detail, add the missing context or ask what information it needs.

Give the request a clear shape

Include the item, a time range, and the format you want back. The diagram below shows how to turn a broad request into one you can verify.

Using the Relio website project and its open tasks, draft an internal update
for this week. Use three sections: completed work, blockers, and next steps.
Include task names. If a due date is missing, say it is missing.

Replace Relio website with a record in your workspace. The company names in these examples are illustrative; the prompts do not connect to those companies.

Requests to try

Daily planning
Client update
Meeting preparation
Follow-up draft

What tasks need my attention today? Separate overdue work from work due
today, and include the project for each task when it is available.

Check the task dates and current statuses before changing your plan.

Summarize the open work for Relio this week. List blockers and missing
information separately. Keep the update under 150 words.

Mention the client’s record and verify the time range and linked work.

Use this project's context to draft five questions for our next review.
Focus on unresolved decisions and tasks waiting for client input.

Mention the project or meeting and check that the questions are still relevant.

Draft a short follow-up from this meeting. Separate decisions from actions,
include owners where recorded, and flag anything that still needs confirmation.

Review the meeting details before sharing the draft. A draft is not a sent email.

Know the conversation controls

Control	Use it to
New chat (+)	Start a separate conversation.
Recent chats	Reopen an existing conversation when history is available.
More options (⋮)	Open the full-page chat experience or Ask Kato settings.
Close (×)	Close the panel and return your attention to the page.
@ mention	Identify a supported workspace item in your request.
Copy response	Copy an answer for use elsewhere after reviewing it.

Refine an answer

Continue in the same conversation when the topic is unchanged. For example:

“Focus only on tasks still waiting for client input.”
“Use the due date on the project record.”
“Which details are missing from the information you found?”

If the underlying information is wrong, update the record or task too. A prompt can clarify your intent, but it cannot make an absent deadline reliable.

Check answers and proposed actions

Read the source details behind an answer when references are available. When a response includes a proposed change, review the target item and the new values before using its action controls. After a change, open the affected item to confirm the result. A generated list of tasks is not necessarily a saved task list. When you only want ideas, say so: “Suggest three follow-up tasks; do not create them yet.” For web research, respond to the permission request if Kato presents one. Connected sources and your settings determine which information is available.

Troubleshooting

The answer is about the wrong client or project.

Check the workspace, select the intended record with an @ mention, and restate the question. Start a new chat if the earlier conversation was about a different client.

An expected meeting or record is missing.

Confirm that you can open it yourself. For synced information, check the relevant connection in settings. Name or mention the item directly and narrow the date range.

I have reached my credit limit.

Check your plan and available credits. Free includes 100 personal credits each month; Pro includes 1,000 per person each month. See Billing and plans for details.

A response still does not help.

Use the response feedback control when available, or contact support. Include what you asked, what you expected, and the workspace or item link needed to investigate.

Explore Kato

Use Ask Kato

Open Ask Kato

Send your first question

Give the request a clear shape

Requests to try

Know the conversation controls

Refine an answer

Check answers and proposed actions

Troubleshooting

Keep going

After a meeting

Keep context connected

​Open Ask Kato

​Send your first question

​Give the request a clear shape

​Requests to try

​Know the conversation controls

​Refine an answer

​Check answers and proposed actions

​Troubleshooting

​Keep going

After a meeting

Keep context connected

Open Ask Kato

Send your first question

Give the request a clear shape

Requests to try

Know the conversation controls

Refine an answer

Check answers and proposed actions

Troubleshooting

Keep going