Answer supervision and false answers from carriers

Answer supervision is the signal your carrier sends to say a call was genuinely answered. A false answer is when that signal fires before anyone actually picks up, which makes dead calls look connected, inflates your stats, and quietly breaks predictive pacing.

What answer supervision is

When you place an outbound call, the far end goes through stages: ringing, then answered, then eventually hung up. Answer supervision is the moment the Carrier reports back over the SIP (Session Initiation Protocol) signaling that the call connected, typically a 200 OK. Your dialer trusts that signal: it marks the call answered, starts the billing clock, and on a live connect bridges an agent. The Hangup cause reported at the end tells you why the call ended, but answer supervision is what defines when it truly began.

Everything downstream hangs on that one signal being honest. Your connect rate, your billing, and the pace your dialer runs at are all built on the assumption that an answered signal means a human is on the line. When the signal is accurate, the whole system stays in sync. When it is not, every number that depends on it drifts away from reality, and you cannot tell from the dashboard alone.

False answers: billing on ring

A false answer (sometimes called false answer supervision, or billing-on-ring) is when a carrier somewhere in the chain returns that answered signal while the phone is still ringing or has already failed. The effect is that the call looks connected when no human is there. Carriers on grey routes sometimes do this on purpose to start billing earlier; sometimes it is a misconfigured switch upstream. Either way, your dialer believes a lie.

True answer vs false answer

The difference is purely about timing: when the carrier sends the answered signal relative to a human actually being there.

sequenceDiagram
  participant V as VICIdial
  participant C as Carrier
  participant P as Called party
  Note over V,P: True answer
  V->>C: INVITE
  C->>P: Ring
  P-->>C: Picks up
  C-->>V: 200 OK answered
  Note over V,P: False answer
  V->>C: INVITE
  C->>P: Ring
  C-->>V: 200 OK answered
  Note over P: Still ringing, nobody there

Why it wrecks pacing

A predictive dialer paces calls using your connect rate. If false answers inflate that rate, the math says you are connecting more often than you really are, so the dialer over-dials to keep agents busy. The downstream damage looks like this:

• Connect and answer rates read higher than reality, so reports lie to you.
• Agents get bridged to silent or already-dead calls and burn time disposing of them.
• Pacing over-corrects, which can push real connected calls into abandonment when the dialer guesses wrong.

How to catch it

Watch for connects that answer suspiciously fast and instantly go dead, and compare talk time against connect counts: lots of zero-second talk on supposedly answered calls is the tell. If one carrier shows it and another does not on the same leads, route around the bad one. Running more than one carrier makes that easy to do; see multiple carriers and failover for setting that up so you can shift traffic off a carrier you do not trust.

Answer supervision is one of several carrier behaviors worth understanding. For the full set, read our VICIdial carrier integration guide.

You choose the carriers; we give you a dedicated VICIdial server, provisioned in under 40 seconds, with the reports to spot a bad one. See our plans to begin.