polite.aiDocs
BUILD / The Builder

Describe what you want

The Builder designs from plain English — it proposes, the user confirms, and nothing changes without approval.

There are no forms to fill in. The job is explained in the Builder chat, and the assistant designs the agents, writes their prompts and wires 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, every change the Builder wants to make follows the same rhythm — it proposes, the user confirms: apply everything, pick parts, or Not now. Changes asked for directly are simply applied.

Questions dock into the composer; a tapped pill, a typed answer or a dictated one all work.

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, 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 can't help.

None of it is needed up front — the Builder asks about whatever is left out. "A receptionist for a dental practice" is enough to begin.

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:

  • 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 the agents may use.

Every panel can be skipped with Not now — a status row below the chat keeps a Set up button handy for anything skipped. A panel that can't proceed says why and links to the page that fixes it; approvals, once given, stick.

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 turn that fails outright gets a one-tap Try again.

Tip

When the plan looks right, the next step is not more polish — run a test call. The Builder hears the result, and fixing what was actually heard beats guessing.

Last updated 2026-08-17