Operator (your people)
A customer calls Acme Support and asks for a person. The AI says "let me connect you", plays calm music, and rings Priya on the billing team. Priya picks up with the AI's notes already on her screen, and a team lead can listen in and whisper to her. Everything in that story — who is on the team, who answers, where the AI may hand off, who may supervise, and what Priya's copilot starts with — is set on one node: the Operator sub-node.
This page is for Asha, an admin at Acme Support. You'll walk away knowing how to add the Operator node, fill its four tabs, and what your team and your callers experience at runtime.
Prerequisites: you should be familiar with the AI Agent node and Canvas Basics before reading this.
What the Operator sub-node does
The Operator sub-node is an optional, 1:1 sub-node in the AI Agent cluster. It attaches to the AI Agent's amber Operator port and is stored with the agent.
It holds everything people do on this agent's conversations:
- Team — who works this agent's conversations: web operators, phone operators and AI operators (other AI agents).
- Routing — who answers a new phone call, whether and where the AI hands off, and what the caller hears while waiting.
- Supervision — who may supervise this agent's live conversations, with which actions, and when they are alerted.
- Copilot — what each operator's AI assistant starts with on a call, and whether operators may start outbound calls.
No Operator node, no hand-off
An agent hands off to a person or to another agent only when its Operator node sets up a hand-off. Without one, the AI handles every conversation itself and has no way to pass it on.
A new Operator node from the picker starts with the AI answering first and no hand-off — you switch on what you need.
To add it: open an agent in the Agent Builder (Build → Agents → open an agent), then either:
- click the + glyph on the AI Agent card's amber Operator port to open the node picker and choose Operator, or
- drag from the Operator port to empty canvas to add-and-connect in one gesture (see Drag-to-connect).
The node picker entry reads: "Operator — Your people on this agent — who answers, the hand-off to a person or another agent, supervision and the copilot."
The Operator port in the AI Agent cluster
The AI Agent card exposes seven typed ports along its bottom edge, each colour-coded. Left to right:
| Port | Colour | Required | Cardinality | Sub-node |
|---|---|---|---|---|
| Personality | purple | Yes | 1:1 | Personality |
| AI Model | violet | Yes | 1:1 | AI Model |
| Integration | purple | No | 1:N | Integration(s) |
| Knowledge | teal | No | 1:N | KB folders (semantic search) |
| Action | emerald | No | 1:N | Action tool nodes |
| Operator | amber | No | 1:1 | Operator (this node) |
| Steps | — | No | 1:1 | The first step of the agent's step-by-step process (Steps) |
Required ports show a red asterisk — the Operator port does not, because it's optional. The + glyph on a port is also the drag handle: click it to open the picker, drag it to wire an existing sub-node, or drag it to empty canvas to add-and-connect a new one. Once an Operator sub-node is wired, the + glyph disappears and the port shows a bare handle — no second connection is invited. See AI Agent node ports.
The canvas card
On the canvas the Operator sub-node appears as an amber card with a headset icon. Its subtitle summarises the node, for example:
AI first · 3 web operators · 1 phone operator · 2 AI operators · supervised- Team first when the team answers new calls first
no hand-offwhen the AI has no hand-off
A node still on the settings from before October 2026 reads skill: <group> · old settings or any operator · old settings until you open and save it.
The card connects upward into the AI Agent's amber Operator port.
Connection rules
The canvas enforces connection types before any edge is drawn — it won't let you wire something that activating would reject:
- Type validity: the Operator port only accepts an Operator sub-node. Any other node type is refused.
- 1:1 cardinality: an AI Agent may have at most one Operator sub-node. A second Operator edge into the same agent is refused.
While you drag, the connection line turns green over a valid target and red over an invalid one. See Drag-to-connect + connection rules.
The Operator panel
Selecting the Operator sub-node opens its own panel. The Config tab has four sub-tabs — Team, Routing, Supervision and Copilot — next to the Operator app, Settings and Notes tabs.
Every save is checked, and publishing checks the team and the hand-off for gaps: a row with no person, a group you ticked that nobody is in, or a hand-off with nowhere to go.
Opening a node that still uses the older settings shows them converted — including any older Hand off to Human actions on the same agent, which the panel lists as replaced. Saving writes the new settings.

