Why calls ring but never connect to an agent

A customer's phone rings, but nobody ends up talking to them. Sometimes the call drops, sometimes it just rings forever, and sometimes the agent screen never lights up. This is one of the most common operator complaints, and it almost always lands in one of three places: there were no agents ready, the dialer had nothing to dial, or the carrier rang the line without ever telling the dialer the call was answered. Each one looks similar from the outside, so the trick is knowing which checks separate them.

No agent was ready when the customer answered

In predictive and ratio dialing, the dialer places calls a beat ahead of agent availability. If a customer picks up and every agent is still busy, the dialer has nowhere to send the call. That call gets dropped, and the lead is marked DROP — "Agent Not Available" — while inbound versions of the same event get XDROP. A sudden cluster of DROP statuses almost always means your pacing is too aggressive for the number of agents logged in. Lower the dial level, or watch your live drop count, because too many dropped answered calls is a Nuisance call problem with real compliance weight, governed by your Drop rate limit.

The dialer had nothing to dial

Every 60 seconds the dialer grabs a batch of leads, runs each one through the call-time, filter, and DNC checks, and drops the survivors into the Hopper to be called. If the hopper runs dry, the dialer slows or stops, agents sit idle, and what calls do go out feel sparse and slow. An empty hopper usually means your lists are exhausted, your call-time window has closed for those time zones, or a filter is rejecting almost everything. Check the hopper count before you blame the carrier.

The carrier rang the line but never sent a real answer

SIP (Session Initiation Protocol) is the signalling that sets up and tears down each call between your dialer and your carrier. The dialer only hands a call to an agent once it gets a genuine answer signal. If the carrier rings the line but never returns that signal, the call sits in a ringing state and eventually times out as NA — "No Answer" — which covers ring-no-answer, disconnects, and carrier errors all at once. Worse, some carriers send an early answer signal on a line that is still just ringing. That false Answer supervision tricks the dialer into treating a ring as a live person, so a short PU or a two-second "answered" call that nobody really picked up is a strong tell.

Walking the decision tree

flowchart TD
  A[Calls ring but no agent connects] --> B{Hopper has leads}
  B -->|No| C[Refill lists or fix call time filter]
  B -->|Yes| D{Agents getting DROP}
  D -->|Yes| E[Lower dial level pacing too hot]
  D -->|No| F{Carrier sent real answer}
  F -->|No| G[Mostly NA carrier or routing issue]
  F -->|Yes but very short| H[Suspect false answer supervision]

When the dialer sent more calls than it could place because lines were not available, those attempts log as CHANUNAVAILABLE rather than a carrier rejection. And a burst of CONGESTION codes means the carrier accepted the call but could not complete it on their side. Both are upstream of your agents, so confirm them before you touch pacing.

Where to go next

If the symptom is an empty queue and idle agents, start with why the hopper is empty. For the broader first-response checklist, see the VICIdial troubleshooting playbook.

If you would rather tune pacing than chase phantom drops, VICIfast runs a hardened, managed VICIdial box that is live in under 40 seconds. See our plans and pricing.