DocumentationDeployment TrustContact sales

Answer the phone, not the machine.

Every answered call is judged in the first second, person or recording, and the disposition goes straight back to your dialer. Runs inside your network. Never charges you per call.

Person, connected Machine, dropped Illustration · typical outbound traffic
3.0%
The ceiling you cannot cross

The FTC caps abandoned calls at 3.0% of answered calls; Ofcom sets the same limit for silent calls. Every live answer dropped in error counts against it.

00 Your stack

It sits between the carrier and the headset.

  1. CarrierThe trunk delivers the answered call
  2. Your dialerVICIdial, Asterisk, whatever you run
  3. AMD CopPerson or recording, decided here
  4. Desk phoneOr softphone, or SIP endpoint
  5. Your agentOnly ever hears a person
01The incumbent

A stopwatch cannot hear.

Asterisk's detector times the call. Silence length, greeting length and word count, each measured against a fixed threshold. Never against the audio.

So it cannot separate a slow hello from a recorded one.

FIG Live answers released in error
Illustration · proportion exaggerated for legibility
FIG Agent occupancy
Illustration
02What changes

Seats fill with conversations.

Recordings are released before they reach a headset. Capacity rises without adding a seat.

Nothing plays to the called party while the call is judged.

03 Side by side

Same calls. Different verdicts.

The detection you have now
Waits up to 5 seconds to decideGuesses from timing alone
How a verdict lands · illustration
With AMD Cop
Decides in about a tenth of a second targetListens to the answer itself
How a verdict lands · illustration
Runs onYour own servers
New hardwareNone
Cost per callNothing
Your recordingsStay with you
Gets it right99% target
Decides in100 ms target

The five second figure is the default waiting time in standard Asterisk detection. Both panels are drawings of how a verdict lands, not measurements: the number of wrong verdicts shown is illustrative. Accuracy and speed are design targets, not measured results.

04 Impact on the floor

Every machine that reaches a headset is paid for.

An agent who answers a recording loses roughly ten seconds before they can dispose of it and move on. On a BPO floor that repeats all day, and it is time you have already bought.

Seats100
Hours per seat per day8
Answered calls per seat per day180
Recordings reaching an agent15%
Handling time each10 s
Agent hours lost per day7.5

A worked model, not a measurement. Substitute your own volumes; the arithmetic is seats x calls x pass-through x handling time, against a floor of seats x hours. Ten seconds is our own estimate of dispose-and-move-on time.

05 Deployment

Three models. One engine.

Self-managed

Community

  • Unlimited calls, unlimited servers
  • Runs on infrastructure you own
  • Public release channel
  • Community support
Self-managed · supported

Enterprise

  • Everything in Community
  • Contracted response times
  • Deployment and tuning assistance
  • Named support contact
  • Early access to model releases
Vendor-operated

Private cloud

  • Dedicated tenancy
  • No infrastructure to run
  • Contracted response times
  • Consumption-based terms
06Trust

Nothing crosses the boundary.

Hosted detection makes a vendor a processor of your customers' voices. Under GDPR, or a client data agreement, that is where most evaluations end.

No egress to review. No sub-processor to declare.

FIG Your network perimeter
Illustration

Point one campaign at it.

Run it beside what you already have. Compare dispositions on live traffic for a week. Reverting is one field.