What the PDROP status means and why it points at carrier behaviour

PDROP is one of those statuses that looks like a dialer problem and is almost never a dialer problem. It means a call was dropped before it could be routed anywhere, hung up the very instant the Answer signal arrived. That timing is the whole story, and it points straight at your carrier.

What PDROP records

PDROP stands for pre-routing dropped call. The dialer placed an outbound attempt, the carrier sent back an Answer signal, and the call hung up in the same moment that answer landed. There was no time for the call to reach an agent or even enter the routing logic, so it gets the PDROP Status (lead status) instead of a normal Called status like a sale or a no-answer.

Why the timing accuses the carrier

A real person answering a phone takes a beat to say hello. An answer that arrives and then immediately ends did not involve a person at all. This is the classic shape of a false answer, where the carrier reports the call as connected when it never actually reached a live human. The Answer signal is the part of Answer supervision your dialer trusts to decide a call is live, so when that signal lies, the dialer logs a connection that lasted no time at all.

Why would a carrier send a false answer? Usually it is upstream routing. When a call passes through several networks before it reaches the destination, an intermediate hop can return an answer to make its own statistics look better, or because a downstream leg failed and it papered over the gap. Your dialer has no way to see that chain. It only sees the answer it was handed, trusts it, and then watches the call collapse a fraction of a second later. PDROP is what that collapse looks like in your reports.

The PDROP sequence

sequenceDiagram
  participant Dialer
  participant Carrier
  participant Agent
  Dialer->>Carrier: Place outbound call
  Carrier-->>Dialer: Answer signal
  Note over Dialer Carrier: Call hangs up the same instant
  Dialer->>Dialer: No time to route
  Dialer-->>Agent: Never reaches an agent
  Dialer->>Dialer: Log status PDROP

What to do about it

• Confirm the pattern. A handful of PDROPs across a busy day is noise. A spike concentrated on one route is a carrier signal.
• Match the PDROP calls back to the Carrier and the Trunk they rode on. If they all share one trunk, you have your culprit.
• Compare the CID (caller ID) presented on the bad calls. False answers often cluster on numbers that are getting flagged or rejected upstream.
• Take the evidence to your carrier. PDROP timing is hard to argue with because the answer and the hangup share a timestamp.

One thing PDROP is not is a reason to slow your pacing. Because the calls never reached an agent, throttling your dial level will not move the number, it will just lower your call volume while the false answers continue at the same rate. The fix lives with the carrier and the route, not with how aggressively you dial. Chasing it through pacing settings is a common and costly wrong turn.

PDROP is one face of a wider problem, and the deeper diagnosis lives in diagnosing false answer supervision, which walks through proving short-duration false answers across your reports. For the full first-response checklist, start with the VICIdial troubleshooting playbook.

Run on a box that surfaces it

Catching PDROP early means having reports that group calls by route and duration so a false-answer spike is obvious. VICIfast runs a managed, hardened VICIdial server, live in under 40 seconds, with those reports built in. See our plans and pricing.