Whitepaper
Aged List Reactivation Without Burning the File
Aged data is expensive inventory sitting idle. Reactivation fails when teams dial harder instead of dialing smarter.
Contents
- Why aged lists get abandoned
- What burn means
- Reactivation model
- Benchmarks
- Compliance
- Evaluation
1 · The problem
Why aged lists get abandoned
Connect rates collapse, teams buy fresh data, and paid inventory dies. Often the process—not only the data—is broken.
2 · Burn
What burning a file looks like
- Over-dial without connect → spam labels
- Wrong ANI → more screens
- Ignoring RND and consent → legal risk
- No recycling logic → same bad order forever
3 · Model
A reactivation operating model
1) Scrub and consent-gate. 2) Score who is worth another attempt. 3) Time attempts. 4) Rotate healthy ANIs. 5) Cap attempts. 6) Feed outcomes back. 7) Hybrid cover for connects that need humans.
4 · Benchmarks
Targets (illustrative)
| Measure | Aged-list target | Note |
|---|---|---|
| First-touch connect | 25%+ | Varies by vertical |
| List penetration | 60%+ | Of workable records |
| CPA | ↓ vs. re-buy | Back into your model |
Pilot goals, not guarantees. Prove on a slice of the file.
5 · Compliance
Constraints that do not flex
Reactivation is not permission to ignore DNC, RND, or expired consent. Gates first—then aggression within policy.
6 · Evaluation
Questions for ops
- What % of aged file is still dialable under policy?
- Attempts-to-connect vs. last quarter?
- Penetration or only dials?
- Would re-buying cost more than fixing the model?