Skip to content
Trueline

How it works

It reads a copy of the call. Nothing waits on it.

Trueline receives caller audio the way a call recorder does, as a fork of a stream your platform already carries. It is not a hop in the media path, so there is no latency to budget for and no call it can drop.

Integration model
Passive tap, never inline
Added latency
None, on any call
First verdict
About twelve seconds of speech
Action taken
Advisory only, your flow decides

Where it sits

A branch off the trunk, not a hop in it.

The same call, two places to put a detector. Latency budgets, failure modes and rollback plans all follow from which row you are in.

In the media path

Adds latency to every call. Can drop one.

Caller
Carrier
Vendor
Agent

Trueline, passive tap

No added latency. Cannot drop a call.

Caller
Carrier
Your platform
Agent
Trueline
Your systems

the calla copy of the audiothe flag, to your systems

Inside a call

A clear at twelve seconds can still be overturned.

A clear result is provisional. Two confident windows inside any thirty seconds overturn it, which is how a caller who hands over to a synthetic voice mid-call is caught.

Caller audio
Checks
Two confident windows
Verdict
Clear so farFlagged
Your systems
Flag delivered, with the reason
0s8s16s24s32s40s
a call that opened clean and was handed to a synthetic voice; the provisional clear at 12 s is overturned at 20 s

Getting the audio to us

Any platform, one record.

Carriers paste one URL. Contact-centre platforms open a session. Same record either way.

Trueline
Record

What you receive

A flag is a record, not a verdict from a black box.

call record28 s scored · coverage 100%

the record keeps every window, before and after the flag

call.flaggedsigned

Rule that fired
two confident windows
Confidence
0.99
Raised at
20.0 s, window 9
Coverage
100% of the audio scored
Engine
release 9
Delivery
signed, delivered

Retried until received. Kept on the call record for your retention window.

Failure behaviour

When something breaks, the call does not.

01Scoring engine unavailable
Calls carry on. Sessions in the gap close as inconclusive with their coverage recorded, so the gap is visible.
02Connection drops mid-call
The call continues. The session resumes on the same record, and what was scored before the drop stays on it.
03Flag cannot be delivered
Retried on a backoff schedule, every attempt visible to you. Events are signed, so a flag can be verified as ours.
04You disagree with a verdict
Every call carries its rule, engine release and window scores, so a case is reviewed from the record, not from memory.

Switched on in an afternoon, in front of your own traffic.

A pilot runs on one number or one queue, beside everything you already have. Your call flow and your agent desktop do not change to accommodate it.