Real-Time Outbound Call Dashboards: What to Measure and How to Build Them

Why Outbound Dashboards Are Different From Inbound

Inbound dashboards are queue-centric: average wait time, service level, queue depth. Outbound dashboards are rate-centric. The core question is always throughput per unit cost: how many right-party contacts per agent-hour, at what abandon rate, across how many concurrent SIP channels.

When your telephony is per-minute billed, you watch the clock obsessively because every idle second costs money. On a flat-rate outbound network like UnlimCall, the constraint shifts. You watch concurrency and agent utilisation — not the meter. That changes which numbers go on the wall.

The Six Numbers That Belong on Every Outbound Dashboard

1. Active SIP channels (live). The number of calls in flight right now — dialing, ringing, connected, or in wrap-up transfer. This is your real-time concurrency ceiling. If you provision 150 channels for 50 agents and you're sitting at 30 active calls at peak, something is wrong with pacing or list penetration.

2. Agent utilisation rate. Time on call plus wrap-up divided by total logged-in time. World-class predictive floors run 85–92 %. Below 75 % means your pacing ratio is too conservative or your list is too sparse. Above 94 % means agents never get a breath and abandon rates climb.

3. Connect rate (answered / dialed). Track this in 15-minute windows, not daily. A 14:15 dip often signals a list segment problem — wrong time zone, burned caller ID, or a bad DID — that you can correct mid-campaign rather than in the post-mortem.

4. Abandon rate (rolling 30-minute). FTC's Telemarketing Sales Rule sets 3 % over any 30-day period per campaign. Watching it in real time catches spikes before they matter over the longer averaging window.

5. Average handle time (AHT) by campaign. A sudden AHT jump on a collections campaign usually means agents are reading compliance disclosures slowly because of a supervisor reminder. A sudden AHT drop on an appointment-setting campaign usually means agents are hanging up instead of pitching.

6. Right-party contact rate. Connects that reached the actual target, not a gatekeeper or voicemail. This is your quality metric; connect rate is your volume metric. Both have to move together.

Data Sources: CDRs, SIP Events, and Agent State

A real outbound dashboard has three live data streams feeding it.

The CDR stream provides post-call truth: duration, disposition, timestamps, the SIP response code on unanswered legs. CDRs from your SIP trunk arrive with trunk-side detail — you see ring time, not just billable seconds. On a flat-rate network, that distinction matters less financially but matters a lot operationally for diagnosing PDD (post-dial delay) problems.

The SIP channel state feed is your real-time layer. FreeSWITCH, Asterisk, or a commercial predictive dialer all expose current channel state via ESL, AMI, or an internal API. You poll this at one-second or sub-second intervals to get active call counts and per-agent state.

The agent state feed comes from your dialer's agent interface: logged in, ready, on call, wrap-up, break. The intersection of agent state with SIP state tells you whether a busy agent is genuinely on a connected call or stuck in a runaway wrap-up timer.

See the developers section for how UnlimCall's webhook stream surfaces CDR events for custom dashboard builds.

Refresh Rate and Display Hierarchy

Dashboards have two audiences: the supervisor watching a screen and the agent glancing at a wallboard across the room. The supervisor needs 2-second refresh on channel state and 15-second refresh on KPI windows. The wallboard needs larger fonts, fewer numbers, and a 10-second refresh — the human eye can't parse a number that changes every second at 20 feet.

Structure the layout in three tiers:

• Top row (urgent): active calls, abandon rate, connect rate — current moment
• Middle row (trend): utilisation rate, AHT, RPC rate — rolling 30-minute windows
• Bottom row (context): today's dials, today's contacts, list penetration percentage — shift-to-date

Alerting Thresholds Built Into the Dashboard

A dashboard that only shows data without triggering actions is a report, not a tool. Embed threshold logic directly:

• Abandon rate crossing 2.5 % fires a yellow alert; 3.0 % fires red and can trigger automatic pacing reduction in integrated dialers.
• Active channels dropping below 40 % of provisioned capacity during peak hours signals a pacing or list problem.
• Connect rate falling more than 8 percentage points below the prior-day same-hour average suggests a caller ID reputation issue — check your DID rotation logs.