Blog: Automation
Divert known fraud callers to an AI voice agent
By the TelecomsXChange engineering team ยท
An automation rule can now do more than hang up on a flagged caller: their next call is answered by an AI voice agent instead of your customers, still recorded, transcribed and scored. Whether the agent fools anyone is an open question. The plumbing works today, with xAI's voice agents.
What it does
Divert sends the caller to an agent instead of a 403
Until now an automation rule had one action: block. The caller's number gets a SIP 403 on its next call, the call never reaches your route, and the fraudster moves on to the next carrier in their list. It is effective and cheap, and it tells the caller only that this trunk is closed.
Divert keeps the door open and changes who answers. The number is controlled the same way, but the next call is routed to a Voice AI destination of yours: an agent with a persona you chose on the agent side. The one we tested is an elderly person who is happy to chat, asks the caller to repeat things, and goes along with whatever the script wants, slowly. The fraudster spends their time on a machine. Your customer never hears the phone ring.
Under the hood
How a diverted call travels
- A call from the number is analyzed and the verdict crosses your rule's threshold. The number is added to Controlled numbers with the reason, the action and an expiry.
- The next INVITE from that number reaches the ingress. Controls are checked before routing, so the divert happens at the SIP layer, before the call touches your route or your switch's downstream.
- The proxy sends the call on to the Voice AI destination over TLS, with the agent's number as the request URI, and answers the agent's digest challenge if it has one. The media is relayed and recorded both ways, as always.
- When the call ends, the recording is decoded (G.711 or G.722, whichever the agent chose), transcribed and analyzed. The record shows the call was diverted, and the transcript shows what the caller tried.
Nothing about the diverted call is special to the pipeline. It is billed per second like any other, it counts against your ports while it is up, and every piece of evidence is kept: the stereo recording, the transcript, the verdict, the SIP ladder, the capture, the quality of each leg.
Setup
Three steps in the portal
- Under Network, add a destination of kind Voice AI: the agent's SIP host, TLS on port 5061, and the agent's number as the Agent ID. For xAI that is sip.voice.x.ai and the Direct SIP number you registered with them. Digest credentials or an IP allow-list go on the agent side.
- Under Automation, create a rule: the probability threshold, the recommendations that count, the action Divert the call, the Voice AI destination, and a duration.
- Place a test call through the web dialer from a number you control, let the verdict cross the threshold, and call again. The second call is answered by the agent.
The Divert to a Voice AI destination is marked beta in the portal. The SIP side works. What is still settling is which agent providers we test against and how their personas are best written.
Limits
Will it fool anyone?
We do not know yet. Today's AI voices are good and getting better, but in a live call they still sound synthetic in places: the timing of a reply, the way a question is handled, the too-even tone. A practised fraudster who makes hundreds of calls a day may notice within a minute and hang up. If that is all that happens, the feature has still cost them a minute, kept your customer out of it, and left you a recording of the attempt with the number controlled for the duration you chose. That has value, but it falls short of a trap.
The SIP path, the controls, the recording and the analysis are in place and provider-agnostic. As voice agents get more natural, the same rule gets more useful without anything changing on your side. We will publish what we see on real traffic, including the calls where the caller caught on.
One practical note: a diverted call is a recorded call. Recording-consent rules vary by jurisdiction and apply here as they do to every call through the platform. Check yours before you point an agent at live callers.
Summary
The takeaway
A flagged number's next call can now be answered by a voice agent instead of your customer, at the SIP layer, with the whole call recorded and analyzed. It works today with xAI's voice agents. Whether the persona holds up against a real fraudster is still being tested. The divert, recording and analysis already work.
Related: three ways operators use Open Voice Shield, getting started, or start free with $5 credit.
Questions
Frequently asked questions
What does diverting a caller to a voice agent do?
Once an analyzed call from a number crosses the fraud threshold in your automation rule, that number is put under control for the duration you set. Its next calls are answered by a Voice AI destination of yours instead of reaching your customers: the call is relayed to the agent at the SIP layer, recorded, transcribed and analyzed like any other call.
Which voice agents work with Open Voice Shield?
A Voice AI destination is a SIP endpoint with an agent number; today it is built and tested with xAI's voice agents, reached over TLS. The agent's persona, voice and script are configured on the agent side. Other providers with a SIP interface can follow the same path.
Is the diverted call still recorded and analyzed?
Yes. A diverted call is an ordinary call through the platform with a different destination. It keeps its stereo recording, transcript, verdict, SIP ladder and per-leg quality, and it is billed per second like any other call.
Will a fraudster notice they are talking to an AI?
Sometimes, yes. Current AI voices are good but still sound synthetic in places, and a practised caller may pick up on it. Even then the call cost the fraudster time, never reached a customer, and left a recording. Whether it does more than that is what real traffic will show.
How do I set it up?
Add a Voice AI destination under Network (agent host, TLS on 5061, the agent's number), then under Automation create a rule with the probability threshold and recommendations that count, choose Divert the call, pick the Voice AI destination and a duration. Controlled numbers are listed with the reason and can be released at any time.