Diagnosing calls that drop while the customer is on hold

Few complaints are harder to take seriously without data than a customer who hung up while on hold. The agent says the call just vanished, the customer is gone, and there is no obvious culprit to point at. It is the kind of thing that gets shrugged off as a one-off until it happens often enough to dent your numbers. The Agent Parked Call Report turns that anecdote into a number, because it counts exactly how many parked calls dropped while the customer was waiting.

What parking a call actually does

When an agent puts a customer on hold, the dialer uses Call park — it moves the live caller into a holding slot and plays them music while the agent steps away to check something or grab a supervisor. The customer is still connected to a Channel on the box; they are simply parked. A drop on hold means that parked channel was torn down before the agent came back, which is a very different problem from an agent fumbling the unpark.

What the Agent Parked Call Report shows

Run this report for a single day and it breaks parked calls down by agent and by timeframe. The three figures that matter for a drop investigation are:

• The number of calls parked, per agent and per timeframe, so you can see who parks a lot and when.
• The average time on hold across all calls, which tells you whether customers are waiting seconds or minutes.
• The number of calls that dropped while the customer was on hold — the headline figure for this problem.

Reading the numbers together

flowchart TD
  A[Run Agent Parked Call Report for the day] --> B{On-hold drops high?}
  B -->|No| C[Holds are healthy]
  B -->|Yes| D{Average hold time long?}
  D -->|Yes| E[Customers giving up while waiting]
  D -->|No| F[Short holds still dropping]
  F --> G[Suspect park timeout or RTP path]
  E --> H[Coach faster unpark or warmer hold]

Read average hold time and on-hold drops side by side, because neither number means much alone. If drops are high and the average hold is long, the simplest explanation is that customers are giving up — minutes of music wears anyone down, and that is a process fix, not a server fault, so coach faster unparks and a warmer hold experience. If drops are high but holds are short, customers are not getting bored fast enough to explain it, and you should suspect a park timeout that is too aggressive or an RTP path going quiet so the customer hears dead silence and assumes the line is gone.

Where to go next

For a column-by-column walk through, see reading the Agent Parked Call Report. If the silence-then-hangup pattern is what you are seeing, the audio-path angle in the VICIdial troubleshooting playbook is the next stop.

A correctly tuned park timeout and a clean RTP path are exactly the kind of detail a managed box handles for you. VICIfast runs hardened VICIdial that is live in under 40 seconds. See our plans and pricing.