Pilot, your dashboard assistant

Pilot is the chat bubble in the corner of every dashboard page. Ask it what's going on with your account — “any hot leads today?”, “what did the last caller say?” — or tell it to make a change. It reads your data, it makes edits, and it always tells you what it's about to change before it changes it.

Where Pilot lives

Pilot is on every page of the dashboard, signed in as you. It opens with a personal greeting — “Hi Dana, how can I help you today?” — and everything it can see or touch is scoped to your own organization. The same assistant also answers on this docs site. On phones it collapses to a compact button you can drag out of the way.

If your sign-in session ends — you signed out in another tab, say — Pilot drops to answering general product questions from its knowledge base only. Reload the dashboard to reconnect it to your account.

What Pilot can read

Ask about any of these and Pilot looks it up live, rather than guessing:

• Your account — plan, status, monthly usage against limits, active add-ons.
• Widgets — every brand you manage, its AI model, welcome message and counts.
• Integrations — what's connected and which tools each one has enabled.
• Leads — recent leads by stage and temperature, plus any follow-up emails drafted for them.
• Conversations — recent chats across your widgets, including human takeovers in progress.
• Knowledge — what's in your knowledge base, the content of any item, and the flagged gaps the bot couldn't answer.
• Agent tasks — what the agent is working on, what's scheduled, what failed and why.
• Personas, locations, phone numbers and the people directory — the setup behind your channels.
• Voice — recent calls and the transcript of any of them.
• The sales playbook — value props, objection handlers, pricing lines.
• Suppressions and outbound — who has opted out, and the audit of recent outbound email/SMS/calls.
• Live activity — whether anyone is waiting on a human right now.

Changes Pilot can make — confirm first

Pilot never takes a write action without naming what it's about to change. Tell it what you want, it states the exact change, you say yes, it does it. The changes it can make:

• Knowledge base — add, edit or delete an item. The bot starts using new knowledge immediately, which is exactly why Pilot confirms before saving.
• Integrations — turn an individual tool on or off on a connected integration (it won't connect or disconnect the integration itself).
• Widget settings — switch the AI model (only to models available on your own provider keys) or change the welcome message.
• Personas — update a persona's system prompt or name.
• Live conversations — take over a chat (the AI goes quiet and you speak for the business), send replies — Pilot confirms the exact message text, and it's auto-translated to the visitor's language — and hand the conversation back to the AI.
• Lead follow-ups — draft a follow-up email for a lead. Drafting never sends: the draft waits for your review on the Leads page.
• Suppressions — stop contacting a person (email, SMS, voice or all channels), or lift a suppression.
• Tasks and tidy-up — mark an agent task done or cancelled, dismiss a knowledge gap, mark your leads read.
• Voice settings — silence timeout, maximum call length, voice provider. These apply to every voice session, so Pilot spells that out first.
• Sales playbook — turn pasted notes or a positioning doc into structured playbook entries.

Finding the right page

Pilot doesn't have a tool for everything, and it knows it. Ask for something outside its reach and it says so, then points you to the right dashboard page — Integrations, Customize, Knowledge, and so on — instead of improvising. Two examples worth knowing:

• Asked to pin an AI model when your organization has no provider keys of its own, Pilot will tell you that adding a key under Settings → Workspace (the AI API keys card) is what unlocks choosing a model.
• Asked about pricing or invoices, it routes you to the billing portal rather than answering from memory.

Pilot on the Support page

Pilot also runs the guided help flow on the Support page (in the sidebar). Pick one of three starting points — Something's not working, I need help with a feature, or I have an idea — and Pilot asks a couple of questions, searches these docs, checks your recent errors and integration health, and either helps you on the spot or opens a support ticket with us for you. An Open a ticket anyway button stays visible the whole time — you can always escalate, even if Pilot thinks it solved the problem.

Troubleshooting