Team
Team lists who works this agent's conversations. Only people listed here are ever rung for this agent.
Web operators are people who answer in Perfox:
- a Studio user of your workspace — they take calls with Conversations → Go online; or
- an External ID (your app) for an operator who connects through your own console built on the operator SDK. This is a reference only — no account is created.
Drag rows to reorder them (the order matters for the "in the order listed" ring style). Each row can optionally set:
| Field | Meaning |
|---|---|
| Skills | Blank = takes any hand-off. Set = only hand-offs that ask for one of these skills |
| Languages | Blank = any customer. Set = only customers speaking one of these languages |
| Chats at once | Blank = the team default |
| Wrap-up, seconds | Blank = the team default |
Team defaults: Chats at once 0–10, default 3 — counted across every agent the person is on — and Wrap-up after a call, seconds 0–300, default 30 (0 = until they press Ready).
Phone operators are a name and a number that Perfox dials and joins into the call. The number is a Fixed number or comes From workflow data — the AI never chooses it. The call stays on Perfox, recorded and transcribed, and can come back to the AI. Phone operators are dialled one at a time, in the order listed, on a hand-off.
Phone operators are dialled from this agent's own phone number: the number connected to its phone trigger. There is no fallback number. When you publish, Perfox warns you if the agent has no phone number, or if its number isn't one of the numbers on your connected phone account, because those calls would be refused.
AI operators (other AI agents) let the AI pass a voice call to another of your agents. Each has a name the AI uses (lowercase, no spaces, for example refunds), the published agent that takes the call, and Transfer when — the AI picks the AI operator from this text. AI operators are offered on voice calls only, not in chats.
Publishing is blocked for a row with no Studio user or External ID, a person listed twice, a phone operator with no usable number, an AI operator with no agent or no Transfer when, and a duplicate or reserved AI operator name.
Routing

