Describe what you want

There are no forms to fill in. The job starts in the Builder chat; the assistant designs the agents, writes their instructions and connects their tools.

Propose, confirm, change

The Builder starts with a few short discovery questions, usually with pill options plus an Other box. It then proposes a plan in plain language: what each agent will do and what a caller will experience. Once a team exists, the same rhythm governs every Builder-led change: the Builder proposes, and confirmation can apply everything, pick parts, or choose Not now. Direct requests are applied.

What a good description looks like

Three details give the Builder what it needs:

• The job. "Answer our phones, take booking requests, and capture a message when we cannot help."
• The callers. Who rings, what they usually want, and how they expect to be spoken to.
• The outcomes. Where captured details should land, and what happens when the agent cannot help.

None of it is needed at the start. The Builder asks about whatever is left out. "A receptionist for a dental practice" is enough to begin.

Outcomes become recorded goals

The outcomes agreed in discovery do not disappear when the design is saved. The Builder records them on each agent as its conversation goals: a short, tagged list in the agent's description of what a successful call achieves ("appointment booked and reference read back", "callback captured with name and number"). Each goal is marked must or should, and the list stays current as the design changes.

The goals are the team's definition of success. When a call is later tested or handed to troubleshooting, the diagnosis is scored against them, so success is measured against what was agreed, not guessed after the fact.

Panels appear when approval is needed

Some steps need a real decision from an organisation admin, so the Builder never does them without approval. When the design calls for one, a setup panel appears in the chat:

• 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 verified members.
• Enable integration tools: approve exactly which Workspace tools or MCP tools the agents may use.

Every panel can be skipped with Not now. A status row below the chat keeps a Set up button available for anything skipped. A panel that cannot proceed says why and links to the page that resolves it; approvals, once given, continue to apply.

If the chat disconnects

Dropped connections reconnect automatically. A pill above the chat shows the state, and anything typed meanwhile is queued and sent when the link returns. A failed turn gets a one-tap Try again.