Skip to content

Customizing Your Assistant

The call path — assistants run in the highlighted hop

Assistants run in the highlighted hop: Parrot Cloud — the same call engine, whatever board or phone is on the other end.

The assistant is the recipe your device follows on a call: what it's trying to accomplish, how it sounds, and which AI vendor runs the voice. Your device is bound to an assistant during initialization, so customizing is optional.

Choose or create an assistant

Open Assistants to see your account's assistants, search them or filter by AI provider. Initializing a device selects an existing assistant from your account or creates one ready for use. Reconnecting or reflashing the device preserves your selection and edits.

Every assistant is editable. Duplicate one from the editor's ⋯ menu for an independent copy, start with a Blank assistant, or choose Build with AI to draft one through chat and apply the parts you accept. The History tab lets you restore a previous saved version.

Choose the assistant a line should use on its device page. Web Phone temporarily uses your browser microphone and speaker while retaining that selection; switching back to AI resumes it. You can delete an assistant after choosing another for each device that still uses it, including devices currently in Web Phone mode.

The editor

The assistant editor: prompt with variables, model & voice panel

The editor is tabbed — Prompt · Model · Tools · JSON · History — with the model & voice panel always on the right. What you'll actually touch, in rough order of impact:

  • Prompt (Prompt tab) — what the assistant is trying to do on a call, in your words. You can include variables like {{RESTAURANT_NAME}}: type {{NAME}} or add one on the Tools tab, and Insert variable puts one you've already defined at the cursor. Preview shows the prompt with variables filled in; after you save, it also shows the automatic adaptations Parrot makes for the chosen AI vendor.
  • Model & voice (right panel) — which AI vendor runs the call, which of its models, and the voice (hit ▶ to hear a short sample right in the browser). Providers are grouped like the AI providers page — the shared line and your working keys — with capability chips showing what each line can do. A vendor you can only use with your own key appears once you add that key. Switching providers resets the model/voice pickers to that vendor's options, so you can't save an invalid combination.
  • Identity & tuning (Model tab) — the assistant's name, its one-line Objective, the First message it speaks, and the tuning knobs the provider supports (temperature, who speaks first, reply language and input recognition language).
  • Turn-taking (Model tab) — how the vendor decides that the other side has finished speaking, and whether they can interrupt the assistant. Every knob is optional (blank = the vendor's default) and each vendor has its own set: Ultravox's turn endpoint delay / minimum turn / minimum interruption / speech threshold; OpenAI's server or semantic turn detection, eagerness, silence and threshold, and whether the caller can interrupt; Gemini's start/end-of-speech sensitivity, prefix padding and end-of-turn silence. Raise the end-of-turn delay when a phone menu or a slow speaker pauses mid-sentence and the assistant keeps jumping in.
  • Input variables (Tools tab) — every {{VARIABLE}} in the prompt gets a row here, and each needs a saved default (the editor won't save without one). Four fill themselves and never need a default: {{OBJECTIVE}} and {{OPENING_LINE}} come from the Objective and First message fields, and Parrot fills {{TODAY}} (the current local date, e.g. Sunday, September 13, 2026) and {{NOW}} (date and time) at call time. Every call also gets a "current local date and time" line automatically, so the assistant can resolve today, tomorrow or this Monday without you spelling out the date. Whoever places a call can override any of them for that one call — or leave them alone and get the defaults, which is also what happens on calls nobody dials, like auto-answered inbound (Making & receiving calls).
  • Output variables (Tools tab) — define fields (a confirmation number, a price, a yes/no) and a post-call pass extracts them from the transcript; they show up in the call report's "Extracted data" section (After the call). Mark a field req when every call should capture it: a missing one shows as not captured in the report. It does not change the AI's Goal met verdict.
  • Tools (Tools tab) — the actions the AI can take mid-call. The core set (pressing phone keys, reporting to you, asking you a question) is always on. Anything that ends or moves the call is opt-in per assistant, off unless you switch it on:
    • hangup_call — lets the assistant end the call itself. Off by default on purpose: without it your assistant says goodbye and waits for the other person to hang up, so it can never cut a call short. Turn it on for tasks that dial out and hit dead ends (voicemail, busy signals, wrong numbers) and should give up on their own.
    • handoff_to_user — moves the live call's audio from the AI to your phone so you take over the conversation.
  • Test it (the Test ▾ button) — Test call dials a real number through one of your online devices with this assistant, variables fillable for that one run. Try in browser skips the hardware entirely: a live microphone conversation with the assistant right in the tab — the fastest way to hear a change (it uses a real AI session, so it's billed like a call).
  • AI assist / AI Check — AI assist is the same Build-with-AI chat, available while editing ("make it more concise", "add an escalation rule"); AI Check saves your edits, then has an AI review what you changed in the prompt, objective and first message since the previous version. Its suggestions start ticked: untick any you don't want, then choose Apply selected & save.
Can I try an assistant without a board?

Yes — Test ▾ → Try in browser holds a live microphone conversation with the assistant right in the tab, no hardware involved. It uses a real AI session, so it's billed like a call.

Two behaviors worth knowing:

Edits apply to the next call

A call locks in the assistant's exact configuration at the moment it dials. Editing mid-call never changes a call already in progress — your change simply applies from the next call onward.

Every save is a version

The editor's History tab keeps every version — compare any older version with the current one, field by field, and restore an older one (you see exactly what will change before confirming; restoring adds a new version, history is never rewritten). Each call's record pins the version it actually ran as an @v… tag, which opens that exact version read-only.

Bringing your own AI vendor key (optional)

By default, calls run on Parrot's shared vendor accounts, billed through your Parrot credits. Register your own vendor key on the AI providers page and point an assistant at it — from then on that assistant's AI usage is billed by your vendor directly. Check Billing for the applicable Parrot charges. The provider picker in this editor mirrors that page: one group per vendor, holding the shared line and your keys.

Where this fits

An assistant defines how calls go. To let your own AI agent decide when they happen and supervise them live, continue to Connect your AI agent (MCP).