How it works
You name the job. It builds the team. The team does it.
Not one assistant answering questions. An orchestrator who decides who does what, agents who do it, and the systems you already run on underneath. Six steps, in order.
- 1
You tell us the job
Not a flowchart, and nothing for you to set up. The job in the words you would use with a new starter: answer the phone and the inbox, chase the suppliers who have not come back, fill tomorrow's gaps. We come back with the team we would build for it, and you change anything you want before we start.
We design the seats, the tools each one gets and the limits they work inside. You sign it off.
- 2
It reads your business
Your website, your policies, your past conversations. One live customer's support mailbox turned 8,994 past conversations into an approved knowledge base; a nine-page procedure document became 37 separate answers it can actually use.
From a live customer's Freshdesk mailbox. You approve what it learnt before any of it is used.
- 3
It practises before it meets a customer
It is put through real situations from your own history, with nothing connected to the outside world. It has to pass 27 kinds of check before it goes anywhere near a person, and you watch it play through them.
How it works. Nothing is sent to a real customer during practice.
- 4
It goes live in draft
Day one, everything waits for you. Every reply, every chase, every change to a booking sits in one queue with the reason it chose that answer and where it got its facts. You approve, edit, or hand it back.
Draft mode is the default, not an option you have to find.
- 5
You stop checking, one kind of job at a time
When the "is my order ready" replies have been right fifty times running, let those go on their own and keep checking the rest. Typically about 70% of replies are approved unedited in week one and about 90% by month three.
Typical, illustrative. Money always waits for a person unless you say otherwise. Tightening never needs anyone's permission.
- 6
You can stop it, and see everything it did
One button pauses the whole team. Set a monthly spending limit and it physically cannot go past it. Every job has one record you can download: what it was told, every step, what it asked permission for, and what it cost from the AI provider's own bill.
And when you correct it, it stays corrected.
You stay in charge
Full control
It runs on its own. These four things stay yours, and every one of them is a switch or a screen in the product.
- !Why it stoppedA refund is your call
- What you haveThe thread, his order, a draft
- →SuggestedCall him before 5pm
- 23:12Read Priya's message
- 23:13Used your payments page
- 23:16Asked you first
- 07:41Sent the reply
- Nothing goes outMid-conversation or not, it stops where it is.
- Nothing is lostDrafts, threads and part-finished jobs wait for you.
- One button starts it againIt picks up where it left off, knowing what it missed.
You decide when to stop checking, one kind of reply at a time
Start with everything past you. When the "is my phone ready" replies are always right, let those go out on their own and keep checking the rest. Refunds never stop waiting for you.
Typical approval rate, illustrative: about 70% of replies approved unedited in week 1, about 90% by month 3. The spending limit shown is an example. Our name for the queue is approvals; the limit is a spending cap.
Tell us what takes up your week. We will build you the team that does it.
Every team is built round the way you already work: your systems, your tone, your rules. Tell us what needs doing and we will show you what it would look like.