CRM for Detecting and Reactivating Dormant Accounts

Accounts that quietly stop shipping — not formally churned, not cancelled, just gone quiet — are a distinct category from active churn that most CRM processes handle poorly. A dormant account sitting unflagged in the CRM represents lost revenue that nobody is actively working to recover, often because no clear process defines when "quiet" becomes "worth a reactivation effort."

Why Dormant Accounts Slip Through the Cracks

An account that formally cancels triggers a clear process — an offboarding note, maybe an exit interview, a closed-lost or churned status. An account that simply stops shipping without any formal notice often doesn't trigger anything at all. It sits in the CRM with an "active" status because technically the contract hasn't ended, while in practice the relationship has already lapsed. Without a defined dormancy threshold and automated detection, these accounts are only noticed if an account manager happens to check historical volume manually.

Defining and Detecting Dormancy
  • A volume-based dormancy threshold specific to the account's historical shipping pattern — a customer who used to ship weekly and hasn't in six weeks is dormant in a way a naturally infrequent shipper isn't
  • Automated flags when an account crosses its dormancy threshold, rather than relying on an account manager's memory of what "normal" looked like for that account
  • A distinct dormant status separate from active and churned, so reporting doesn't conflate accounts that are quietly gone with accounts that are formally lost
  • Reactivation outreach tracking as its own workflow, separate from new-business prospecting, since the message and context differ significantly
Active shipping Below threshold — flagged Reactivation outreach Won back / formally closed
Reactivation Outreach Needs Different Messaging Than New Business

A dormant account already has a history with the provider — prior service experience, a known reason (even if unstated) for going quiet, and existing rate agreements that may or may not still be relevant. Treating a reactivation outreach as generic cold prospecting wastes the advantage of that history. The CRM should surface the last known shipping pattern, the most recent service or complaint history, and any prior renewal or pricing friction so the outreach can address the likely real reason the account went quiet, not just ask "are you still interested."

Prioritizing Which Dormant Accounts to Chase

Not every dormant account is worth an active reactivation effort — some went quiet because they went out of business or were acquired, others simply switched providers permanently for reasons unlikely to change. Prioritizing outreach by prior account value and by any known reason for the drop-off (versus a total unknown) focuses effort on the dormant accounts most likely to actually respond.

Rollout Notes

Set the dormancy threshold per account or account segment rather than a single company-wide number — a seasonal shipper going quiet for two months might be entirely normal, while the same gap for a weekly shipper is a clear signal.