Overview
For work that takes more than an answer
Chat is for questions. Tasks is for work. If something would take several steps and a few minutes (going through a folder of new contracts and flagging anything unusual, for example), describe it on the Tasks page and let it run. Previous tasks stay in the list on the left so you can reopen them anytime.
A task works through your knowledge library the same way chat does, so it only ever sees what you already have access to. Nothing outside your library happens without asking you first.
- Describe the work
- Say what you want done in plain language and press Start.
- Watch every step
- Steps appear on the task card, numbered, and check off one by one as the work happens.
- Steer it mid-run
- Type while a task is working to narrow the scope, add a detail, or point it somewhere better.
- Approve before anything consequential
- A task pauses and asks before doing anything outside your knowledge library.
Tip
Quick Start
Hand over your first piece of work
Open Tasks
Open Tasks from the center action row (when Tasks is enabled for your org). Previous tasks sit in the list on the left.
Describe the outcome
Type the result you want and press Start.
Watch it work
Steps check off as they finish. If the task asks permission, answer it and the work carries on.
Starting a Task
Describe the outcome, not the steps
Type what you want done and press Start. Describe the result you want rather than the steps to get there.
- Works well
- "Flag anything in the new vendor contracts that conflicts with our standard terms." It names the result you want.
- Works less well
- A list of instructions to follow. It describes the steps instead of the result.
One task runs at a time in a thread. If you want two unrelated things done, start them from separate task pages.
Watching It Work
Every step, as it happens
Everything about a task lives on one card.
- Status badge
- Sits at the top of the card and tells you where the task stands right now.
- Numbered steps
- The steps sit underneath, checking off one by one as the work happens.
- Approval record
- Any time it needs your approval, that record stays right there in the same card.
- Final result
- Shows up at the bottom of the card when the task is done.
A step marked "Done after retries" means it eventually succeeded but had to try more than once, worth a look, because it usually points at something inconsistent in the underlying material.
Tip
Steering or Stopping It
Add a note while it runs
You can type while a task is working. Anything you send becomes a note to the task already in progress, not a second task. Use it to narrow the scope, add a detail you forgot, or point it somewhere better.
Important
Stop ends the task at the next step. Anything already finished stays finished.
When It Asks Permission
Nothing consequential happens without your yes
Before doing anything outside your knowledge library, a task pauses and asks. The card shows what it wants to do, quotes your own instruction back to you word for word, and explains why it is asking. The full detail is one click away if you want it.
- Answer yes
- It picks up exactly where it left off, and the decision is recorded against your name.
- Answer no
- It stops there, and the decision is recorded against your name.
- Acted on my behalf
- Every yes turns into something real: an email drafted, a call placed, and so on. Click Acted on my behalf in the header of the Tasks page for a panel listing every draft created and every action taken for you.
Tip
Closing the Tab
A task keeps going without you
Tasks run on our side, not in your browser. Close the tab, switch devices, or refresh mid-run. When you come back to the same task page, it reattaches and shows you everything that happened while you were away.
If a task says "interrupted, resuming", something on our side restarted. It picks itself back up automatically; work already finished is not repeated.
Tips & Best Practices
Getting better results
- Give it a finish line
- "Flag anything unusual and list it" ends somewhere. "Look into the contracts" does not.
- Retrying the same step?
- The material it needs is probably missing or unreadable. Adding the right document is usually faster than rewording the request.
- Add what is missing first
- Tasks only know what your library knows. If the answer depends on something nobody has uploaded, add it first.