Skip to content
Trueline

Catch the callers your fraud checks are letting through

Flag cloned voices and AI voice agents about twelve seconds into the call. Send the flag to the systems your team already works in. Nothing changes on your call path.

preview

Synthetic.

The attacks

The call sounds like your customer.
It isn't.

A cloned voice asks your care team to move a number to a new SIM.

1,055%

rise in unauthorised SIM swaps reported in the UK in 2024, to nearly 3,000 cases.

Source: Cifas, Fraudscape 2025 · May 2025 ↗

Example call

“I've lost my phone. Can you move my number to a new SIM today?”

Measured live

A verdict at twelve seconds.
Then it keeps listening.

How we measure →
Caller audio
Checks
Every 2 seconds
Verdict
Keeps listening
Your systems
Flag sent, with the reason
0s4s8s12s16s20s

19 / 22

Fakes caught live

AI voice agents and cloned voices, over internet and phone-network calls

0 / 12

Genuine calls flagged

Real callers on clean lines

0 ms

Added to your calls

Trueline listens to a copy, so no call waits

How it works

It listens to a copy of the call.
Your calls never wait for it.

The full walkthrough →
The call path with Trueline's tapA caller's phone connects through the carrier to the contact centre. Before the trunk enters the building, a copy of the audio branches to a Trueline rack, which scores it in four-second windows and sends a signed webhook to your systems, drawn as a desk where a flag reads Synthetic. carrier caller01 a copy of the audiolike a call recorder contact centre Truelinechecks the voice every 2 s02 alert sentabout 12 s into the call your systemsthe flag and the reason03
  1. 01Connect your phone line

    Send Trueline a copy of each call from Twilio, Telnyx or your own phone system. Your call routing and agent tools stay exactly as they are.

  2. 02We listen as the caller speaks

    Trueline checks the voice every two seconds and makes its first decision twelve seconds into the call. It keeps listening until the call ends.

  3. 03The flag reaches your systems

    The moment a synthetic voice is detected, your systems are told, with the reason. Your team decides what to do; Trueline never ends a call.

Trueline only listens to a copy of the call, so it can never delay or drop one.

Built for regulated teams

What your security team will ask first.

Encryption, keys and tenancy →

Audio is never stored

It lives in memory for up to eight seconds while it is scored, and is never written to disk. No voiceprint is made, so there is nothing to enrol and nothing to leak.

eight seconds in memory, then there is nothing to hold

It cannot touch your calls

Trueline reads a copy, the way a call recorder does, so nothing is added to the call. If we stop mid-call, your call carries on and the record says how much was scored.

the call carried on to the end; only our scoring stopped

Where it runs

Run it where your calls are.

The same build either way: nothing in Trueline depends on a particular cloud, so your own box is the hosted service with your keys.

The questions we get on the first call.

Every answer here is what the system does today. Where the honest answer is a weakness, it is written as one.

See how it works →
01What about calls from mobile phones?

Our numbers come from internet and carrier routes, which is where voice agent fraud arrives first and where Trueline is strongest.

A mobile leg is a harder path for any detector. The call is compressed by the handset and the mobile carrier before anyone else hears it, and that first hop takes away part of what makes a synthetic voice detectable.

It is where our measurement work is now, and we will not tell you it is solved. If your callers are mostly on mobiles, say so before a pilot rather than after, and the report will tell you where your own traffic stands.

How we measure it →
02If a call is flagged, do you stop it?

No. Trueline is never in the call path, so it has nothing to stop. The flag leaves as a signed webhook and your policy decides what happens next: step up the ID check, hold the payment, move the call to a specialist.

It is an assist for the people who already make that call, not an automatic block.

03Do you need a voiceprint of our customers?

No. Nobody is enrolled and no biometric template is created or kept. Trueline does not compare the caller to a known voice. It judges how the speech itself was produced.

So it works on the first call from a number nobody has heard before, and there is no voice database to govern.

04What if the attacker uses a voice tool you have never seen?

There is no list of tools to keep up to date, so a new engine is not a new signature to add. What gets scored is the way the speech was made, not which product made it.

That is not the same as saying nothing gets through. Where a route does defeat it, as a mobile handset in the path does today, we publish that rather than patch around it.

05Can we see why a call was flagged?

Yes, and it is the same record every time: which rule fired, how many four-second windows crossed the threshold, how much of the caller's speech had actually been heard, and the model version that decided.

The reason travels with the flag and stays on the call record, so the decision can still be explained months later.

Point one week
of calls at it.

You get back every flag with its reason, every fake it missed, and the routes it was measured on. Your calls, not our bench.

Or see how it works first →

Request a demo

  • One week of your calls, scored
  • Nothing added to the call path
  • A report with every flag and every miss