polite.aiDocs
START

The product tour

A seven-stop walkthrough that ends with a working agent.

On a first visit to the dashboard, whichever screen opens first, a small card docks bottom-right and offers the tour. Show me around begins it; No thanks dismisses it.

A stop in progress: the ring around the real control, the stop card, and the YOUR FIRST AGENT checklist.

Seven stops to a working agent

The tour helps you build an agent in the same order as the Quickstart recommends:

  1. Knowledge: a look at what the agent already knows. The stop's copy reflects the crawl state: queued, in progress, pages read, or declined at signup. While a document is still missing, it highlights Add knowledge, offers to open that panel, and asks for information the website cannot give an agent: a policy, price list or staff manual (Website knowledge).
  2. New agent: press New agent and describe the job.
  3. Test agent: say hello on a browser test call. This stop has no callout; it ticks the checklist.
  4. Add number: buy a fresh number or add one from a trunk; either completes the stop. Pointing the number at the team happens back in the Builder (Connect a phone number).
  5. Deploy: press Go live on the draft bar (Drafts, versions & going live).
  6. Calls: open the row created by the first call (Finding calls).
  7. Inspect: open the call drawer's data pane, then use Fix with AI to send the evidence back to the Builder (Inspecting a call, Troubleshoot a call with AI).

How the tour advances

Each stop draws a ring around the real control and gently dims the rest of the screen. The stop's copy, including a step label like 1 / 7 · KNOWLEDGE, a progress bar and a Skip link, lives in a docked card at the bottom right, where it does not cover the control it is describing.

On a different screen, the callout attaches to the sidebar instead: Next stop: Numbering with Take me there →. Stops completed out of order are skipped over; the tour never asks for work to be redone.

Esc or Skip pauses rather than abandons the tour. It waits in Help.

How the tour ends

Closing the call drawer on stop 7 finishes the tour. A final docked card says That's the tour done and summarises what has been created: a working agent, live on a real number, with its first call on the record. Back to your team → returns to the Builder.

The last card: what the tour built, and the way back to the team.

Finish with a step still deferred and the card says that instead: which step is still waiting, and Finish that step → to go back to it. Got it puts the card away, and it does not come back. A finished tour remains available in Help from then on.

The YOUR FIRST AGENT checklist

While a tour is in progress or paused, a docked card tracks six milestones with a progress bar: Check what it knows, Describe the job, Say hello: test call, Connect a number, Deploy to callers, Listen back in Calls. It reflects reality, not tour order, and it is honest about skips: a step that was skipped is marked as skipped, not ticked, and remains an active to-do. Pressing it takes the tour back to that step. Once a revisited step is done, the tour returns to where it left off, or ends if everything else was already finished.

Hide: it waits in Help puts the card away; the Help menu's Getting-started checklist row, showing the n/6 count, brings it back.

First-visit hints

After a declined or finished tour, four screens teach themselves on first visit: Agents, Calls, Numbering and Knowledge each show one docked card with a short explainer and, usually, a button that performs the screen's first action. While a hint is showing, the topbar wears an amber FIRST VISIT · HINTS ON chip.

A hint clears on Got it, on using its button, or on doing the action anyway. Each hint shows once. The First-visit hints switch in the Help menu turns them off wholesale; switching back on shows only hints not yet seen.

Pausing, resuming and retaking

The ? button in the dashboard topbar is the tour's permanent home. Its Product tour row adapts: START · 7 STOPS before a first run, RESUME · n/7 while paused, and TAKE IT AGAIN after a finish.

Good to know:

Tour progress is saved to the user account, not the browser. A tour paused on one device resumes on another. It is also per person: every teammate gets their own first run.

Last updated 2026-08-26