Connect the agent through its own service identity, and grant telephony capabilities one at a time: read call context, answer, transfer, call back. Each gets its own depth and its own certificate. The agent never controls recordings, edits routing or changes queues. Every call event it touches is written to the record alongside the verdict that allowed it.
What does the connection involve, and who owns it?
A contact centre telephony platform routes calls to queues and advisers, runs the menu callers hear, records calls, places outbound calls and reports on all of it. Connecting an AI agent means letting it sit inside that flow: receiving a call or a stream of its audio, knowing who is calling and why, speaking, and passing the call on.
The telephony or contact centre systems team owns the platform and its configuration. Security owns the agent's identity and credentials. Compliance owns recording, consent and disclosure rules. Operations owns queues and routing. The agent is a new kind of participant that must fit into all four, which our guide to the AI support agent that knows when to say no treats as the starting point: capability first, then authority.
What are the steps, and at what depth?
- Person, systems team: creates a dedicated identity for the agent on the telephony platform, separate from any adviser login, with credentials held in your secrets store and a named owner.
- Person, security: grants read access to call context. Caller number, menu choices, queue, and, after authentication, the customer reference. Depth 1.
- Agent, depth 1: receives live audio for calls routed to it, through the platform's supported interface. It does not receive audio for calls handled by advisers unless a separate assist capability is granted.
- Person, systems team: grants answer capability, so the agent can speak on calls routed to it. Depth 3 once certified.
- Person, systems team: grants transfer capability to a defined list of queues, with the handover note attached as call data. Depth 3.
- Person, operations: decides on outbound callbacks. Starts at held: the agent proposes callbacks and a person approves the list. Moves to depth 3 only with evidence and within consent and calling-hours rules.
- Agent, depth 3: sets wrap-up codes on calls it handled, from your approved list.
- Person, compliance: keeps recording control. The agent cannot start, pause, stop or delete recordings. Card payments use the platform's secure capture, which pauses recording without the agent.
- Person, systems team: tests revocation. Disabling the agent's identity must stop it taking calls within minutes, with calls falling back to the adviser queues.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Call context | Reads caller and menu data | 1 | Nothing |
| Audio | Receives audio for its calls | 1 | Assist on adviser calls |
| Answer | Speaks on routed calls | 3 | Script approval |
| Transfer | Sends to listed queues with note | 3 | Queue list |
| Callback | Proposes, later places, calls | 2, then 3 | Approving early lists |
| Wrap-up | Sets disposition codes | 3 | Code list |
| Recording | Nothing | none | All recording control |
| Routing | Nothing | none | Queues and routing rules |
Which controls matter, and what evidence does each leave?
One identity, one owner. Calls handled by the agent are attributable to it, never to an adviser login. Evidence: platform logs showing the agent's identity on each call.
Capabilities listed, not inherited. The agent's role grants specific platform functions. Anything not granted is refused. Evidence: the permission list and refused verdicts.
Transfer targets are a fixed list. The agent cannot send calls to arbitrary numbers. Evidence: transfer records against the approved list.
Recordings are out of reach. Evidence: no recording-control calls from the agent's identity in platform logs.
Revocation works. Evidence: dated revocation tests and fallback results.
Every call is filed with the verdicts for each action. Evidence: the append-only record joined to the platform's call ID.
What should you measure?
- Calls answered and resolved by the agent, and transfers by queue. Resolution on the first call is the measure that matters most; see what is first-contact resolution?
- Transfer failures: calls dropped or misrouted on handover.
- Refused actions, which show where the agent tried to do something it was not granted.
- Callback approvals and complaints about unwanted calls.
- Fallback time when the agent is unavailable.
Where does it usually go wrong?
The agent gets an adviser's login. It is quicker to set up and gives far too much access, including recordings and supervisor functions. Always a dedicated identity.
Menus and the agent duplicate each other. Callers press options, then the agent asks the same questions. Pass menu choices as context.
Preference changes happen by voice without checks. A caller asks to stop receiving calls; the agent changes the setting on an unverified call. Can an AI agent change a customer's contact preferences? explains the verification needed.
Knowledge is not connected. The agent answers from a script while the help centre has the current answer. Connect both; how to connect an AI agent to your help centre covers the second connection, and finding gaps in the help centre with an AI agent uses call transcripts to improve it.
Fallback was never tested. The first outage strands callers in a silent queue.
Where Pryme fits
In Pryme, each telephony capability is a separate entry in the agent's role scope with its own certificate, so transfer can be at depth 3 while callbacks remain held. Recording control is never in the role, and every call action is filed against the platform's call ID.
Questions people ask
Can the agent listen to adviser calls to help them?
That is a separate capability, agent assist, with its own permission, disclosure and certification. Do not grant it by default with the answering capability.
Should the agent see the full call history of a caller?
Only after authentication, and only the history needed for the call. Recordings of past calls are rarely needed; summaries usually are.
How fast must revocation be?
Fast enough that a misbehaving agent stops taking calls before it does lasting harm. Test it, and route calls back to advisers automatically when it fires.