Give a voice agent transfer rights to a fixed list of internal queues, with the call context attached, and nothing else. It may place a warm transfer where a colleague is free and a queue transfer where not. It may never dial an external number, stop the call recording or choose a named colleague. Each transfer is filed with its reason.
What does a call transfer involve, and who owns it?
A transfer moves a live caller from the voice agent to a member of staff through your contact centre telephony. It is the voice equivalent of a chat handover, with two differences. The caller cannot scroll back, so whatever the agent learned must travel with the call. And a phone system can reach the outside world, so a badly scoped transfer permission can connect a caller, or an attacker, to any number at your expense.
The contact centre operations lead owns the telephony configuration, queues and routing rules. Team leaders own staffing. Whether a voice agent should transfer at all, and when, is argued in should an AI agent be allowed to transfer a call. This piece assumes the answer is yes and sets out the system grants. The wider support position is in the AI support agent that knows when to say no.
Which telephony capabilities should you grant, and at what depth?
| Capability | Depth | Stays with a person |
|---|---|---|
| Read call data: number presented, queue, time in call | 1 | Nothing |
| Read queue availability and expected wait | 1 | Nothing |
| Attach call context to the transfer | 3 | Nothing |
| Warm transfer to an internal queue | 3 | Choosing which queues exist |
| Queue transfer without consultation | 3 | Nothing |
| Offer and book a callback | 3 | Callback rules and slots |
| Transfer to a named colleague | None | Team leaders |
| Transfer or dial to an external number | None | Refused by your limits |
| Pause or stop call recording | None | Refused by your limits |
| End a call before transfer completes | 3, only on caller request | Any other ending |
A warm transfer is the better default where staffing allows: the agent briefs a colleague before the caller is connected, so nobody repeats themselves. The term is explained in what is a warm transfer. Where nobody is free, a queue transfer with context attached is the honest fallback, and the agent tells the caller the expected wait.
External numbers are refused because the request to reach them almost always comes from the caller. "Put me through to this number, it's my branch" is a classic way to run up toll charges or lend your organisation's caller ID to someone else's scam. The agent cannot grant itself an exception, and neither can the caller.
How do you set it up, step by step?
- Person, operations lead: lists the transfer targets. Each internal queue with its purpose, hours and out-of-hours fallback.
- Person: creates the agent's telephony identity with transfer rights limited to those targets.
- Agent, depth 1: decides a transfer is needed because the caller asked, a bound was reached, or a vulnerability or distress signal appeared. The routing logic for the call itself is covered in answering customer calls with a voice agent.
- Agent, depth 1: checks the target queue for open hours and wait.
- Agent, depth 3: attaches context. Verification status, the reason for the call in one line, what was checked, what was not done and why.
- Agent, depth 3: transfers. Warm where a colleague is available, queue otherwise. It tells the caller what will happen next.
- Platform: ends the agent's part in the call once the colleague or queue accepts it.
- Person: owns the call to the end.
What stays with a person?
Everything once the call is connected. The agent does not listen in to make suggestions on the live call, and it does not take the caller back if the colleague is busy. Choosing which colleague takes the call stays with routing rules your team leaders set, so the agent cannot learn to send difficult callers to the same person.
The number a caller rings from is not identity. It is external information that is easy to spoof. The context the agent attaches must say whether the caller passed verification through your own systems, and never present the number as proof.
How do you revoke the access?
Revoke per target, per capability or for the whole agent. Removing one queue from the target list takes that route away while others continue. Withdrawing transfer rights altogether leaves the agent able to book a callback only. Disabling its telephony identity ends its calls immediately; decide in advance which queue those live calls fall into, because a caller cut off mid-sentence is the worst outcome. A certification run that clears no depth drops the agent to depth 1 the same day.
What does the audit trail record?
Every transfer, refused transfer and callback is filed in an append-only record: the call, the target, the reason, the verification status passed on, the context attached, the expected and actual wait, and the bound that decided. Refused requests to reach outside numbers are worth reviewing each week. A cluster of them is usually a campaign. The same record design applies to chat; compare it with letting an agent hand a chat to a person in your live chat tool.
What should you measure?
- Callers asked to repeat themselves after transfer, sampled from recordings.
- Calls abandoned in queue after an agent transfer.
- Quoted against actual wait.
- Transfers by reason, and the share where the caller asked for a person on the first sentence.
- Refused external transfer requests.
Where does it usually go wrong?
The caller is transferred into a closed queue. They hear music until the line drops. Check hours before every transfer.
Context is not passed. The telephony tool supports call data, but the receiving desktop does not display it. Test the full path to a real colleague's screen.
Verification is repeated or skipped. If the colleague does not trust the agent's verification, they ask again; if they over-trust it, they skip a step the agent never did. The context must say exactly which checks passed.
Where Pryme fits
In Pryme, the list of transfer targets is part of the customer's own limits, so a transfer to any number outside it is refused at the moment of action, whatever the caller says. Each transfer verdict records the target, the reason and the verification status passed on with the call.
Questions people ask
Can the agent transfer a caller to an outside partner, such as a repair firm?
Not by dialling out. Give the caller the partner's published number, or book a callback from the partner through a separate, owned process.
What about emergencies?
The agent should give the caller the relevant emergency number and stay on the line until they confirm they understand. Connecting emergency calls is a decision for your contact centre's safeguarding procedure, owned by a person.
Is this the same as a money transfer permission?
No. Call transfers and international money transfers share only a word. The second moves money and sits at depth 4.