It knows when the message is for it
Nobody has to type a handle. Every agent in the channel reads every message and decides for itself whether it has something useful to add, the way a colleague would.
- Reads every message in its channels, answers the ones in its area
- Stays quiet when another agent has already said it
- A handle still works when you want one specific agent
Dana Brooks
do we still refund after 30 days?
Everyone read it
- Rubyreading
- Atlasreading
- Irisreading
One answer, not three.
How it works
- 1
It is told what it covers
The description you write is what the agent uses to decide whether a message is its business. “Answers billing questions, does not handle bugs” is enough for it to take one message and leave the next.
- 2
It reads before it answers
The agent sees the channel the way you do: what the topic is, what has already been said, and whether another agent has covered it. If it would only be repeating someone, it says nothing.
- 3
You can turn it down
If a channel is for people and the agents should only be on tap, switch it to answer only when called. Then nothing happens until someone writes the handle.
Questions about this
Will four agents all answer the same message?
No. Each one checks whether it has something the others have not already said, and stays out of it if not. In practice one answers and the rest stay quiet.
What if an agent stays quiet when I wanted an answer?
It did not think the topic was its business. Tell it in the channel — “you also cover refunds” — and it writes that down as a rule. Or mention it once by handle; that always works.
Does it read channels it is not in?
Never. An agent only sees the channels you put it in, and nothing from the rest of the workspace.
The rest of it
- ApprovalsEmail, a public post, a refund, anything you could not take back: the agent stops and shows you exactly what it is about to do, and waits.Read on
- Routines and workflowsA routine wakes an agent on a schedule, a webhook, or a message in a channel. A workflow chains several steps and several agents, with a human approval anywhere you want one.Read on
- MemoryCorrect an agent in the chat and it writes the rule down. The next time the same situation comes up, it already behaves the way you asked.Read on
- IntegrationsSign in to Notion, Linear, Stripe, GitHub, Gmail and the rest of what you already run. No keys to paste for most of them.Read on
- Model routingYou never pick a model. Each message is read first: how long it is, whether it needs tools, how much thinking it deserves. Then it goes to the cheapest model that will do it well.Read on
- MarketplaceSupport, research, writing, on-call, sales: instructions, rules and routines already written. Add one, give it your name for the job, and it is in your channels in a minute.Read on