Making & Receiving Calls

This chapter covers the highlighted ends of the path: Parrot Cloud (where dials start and assistants run) and the phone call to the other party.
Your device is a real phone line, and calls can start three ways: you dial from the console, someone calls in, or your AI agent dials programmatically (covered in Connect your AI agent). However a call starts, it's handled the same from that point on — same assistant, same live controls, same record in History.
Calling apps
Any calling app on your phone — WhatsApp, Messenger, WeChat, Telegram, FaceTime, Microsoft Teams, Google Meet, Zoom, Discord and others — can work with Parrot when its call audio is routed over Bluetooth to Parrot App on Windows or an ESP32 board. Start the call in the app on your phone, then choose your paired PC or board as its audio output. The console's Place call dials a phone number; start app calls in the calling app on your phone.
Take over or end a call
You can take over from the AI whenever you want. Turn off Bluetooth on your phone, or switch call audio from Parrot to your phone or another Bluetooth headset. The AI no longer hears or speaks on the call, and you can continue the conversation yourself.
To end the call, hang up on your phone or use End call in the live monitor.
Your call is protected by TLS encryption. Read how your call is protected for details.
Dialing from the console
Open Devices and click your device. Place a call is on the device page itself.

- Number to call — the real phone number to dial.
- What should this call accomplish? — the goal for this one call, shown
when the device's assistant has an
{{OBJECTIVE}}slot. Otherwise the form shows the assistant's Saved instructions; to change them, edit the assistant. - If the device's assistant uses variables in its prompt (like
{{RESTAURANT_NAME}}— see Customizing your assistant), Call details shows one input per variable. Filling them is optional: every variable carries a saved default (the editor refuses to save an assistant without one), so an empty field just means "use the default" — type something to override it for this one call.
The call dials with the device's assistant and runs on its own — you don't need to stay on the page. Console-placed calls are capped at 5 minutes (your account's own duration ceiling, shown on Account, still applies underneath).
What you should see: the phone paired to your board dials, and the console jumps straight to the live monitor so you're watching the call from its first ring.
Why a dial can be refused
Parrot checks everything before dialing, so a doomed call never burns a real phone call. You'll see a clear reason: the device is offline, the phone's Bluetooth isn't connected, another call is already in progress, or your account is out of credit.
Web Phone — taking the call yourself
Your line can also be you, from the browser. Web Phone is on by default for new accounts. The You option is visible on the device page, while each device keeps its AI assistant selected until you choose You. Future calls on that line then use your browser microphone and speaker. If you previously turned Web Phone off, enable it again in Settings to show the option. Your saved on/off preference is retained across sign-ins and upgrades.
Using a Windows PC as the bridge: keep Parrot App running with the phone connected. Open the Console on another device, sign in to the same account and select the PC's line. Web Phone uses that browser's microphone and speaker; the Windows App provides the phone connection. The App's Web Phone notice lets you copy the Console link.
- Dial out with Place call as usual. The console opens the live monitor, asks for your microphone the first time, and you hear the line ring in your browser. When the other party picks up, you are on the call.
- Incoming calls show a banner on whatever console page you have open. It names the caller and the line; Answer takes you to the live monitor, where the call is taken, and Decline ends it. If you don't answer in the browser, the call keeps ringing on your phone as it always has. A board that answers every ring itself (the shipped setting) picks up first; the caller then hears nothing until you take the call.
- On the call, the bottom bar has Mute, Keypad (its digits are sent to the line as touch tones, for phone menus) and Hang up. The rail's Audio tab shows the caller's level and yours.
- Phone review on the bottom bar shows the caller, timer and round Mute · Keypad · Audio controls in the monitor's center panel. Navigation and call details stay available, and the panel follows your console theme. Phones open in this view automatically; Live monitor returns to the transcript.
- The call is recorded like any other and appears in History with your voice on the second track; there is no transcript or AI summary, because no AI listened.
- Metered time starts when the call is answered, not while it rings. The platform fee for Web Phone is currently 0, and it never uses AI credits. A call you place this way may last up to 30 minutes (your account's own ceiling still applies underneath), not the AI's 5.
What it needs: a browser with a working microphone (Chrome or Edge recommended, which can also pick the speaker), and the tab kept open for the whole call. Headphones avoid echo on a laptop. Only one browser can be the call's voice at a time; a second signed-in browser is told the call is already answered.
To use an AI for future calls, choose AI assistant. Your previous assistant remains selected; you can choose another whenever needed. A call already ringing or in progress keeps its mode. To turn off Web Phone in Settings, turn off its switch. Devices configured for Web Phone, including offline devices, resume their retained AI assistants. Other AI assistant choices stay as they are. Existing calls continue in their original mode; you can still answer or rejoin them. The You option disappears from device profiles until you enable Web Phone again.
Watching a call live
The live monitor (you land on it automatically after dialing; it's also a button on the device page) shows the transcript as it happens, with sound-level meters for both sides.

While the call runs you can:
- Listen in — audio starts automatically in the web console and Windows Parrot App, with each side's meter and a per-side mute. Use Mute both to silence local monitoring and Unmute both to hear it again. These controls do not mute or end the phone call. A browser may require a click anywhere on the page before audio can play.
- Steer — type an instruction to your assistant ("wrap it up", "ask about parking too") in the transparent input at the conversation's lower right. It stays open; the latest messages keep their space above it. The other party never hears it; the assistant folds it into the conversation. On AI vendors that support it, an urgency picker controls whether the instruction can interrupt the assistant mid-sentence or waits for a natural pause.
- End the call — hang up immediately.
The rail's Assistant tab shows what's running the call — the
assistant and its provider, model and voice, its tools and objective, and
the saved prompt the call started from (variables appear as {{NAME}}, not
the values you typed for this call) — handy when a call behaves
unexpectedly.
The monitor tabs are Audio, Connection, then Assistant. Audio holds local listening controls and Quality. Quality separates caller uplink (device → Parrot) from assistant downlink (Parrot → device). These measurements verify local capture and playback acceptance, not what the remote party heard. Missing measurements stay Unknown. The Connection tab groups readings by their role: Phone connection · Bluetooth holds the device link and the separate call audio channel; Cloud connection · Internet holds the Bridge ↔ Parrot connection and round-trip delay. A connected device link does not imply that the call audio channel is established. Mobile network · Cellular shows phone signal independently. In the ESP32 setup, Bluetooth connects the phone to the board and Bridge software relays it to Parrot; Windows uses the App's built-in Bridge. Device info identifies that software and its version. Bridge state appears when round-trip evidence is unavailable. The two Details charts show audio delivery and Bridge ↔ Parrot round-trip.
Receiving calls
The board answers every ring. The moment the phone rings — a cellular call or a VoIP call (WhatsApp, FaceTime, Messenger…) alike — the board picks up, and the device's assistant handles the call hands-free. There is nothing to configure and no decision window: pickup is immediate. The one exception is call waiting: a second call that rings while one is already going on is left for you.
On Parrot App for Windows, answering is a setting: turn on
Answer incoming calls automatically in the app's Bluetooth setup. It
starts off; while it's off, incoming calls ring until someone answers them —
you on the phone, or an agent with
answer_call.
Want a particular call for yourself? Take it — mid-call, right from the phone's call screen: open the audio picker (the speaker icon) and switch the audio to your handset. The assistant leaves the call the instant the audio does, and it never fights you for it (see Who's on the call — you or the assistant).
Who's on the call — you or the assistant
One rule decides where the assistant is: wherever the call's audio is. The board is one of the phone's audio outputs, like any headset — while a call's audio routes to the board, the assistant hears and speaks; while it routes to the handset or speaker, the call is entirely yours. The phone's call screen switches this at any moment, on any call — the audio picker (speaker icon) is the per-call control.
That covers calls you make or take yourself, too: if you dial on the phone or the call's audio lands on your handset, it's your conversation — and routing its audio to the board at any point puts the assistant on it, mid-call, tracked and recorded and billed like any Parrot call from the moment it joins. History still tells the kinds apart: a row shows who took the call live ("Parrot answered", "Parrot dialed", or "Your call") and — when the assistant was only on for part of a call — for how long (see After the call).
Three guarantees make the audio route safe to use as the control:
- Switching away is never fought. The board has no way to pull a call's audio back on its own — once you route the audio to your handset, it stays there until you route it back. Switching back hands the call to the assistant again.
- Disconnecting is never chased. If you disconnect the board in the phone's Bluetooth settings, it goes quiet — it doesn't redial the connection while you hold the call on the phone. Reconnect whenever you want it back.
- A reconnect doesn't steal the call. If the Bluetooth link blips and comes back mid-call, phones like to shove the call's audio at the freshly-reconnected device. If the audio wasn't the board's when the link dropped, the board refuses that push — the call stays on your handset, and your next deliberate route-to-board still works.
Each new call starts fresh: taking one call back from the assistant doesn't change who answers the next ring.
Troubleshooting
\"Place call\" is greyed out
The button stays grey until you type a number and the line is ready. The status at the top of the device page says what is missing — usually the bridge is offline or your phone isn't connected over Bluetooth. See Your devices. During a call the form is replaced by Current call.
The dial was refused
The console tells you why, and each reason is what it sounds like: the phone's Bluetooth isn't connected; another call is already in progress; or your account is out of credit.
The call connected but the AI never spoke
First: check where the phone is routing the call's audio. On the phone's call screen, the audio picker (speaker icon) must show your board, not handset or speaker — the assistant is only on the line while audio routes to the board (Who's on the call, and Your board & firmware). If the route is right, check the live monitor's audio meters: if the other side's meter moves but the assistant's doesn't, the AI session likely failed to start — the call report's Call health section will say so. Try once more; if it repeats, check the assistant's provider/model settings (Customizing your assistant).
Incoming calls never get answered
The board answers a ring only while it's actually on the line: the bridge must be running and the phone's Bluetooth connected. Check the device shows online in the console and that your phone shows the board connected (Your devices). A call that rings while the board is disconnected is a normal phone call — nothing picks it up for you. On Parrot App for Windows, also check that Answer incoming calls automatically is on.
Where this fits
When a call ends — however it started — its transcript, outcome, and report are waiting in Call history. That's next: After the call.