What the Shared Debug Page shows for shared-agent campaigns

The Shared Debug Page shows the real-time and recent historical decisions that the shared-agent dialing logic is making — specifically which Campaign gets the next available Agent and how dials are being paced across the shared pool.

What shared-agent campaigns are

In a standard VICIdial setup each campaign owns its own agents. Shared Agent Campaigns flip that: one pool of agents is assigned across more than one campaign simultaneously, and VICIdial decides on each cycle which campaign those agents should be dialing for. The system tries to balance call volume across the active campaigns while staying within each campaign's own pacing limits. This is a non-default feature — if you have not deliberately configured it, the Shared Debug Page will have nothing meaningful to show.

What the debug output contains

The page presents both current state and recent history for two separate processes: agent rotation and dialing. Understanding which process produced a given log line is the first step to reading the page:

• Agent rotation log — records which campaign each Agent session was assigned to when an agent became available. You can see the weighting or priority the system used and whether it matched your expectations. If one campaign is consistently winning every rotation, look at its priority settings relative to the others.
• Dialing log — records the Auto dial level being applied per campaign and the number of calls placed on behalf of each one. If you see one campaign placing far more calls than another, the dialing log will show the dial levels and available-line counts that produced that imbalance.
• Historical view — the page shows not just the current tick but a window of recent cycles, so you can see whether the imbalance has been consistent or whether it is a short-term fluctuation caused by a burst of dispositions on one campaign.

When to open this page

Open the Shared Debug Page when one or more of these is happening on a shared-agent system:

• One campaign appears starved — calls are low or agents are rarely assigned to it even though it has leads and the pool has agents.
• Pacing across the shared pool is uneven in a way that is causing drops on the high-volume campaign and wasted capacity on the low-volume one.
• You have changed campaign priority weights and want to confirm the rotation logic picked up the change on the next cycle.

flowchart TD
  A["Agent becomes available"] --> B["Shared rotation logic runs"]
  B --> C{"Campaign priority weighting"}
  C --> D["Campaign A gets agent"]
  C --> E["Campaign B gets agent"]
  D --> F["Dialing log records dial level and calls placed for A"]
  E --> G["Dialing log records dial level and calls placed for B"]
  F --> H["Shared Debug Page shows rotation + dialing entries"]
  G --> H

What to do with what you find

If the rotation log shows one campaign winning every assignment, compare the campaign priority values. The shared-agent algorithm respects the priority order you set; if you want a more even split, bring the priorities closer together. If the dialing log shows Dialer pacing being suppressed on a campaign that should be running hard, check whether that campaign has hit its Drop percentage limit — the pacing algorithm will back off to protect the drop rate even in a shared-pool context.

The Shared Debug Page only covers the shared-agent logic. For individual campaign issues on a non-shared campaign, the per-campaign debug page is the right tool. For the server-level picture that sits behind all of this, see our guide to monitoring VICIdial server health and capacity. To understand whether the server itself is keeping up with the shared workload, cross-reference with the Server Performance Report.

Running a shared-agent setup on self-managed hardware adds configuration complexity. Start a VICIfast trial and get a fully managed VICIdial box provisioned in under 40 seconds, with all debug pages available from first boot.