Sanaf is the one you talk to. Behind it is a team of agents, one per job, and every agent reports to Sanaf. This article explains how the team works and where you manage it.
Who is who
- Sanaf, the Chief of Staff. Created for you when the workspace is created. It is the only member of the team in Slack and Teams, and the one you mention or message.
- An agent. A member of the team with one job, such as the support inbox or the invoices. It has its own job description, its own apps and its own approval rules. An agent always reports to Sanaf; there is no agent working on its own.
Ask Sanaf, a team answers
When you ask Sanaf for something, it works out which agents it needs, hands each its part, waits for the results and brings you one answer in the same thread. If an agent needs a decision from a person, the question arrives in your thread, the same way Sanaf's own questions do.
If an agent is still working when Sanaf replies, Sanaf says so and posts the result into the thread when it lands. Nothing is dropped: every hand-off is recorded, and a check runs every couple of minutes to deliver any result that was slow to arrive.
The Orgs screen
Open Orgs in the left rail to see the team as a chart: Sanaf at the top and every agent under it. From here you can:
- Add agent: give it a name, pick its job from the list, and choose which of your connected apps it may use. It reports to Sanaf from the moment it exists.
- Propose a team: describe your business in a sentence and Sanaf suggests a team for it. Keep the agents you want.
- Open any agent to see what it has done, change its model, or set a monthly credit cap for it.
Talking to an agent directly
In the console Chat screen you can pick any agent and talk to it on its own. Slack and Teams always reach Sanaf, which hands the work out.
What it costs
Nothing per agent. Credits pay for work that gets done, so a team of eight agents that did nothing this month cost nothing this month. You can cap what any one agent may spend in a month on its overview page.