Why your drop rate suddenly spiked and how to trace it

Yesterday the campaign sat at a comfortable drop rate, today it is double. Nothing obvious changed, but the number jumped. The drop rate is the share of answered calls the dialer connects with no agent ready to take them, and a sudden spike almost always comes from a small number of causes. The good news is each one leaves a trace.

The Drop rate is a ratio of dropped answers to total answers. When it climbs fast, either the dialer is calling too aggressively for the agents on hand, or the answers themselves changed character.

What pushes the rate up

Drops happen when more calls answer than there are free agents to receive them. So anything that raises answers or lowers free agents moves the rate. A more aggressive dial ratio, a batch of fresh leads that answer more often, fewer agents staffed, or false answer supervision counting voicemails and machines as live answers all do it. Predictive pacing adapts over time, but it adapts to a moving target, so a sudden change in inputs shows up as a spike before the algorithm catches up.

Before you assume the dialer misbehaved, pin the spike to a clock time. Line up the moment the rate jumped against your shift schedule and your list-load times. Most spikes land exactly when a new list went active or a break wave pulled agents off the floor, and that timestamp alone usually names the cause.

flowchart TD
  A[Drop rate spikes] --> B{Dial ratio raised}
  B -- Yes --> R1[Lower the ratio]
  A --> C{Fresh leads loaded}
  C -- Yes --> R2[Answers up vs agents]
  A --> D{Fewer agents staffed}
  D -- Yes --> R3[Capacity dropped]
  A --> E{False answers counted}
  E -- Yes --> R4[Tune detection]

Trace it in order

1. Check the dial ratio against agents. If predictive pacing or the Dial level was raised, or agents dropped while the level stayed high, the dialer is over-calling. Compare calls placed per agent now versus before the spike.
2. Look for a fresh lead batch. New, never-dialed leads answer at a higher rate than recycled ones. Drop a chunk of fresh Lead records into a busy campaign and answers outrun agents until pacing adapts. Check whether a new list went active right when the rate moved.
3. Count staffed agents. Fewer agents at the same dial level means more answers with no one to take them. A shift change, a break wave, or logins that lagged all cut capacity. The real-time report shows agents available versus calls ringing.
4. Rule out false answer supervision. If the carrier reports answer too early, the dialer thinks machines and ringback are live people and drops them. Inflated Answer supervision makes the drop rate look high when the real connect rate is fine. Review the hangup causes on the dropped calls.

Trace through the four and you will find the lever that moved. For the full method, see the troubleshooting playbook. To bring the number back down once you know the cause, read how to lower your VICIdial drop rate, and to rule out false answers from the carrier, the hangup cause report shows why each dropped call ended. If you would rather not babysit pacing on your own infrastructure, VICIfast runs the dialer box so you can focus on the campaign.