You don't fill in forms to build an agent team — you explain the job in the Builder chat, and the assistant designs the agents, writes their prompts and wires their tools. Here's how to get the best out of the conversation.
Propose, confirm, change
The Builder starts by asking a few short discovery questions — usually with pill options to tap, plus an Other box when none of them fit. Then it proposes a plan in plain language: what each agent will do and what a caller will experience. It may offer one or two extras it thinks you'd want, always as options — it never adds anything silently.
Once a team exists, every change the Builder wants to make follows the same rhythm: it proposes, you confirm — apply everything, pick the parts you want, or Not now. Changes you ask for directly are simply applied; it won't ask you to confirm your own instruction twice.
What a good description looks like
Three things give the Builder what it needs:
- The job. "Answer our phones, take booking requests, and capture a message when we can't help."
- The callers. Who rings you, what they usually want, and how they'd like to be spoken to.
- The outcomes. Where captured details should land, who should hear about calls afterwards, and what happens when the agent can't help.
You don't need all three up front — the Builder will ask about whatever you leave out. Vague is fine to start: "a receptionist for a dental practice" is enough to begin a useful conversation.
Panels appear when approval is needed
Some steps need a real decision from an organisation admin, so the Builder never does them by stealth. When the design calls for one, a setup panel appears in the chat — one at a time, never while the assistant is mid-thought:
- Connect inbound calls — point a phone number or SIP registration at the team.
- Set up calendar booking — connect a calendar and set the booking rules.
- Enable team email — let the team email call summaries to your verified members.
- Enable integration tools — approve exactly which Workspace tools the agents may use.
Every panel can be skipped with Not now — the assistant is told and won't re-offer unless you ask. A status row below the chat keeps a Set up button handy for anything you skipped. Members without admin rights see a note asking an admin to open the page instead.
If the chat disconnects
The connection pill above the chat shows connected, reconnecting or disconnected. Dropped connections reconnect automatically, anything you type during a wobble is queued and sent when the link returns, and the whole conversation survives navigating away and coming back. If a turn fails outright you get a clear notice and a one-tap Try again.
When the plan looks right, don't polish it in theory — run a test call. The Builder hears the result and fixing what you actually heard beats guessing every time.