Tasks
Respond to questions, decisions, and follow-up requests without losing their context.
A task is a durable request for a person to respond or follow up. It keeps the request, relevant context, and response together, even when the conversation that created it has moved on.
Tasks and threads
A thread holds the ongoing conversation with the agent. A task holds a specific request that needs attention. Tasks belong to a project and can link back to the thread or automation that created them.
Review a task
Read the description and any attached references before responding. A task can include questions, a requested response, an assignee, and comments from people or agents. Use that context to understand what is needed and who is responsible.
For example, an agent preparing a customer update can create a task asking you to confirm the delivery date. The task preserves the question and your answer alongside the work that prompted it.
Resolve a task
Provide the requested answer or result. Tasks track whether they are pending, completed, or canceled. Comments let you add context while the request is being resolved.
When a thread is waiting on a task-backed question, submitting the answer lets that work continue with your response. Other tasks can record follow-up work without blocking a thread.
Decisions and permissions
Tasks can collect human judgment, including a decision about a proposed action. Describe the action and the evidence clearly so the person knows what they are deciding.