Why agent screen buttons stop responding mid-shift

An agent is halfway through a shift, clicks Hangup or Dispo, and nothing happens. The button looks fine but the screen does not move. This is one of the more frustrating things to chase, because the agent swears they clicked it and the screen swears nothing arrived. The Agent Debug Log Report is the tool that ends that argument, because it records what the screen actually did.

What the agent screen really is

The agent screen is a web page that talks to the dialer over a stream of small background requests. Each button you press fires an AJAX call — a behind-the-scenes web request that updates the dialer and returns the next state without reloading the page. When a button feels dead, one of three things broke: the request never left the workstation, it left but never arrived, or it arrived and the database was too slow to answer. The whole job is figuring out which.

What the Agent Debug Log Report shows

When agent debug logging is turned on in System Settings, this report records almost every button click and back-end AJAX call function for a single Agent session across a time range. It is extremely detailed — hundreds of entries per minute is normal — so you pull it for one agent and one narrow window, not the whole floor.

• The Session ID for the agent, so you are reading exactly the session that broke and not a neighbour's.
• The button or function name that fired, in the order it fired, so a missing click is visible as a gap.
• Timestamps tight enough to see when the stream of calls stalled and when it resumed.

How a click becomes a cause

flowchart TD
  A[Agent clicks button] --> B{Entry in debug log?}
  B -->|No entry at all| C[Request never sent or never arrived]
  C --> D[Suspect network or workstation]
  B -->|Entry present but slow| E[Request arrived late]
  E --> F[Suspect database server load]
  B -->|Entry present and fast| G[Screen logic or browser tab]

Read the log around the moment the agent says the button died. If the click left no entry, the request never reached the dialer — that points at the agent's network connection or workstation, and high Latency on the User Latency Report usually confirms it. If the entry is there but the next function lands seconds late, the dialer received the click and the database server was slow to answer. If everything logged fast and looked normal, the problem is on the browser side — a frozen tab or a stale page.

Where to go next

For a field-by-field walk through every column, see reading the Agent Debug Log Report. If the screen is not just slow but fully locked, the steps in fixing a frozen agent screen come first. And for the broader first-response order, keep the VICIdial troubleshooting playbook handy.

Most of these button stalls trace back to an overloaded or undersized server, which is exactly what you stop worrying about on managed hosting. VICIfast runs a hardened VICIdial box that is live in under 40 seconds. See our plans and pricing.