Who answers a new phone call? — The AI (default) or The team (the AI assists). This applies to inbound phone calls only; web chat and web voice are always answered by the AI first. With the team first:
- Ring style: One at a time — longest idle first, One at a time — in the order listed, or Everyone at once — first to answer (default).
- Ring for, seconds: 5–120, default 30.
- Only people with this skill: blank = anyone.
Only web operators are rung. If nobody on the team is online when the call arrives, the AI answers it; if they are rung but nobody picks up in time, the call ends.
When the AI hands off is a switch. Off means the AI gets no hand-off at all and handles everything itself. On gives you:
| Setting | Meaning |
|---|---|
| Hand off when | Your instructions for when the AI should get a person (up to 500 characters) |
| Try in this order (drag to reorder) | Web operators (tick + a ring style) and Phone operators (dialled one at a time, in the order listed). A ticked group with nobody on the Team tab is flagged |
| Ring each person for, seconds | 5–120, default 30 |
| Only web operators with this skill | Blank = anyone |
| If everyone is busy, wait in queue up to (s) | 0–900, default 120; 0 = no queue |
| Tell the caller their place every (s) | 0 = never, otherwise 20–300 |
| If nobody answers | Take a voicemail, or The AI keeps helping; the team calls back (default) |
| When the person leaves the call | Back to the AI (default) or End the call |
| Flag the conversation and notify the team on every hand-off | With no group ticked and no AI operator, this is all the hand-off does |
AI operators on the Team tab are offered to the AI as their own targets on calls. On chats, a hand-off to web operators offers the conversation to the team; AI operators are not offered there.
Waiting sounds:
- Connecting to a person — plays after the AI hands off until a person joins (phone and web voice).
- On hold by an operator — plays while an operator has the caller on hold (phone calls).
- While the team is being rung — when the team answers first: after a short spoken hold line, until someone on the team picks up (inbound phone calls). Default Music — Calm, because silence here sounds like a dead line.
A sound set here wins; otherwise a value set earlier on the AI Model card still applies. The one remaining waiting sound, AI looking up, stays on the AI Model card.
Supervision
Supervision is a switch, then the supervisors (a Studio user or an External ID) and what They can do:
- Listen in — hear the call or read the chat live.
- Whisper — speak to the person on the call; the customer does not hear it.
- Take over — join the customer and drive the conversation.
Alert them when: a customer waits longer than a number of seconds (10–3600), nobody answered a hand-off, and every hand-off.
For an agent whose Operator node uses these settings, only the people listed here may supervise its live conversations, and only with the actions ticked — a workspace role adds nothing. The Live board, Listen / Whisper / Take over on calls, and taking over or releasing a chat all follow this list. Agents still on the older settings keep the role rule (Supervise live conversations). External-ID supervisors are recorded, but alerts and the supervise controls are shown in Perfox Studio only for now. See Live board & supervising.
Copilot
Copilot sets what each operator starts with on a call; they can change it live from the call console.
| Setting | Default | Meaning |
|---|---|---|
| Suggest replies while the operator talks ("Help me" on) | On | Whether the answer panel starts on for each call |
| Suggestion length | Sharp | Sharp (just the value — for example the balance or the date), Short, Medium or Detailed |
| Show rich cards (tables, lists) in suggestions | On | Whether the copilot may also show tables and lists, not just text |
| Copilot language | English | The language the operator reads suggestions in. Mirror = the customer's own language |
| Operators may start outbound calls with this agent | On | See Outbound calls |
When suggestions are on, each customer question produces an answer card — "Customer asked" followed by the key points from the agent's knowledge and tools, with a Copy button — and the operator has an Ask the AI pane for their own questions. The AI never speaks to the caller; it only whispers to the operator.
Outbound calls
When Operators may start outbound calls with this agent is on, an operator can start a call from Conversations: + New (or Reach out → Call), then Phone call → Copilot. The call runs in bridge mode — no AI voice — skips the inbound ring flow, and lands on the customer's phone conversation record.
Operator app tab
The Operator app tab lets you run the copilot from your own operator console instead of Perfox's — for example a support desk your team already uses, built with the Perfox operator SDK. When you turn on Enable operator app for this workflow, your console can drive this agent's copilot: operator availability, inbound ringing, the live transcript, AI whispers and the operator's Ask-AI.
Access is issued per workflow, and the secret is signed on your app's backend — never in the browser.
List the exact Allowed origins (scheme + host, one per line) your console runs on.
Each person who uses the console must be listed on an Operator node's Team tab, in one of two ways:
- by their External ID; or
- as a Studio user. Your console then identifies them by the email they sign in to Perfox with, and the session counts as that Studio user (the same availability, rings and calls). No second External ID row is needed.
Anyone listed neither way is refused.
Leave it off if your operators take calls in Perfox's Conversations page.
Worked example: Asha sets up Acme Support
Setup: Asha opens the Acme Support AI agent in the Agent Builder and drags from the amber Operator port to empty canvas. An Operator node appears and connects automatically. She opens its panel.
Action:
- On Team, she adds Priya and Ravi as Studio users with the skill
billing, and adds the billing desk's landline as a phone operator. - On Routing, she leaves Who answers a new phone call? on The AI, switches on When the AI hands off, writes "when the customer asks for a person or disputes a charge" in Hand off when, and ticks Web operators first and Phone operators second. She picks Music — Calm for Connecting to a person.
- On Supervision, she adds herself with Listen in and Whisper, and asks to be alerted when nobody answers a hand-off.
- She leaves Copilot on its defaults and publishes the agent.
Result: A caller disputes an invoice. The AI says it will connect them; the caller hears calm music while Priya and Ravi are rung. Priya, who is online, picks up with suggestions already on. Asha sees the call on the Live board and listens in. Had neither web operator answered, the billing desk's landline would have been dialled next, and Asha would have been alerted if nobody picked up.
Runtime: what happens on a call
When the team answers first
Only when Who answers a new phone call? is The team does a cold inbound phone call reach a person first:
While the team is being rung, the caller hears a short spoken hold line, then the While the team is being rung sound from Routing → Waiting sounds (Music — Calm by default). With The AI first (the default), nobody is rung when a call arrives.
Alongside the audio, a copilot session transcribes both sides live, labelled operator and customer. When suggestions are on, answer cards reach the operator's screen in real time, in the operator's copilot language. The copilot supports three modes — dictation, live tap, and third actor.
Going online
- A Studio user listed on any agent's Operator node sees Go online in Conversations (tooltip "Take calls for <agents>"). A person on no node has no button and is never rung.
- Online, they take calls and chats for every agent that lists them. The console card reads Ready for calls with "Taking calls for <agents>" and a Go offline button.
- Skills, languages, chats at once and wrap-up come from their row on each Operator node — there is no workspace-wide profile.
- Operators using your own operator app report availability through it, as a listed External ID or as a listed Studio user identified by their email. Anyone else is refused.
- An operator who is ringing, busy on a call or in wrap-up is not offered another call.
- Rings are pushed to the console immediately, with a periodic check as a fallback. Outcomes — no-answer / busy / declined / failed — are reported back.
What you can do with the Operator sub-node
- Decide who answers a new phone call — the AI, or your team with the AI assisting.
- Let the AI hand off to web operators, phone operators or another AI agent, in the order you choose — or not at all.
- Choose what callers hear while they are connected to a person or on hold.
- Name your supervisors and exactly what each may do, with alerts when customers wait.
- Set the copilot your operators start with, and let them dial out.
You can now put your people on an agent — who answers, where the AI hands off, who supervises — all from one node.
See also
- AI Agent Node — the sub-node ports and the cluster the Operator attaches to
- Canvas Basics — drag-to-connect, connection rules, and the node picker
- Copilot (Human-in-the-loop) — the operator console and live-call experience
- Contact Center — how hand-offs, queues and supervision work end to end
- Human Handoff — the workflow-level human pause node, for pausing a workflow for human input rather than connecting a live conversation
- Personality sub-node · AI Model sub-node