Your list is degrading right now. Aged leads, disconnected numbers, leads that already converted on a different campaign, numbers that hit DNC since you imported them — all of them are burning dial attempts and suppressing your contact rate. Here's how to build the monitoring layer that surfaces this before it collapses your numbers.
Why List Health Degrades Faster Than You Think
A fresh lead list has a predictable contact rate. As it ages, that rate decays — but not linearly. The first pass reaches the easiest contacts. Each subsequent pass hits harder-to-reach numbers, people who've already heard the pitch, numbers that have gone stale since import. The decay curve accelerates as penetration increases.
Most Convoso operations notice this as "the list is getting old" and respond by ordering more inventory. The actual problem usually sits earlier: the campaign's penetration rate wasn't being tracked, import hygiene missed duplicates against existing leads, and the warning signs were invisible until the contact rate had already collapsed.
A 10% drop in contact rate over a week is expensive. A 30% drop is a bad week. Neither one is a surprise if you're monitoring the right signals before they hit.
What List Health Monitoring Tracks
The metrics that matter, in roughly the order they'll help you:
Penetration rate by campaign. What percentage of imported leads have been attempted at least once? This is the leading indicator — the one that gives you time to act. When penetration reaches a threshold, you need new inventory in the pipeline before the campaign goes hungry, not after agents are sitting idle. Convoso doesn't surface penetration rate prominently in its standard reporting. You have to calculate it from the data the API exposes.
Contact rate by lead age. Track conversion not just in aggregate but broken down by how long ago a lead was imported: leads attempted in week one, week two, week three since import. The decay curve tells you when a list is effectively exhausted from a productivity standpoint, even if numbers technically remain. Most operations have more "leads" than viable leads — the monitoring makes that distinction visible.
Lead aging distribution in active campaigns. A campaign can look healthy on aggregate while its active pool is dominated by weeks-old records. Breaking it down by import age surfaces this before it becomes a contact rate problem.
Cross-campaign duplicate exposure. A number active across multiple campaigns creates agent confusion, customer frustration, and wasted attempts. Deduplication at import catches most of this; monitoring catches what slipped through and surfaces it before it compounds.
The Complication: Convoso Shows You the Past
Convoso's built-in reporting is backward-looking. It shows you what your contact rate was yesterday, what it was last week, how many dials converted over any given period. That data is genuinely useful for trend analysis, period comparisons, and reporting to management.
It doesn't tell you what your contact rate is going to be in two hours if the list doesn't change.
The monitoring that prevents a bad afternoon is penetration rate tracking updated in near-real time, not an end-of-day summary. When a campaign's available-to-dial leads drop below a threshold, you want to know while there's still time to load new inventory and have it processing before the afternoon push — not the following morning when the opportunity is already gone.
Building that leading indicator requires pulling data Convoso doesn't surface in standard dashboards. A scheduled pull from the API at regular intervals, tracking available lead count by attempt history, gives you the penetration picture as it develops. Cross that with contact rate by lead age and you have a system that surfaces degradation while there's still time to respond.
The second complication is at import time. A list that wasn't scrubbed against existing leads, recent DNC additions, and disconnected numbers before it loaded starts its decay already in progress. Monitoring will surface this — you'll see the contact rate compress faster than expected for a fresh list — but prevention is cheaper than remediation. Import hygiene automation that runs before the first dial is the companion to monitoring that makes the numbers meaningful.
What the Monitoring Layer Looks Like in Practice
A scheduled data pull from the Convoso API capturing campaign-level lead counts, attempt history, and contact rates at regular intervals. This doesn't require a dedicated monitoring platform — the API exposes the data and a scheduled script can collect and log it reliably.
A dashboard that surfaces threshold violations. A Google Sheets integration works for most SMB contact centers: data lands in a structured format, conditional formatting flags penetration thresholds, and a shared sheet gives ops managers visibility without requiring a new tool. Slack alerts on threshold crossings add a push notification for the signals that need immediate attention.
Defined thresholds calibrated to your operation. The metrics that signal a list health problem aren't universal — the right numbers come from your own historical baselines. But the framework is consistent across operations:
- Contact rate significantly below your historical baseline: urgent flag — the list is exhausted or degraded and is burning agent time without result
- Contact rate in a healthy range for your vertical and lead source: the target for a well-managed list with appropriate aging
- Conversion rate below a minimum threshold: list quality problem — leads aren't converting at a rate that justifies continued dialing; source quality or aging is the likely cause
- Conversion rate at or above your operational target: the performance level a fresh, properly sourced list should sustain
Establish your own baselines from the first few weeks of monitored data. The monitoring layer tells you when you're deviating from those baselines — the thresholds you set determine when deviation triggers an alert.
Import hygiene automation. Pre-import scrubbing against your existing lead pool and DNC sources reduces the decay rate before the first attempt. This is prevention rather than monitoring, but it's the step that makes the monitored numbers worth tracking.
Frequently Asked Questions
Does Convoso have any built-in penetration tracking?
Convoso shows attempt counts and disposition breakdowns, but not penetration rate as a campaign-level health metric calculated against total imported leads. You derive it from the data the API exposes — available leads versus total leads in the campaign.
How often does the monitoring need to run?
For most operations, regular intervals give you enough resolution to catch degradation while there's still time to act. Running it more frequently is possible but usually doesn't change the response time meaningfully.
What if we're pulling from multiple lead sources with different quality profiles?
The monitoring should track by source where possible, not just by campaign. A list from one source may have a different expected decay curve than another. Blending them without source tagging makes the contact rate signal harder to interpret.
If You'd Rather Have This Running
I build monitoring layers for contact centers using Convoso and similar platforms. If you want penetration tracking, contact rate dashboards by lead age, and threshold alerting set up correctly — start here: rfditservices.com/intake.html
The first conversation is free.
Top comments (0)