Copilot (Human-in-the-loop)
A customer asks a billing question your agent can't quite answer, and a person needs to step in, but that person could use a quick answer to what the customer just asked. That's what Copilot is for: someone on your team talks to the customer on the phone, while the AI listens silently and puts answers, drawn from your agent's knowledge, on the operator's screen. The AI never speaks to the customer.
This page is for admins setting up copilot calls and for operators learning what Copilot does during a call. By the end you'll know how calls reach your team, what the AI does while they talk, and what's saved afterwards.
How it works
Copilot calls happen on the Conversations page. There are three ways in:
| Call | How it starts |
|---|---|
| Outbound | An operator clicks + New (or Call under Reach out on a conversation), chooses Phone call → Copilot, picks the agent, and dials the customer. The call goes out from that agent's own phone number. |
| Inbound, team first | When an agent's Operator node is set so the team answers first, calls to it ring the operators it lists who are online (they clicked Go online in Conversations). If nobody on the team is online, the AI voice answers. |
| Handed over by the AI | The AI hands a call off to your team. The operator's screen shows AI is handing you a call; see Contact Center. |
During the call:
- The operator and the customer talk normally. The operator hears the customer through the browser, so headphones are recommended.
- The AI transcribes both sides of the call, labelling who said what.
- When the customer asks something, the AI works out an answer and shows it to the operator as a card.
- The operator can also ask the AI their own questions, typed or dictated, without the customer hearing.
The AI answers as your agent would: it uses the persona, knowledge base, and integrations of the agent on the call — and if the call was passed to a different AI agent, it follows that agent. So the operator gets the same grounded answers your AI agent would give, framed as short points to read or say.
What the operator sees
The live call panel and the Copilot view are described step by step on the Conversations page. In short:
- Call controls: a call status (
Connecting…,Calling…,Live · MM:SS, or the outcome if it didn't connect), Mute, Hold (plays a hold tone and mutes the operator), Transfer to a colleague, a phone number or another AI agent, Hand back to AI on a call the AI handed over, and End. See The live call panel. - AI assist controls: turn the AI on or off, choose how long its answers are (Sharp, Short, Medium, or Detailed), switch tables and charts on or off, and pick the Language the operator reads the customer's question and the answer in, or Mirror the customer's language. With no language picked, answers come in the language of the customer's latest question. Small talk such as "ok" or "hello" doesn't produce an answer card.
- AI answers: one card per customer question, showing the question, the answer as Key points, and a 📋 Copy button, plus the knowledge-base articles used.
- Ask the AI: a box for the operator's own questions during the call, with Hold to talk dictation.
See Copilot view for the details and a screenshot.
The starting values for the AI assist controls (whether suggestions are on, the suggestion length, rich cards, and the copilot language) are set on the Copilot tab of the agent's Operator node, and each operator can change them during a call.
If the AI assist stops working mid-call, the call carries on and the panel shows "AI assist unavailable". The phone call never depends on the AI.
Worked example: Asha takes a billing call
Setup: Asha is an operator at Acme Support. The Acme Support agent has a knowledge base of billing policies and an Operator node that lists Asha on its Team, with the team answering first and suggestions on.
Action: Asha opens Conversations and clicks Go online (she's the operator automatically, as the signed-in user). When Priya calls about being charged twice, Asha's screen shows Incoming call, and she clicks Answer. Priya asks, "Why was I charged twice this month?" A card appears with the question and the key points from the billing policy: a failed payment retry can cause a duplicate charge, and it's refunded automatically within five working days.
Result: Asha explains the cause and the refund in under three minutes, then clicks End. The whole call is in the conversation's transcript, and the conversation is scored when it closes.
What just happened: the AI heard Priya's question, answered it as the Acme Support agent would, from the same knowledge base, and showed Asha the answer, while Priya only ever heard Asha.
Routing calls to your team
Who takes an agent's calls is set on its Operator node in Build → Agents. The full reference is on Operator and Contact Center. In short:
- Team lists the operators who take this agent's calls. Only people listed there are ever rung.
- Routing → Who answers a new phone call? is The AI (the default; nobody is rung when a call arrives) or The team (the AI assists), with a Ring style (one at a time longest idle first, one at a time in the order listed, or everyone at once), a ring time (5–120 seconds, default 30) and an optional skill.
- Copilot → Operators may start outbound calls with this agent lets operators dial out for this agent (on by default).
When a call comes in to an agent whose team answers first, Perfox checks whether anyone it lists is online right now:
- If someone is, the AI voice doesn't answer. The caller hears the agent's Waiting for operator sound while the team is rung by the ring style. The first to answer joins the call, and the AI assists them.
- If nobody is online, the AI voice answers straight away, so an unstaffed line behaves like a normal AI agent.
- If they're rung but nobody picks up in time, the call ends, and supervisors who asked to hear about unanswered hand-offs are alerted.
Who counts as available. An operator is available while they're online in Conversations (Go online), for every agent whose Operator node lists them. They stop being available when they click Go offline or leave the page, and they aren't offered another call while one is ringing, while they're on a call, or during wrap-up. If your team uses its own operator console (see the Operator node's Operator app tab), that console reports availability for each operator's External ID; an External ID that no Operator node lists is refused.
What's saved
- The transcript. Every finished line of the call is saved to the conversation's transcript as it happens, labelled operator or customer, so the call reads like any other conversation. If the customer reads out a code to the operator — a one-time password or a PIN — it's stored masked. See The transcript.
- The AI's answers. The answers the AI gave, and the operator's own questions and answers, stay in the Copilot view as a history.
- The recording. Phone calls are recorded like any other voice call, with separate caller and operator tracks. See Recording.
- A post-call recap. When the call ends, the AI writes a short recap of the call: what happened, the recommended next step, the customer's sentiment, and any facts learned (such as names, amounts, or dates). It's saved with the conversation.
- The quality verdict. Like every conversation, the call is scored when it closes. See QA outcome verdict.
Usage. Transcribing a copilot call uses credits, like any voice call, and each AI answer is an agent turn. As a safety net, a copilot session that is somehow left running stops itself after 60 minutes.
Where to go next
- Conversations: where operators go online, dial out, and use the live call panel.
- Operator: every setting for routing an agent's calls to people.
- Contact Center and Operator console: hand-offs, queues, wrap-up and hand-back for your team.
- Cases: the ticket-queue view for following up after the call.