Somewhere in a suburb, a man named Dennis gets a new phone number. By Thursday he has received three texts asking whether the dental cleaning is still on for Friday.
Dennis does not have a dentist appointment. Dennis, as far as he can tell, does not have a dentist. What Dennis has is the old number of someone's appointment-reminder agent, retired a few weeks earlier and quietly handed back to the pool.
This is the number graveyard. It is bigger than most builders realize, and it is getting more crowded.
Numbers are rented, never destroyed
A phone number is not a file you delete. It is a finite resource that goes back into circulation. After a number is disconnected, carriers generally hold it for a while and then make it available again to someone new. In the United States there is even a Reassigned Numbers Database, because the problem of "this number now belongs to a different person" is common enough that regulators built infrastructure around it.
For humans, that recycling is a mild annoyance. You get a number that used to belong to someone named Carol, and for a few months you receive her pharmacy texts.
For agents, three things make it worse.
Agents retire numbers far more often. Rotating numbers is a common reaction to reputation trouble. If your agent's number gets flagged, the reflex is to throw it away and buy another. Across a fleet, that is a steady stream of numbers headed for the graveyard.
Agents contact far more people. A person might have a few hundred contacts. An agent running outreach may have touched thousands. Each of those people still has the old number saved, still has the old thread, and may still reply to it.
Agents leave a louder footprint. A number with a long history of automated traffic has a reputation, good or bad, and that reputation does not reset the moment you stop paying for it.
The three hauntings
1. The ghost caller. Your agent's old number goes to someone new. Customers keep calling it, because it is the number on their invoice, in their contacts, on the card your agent texted last spring. The new owner picks up and hears: "Hi, is this Fern from Acme?" They are not Fern. They are not at Acme. They are annoyed.
2. The wrong-number texts. The inbound stream does not stop when you stop listening. Replies, "STOP" requests, and confirmations all land on a line you no longer control. The "STOP" is the dangerous one: a customer who opted out has had their request delivered to a stranger, and your system never learned it.
3. The inherited score. Spam-labeling systems score numbers over time. If your retired number was flagged as "Spam Risk," the next owner may inherit that label. Their first calls to the pharmacy go unanswered, and they will never know why. Reputation is tied to the number, not to the person who currently holds it.
> The cruel symmetry: the number you burned becomes someone else's problem, and the number you adopt may be someone else's burned number.
Quarantine as a design idea
If you operate numbers at scale, the graveyard deserves a lifecycle, not a trash can. One way to think about it is a simple state machine:
active -> draining -> quarantined -> releasedIllustrative states, not a real API:
And in the other direction, a good provisioning flow should be suspicious of numbers on the way in. A number that comes with an ugly history is a liability you are buying.
The details of how long each stage should last depend on the carrier, the region, and how heavily the number was used. The principle does not: retiring a number is an operation with a tail, not an event.
Why number-per-agent fills the graveyard fastest
Here is the uncomfortable engineering point. If every agent gets its own dedicated number, then:
You are running a number farm and a cemetery at the same time.
The approach the whitepaper argues for is different. Agent identity is anchored in an identifier that is not a phone number, the Agent Communication Number, and phone numbers become one channel among several that the identity can use. Reputation is tracked per identity. Volume can be spread across pooled infrastructure rather than concentrated on one fragile line. When a number does have to be retired, the identity persists, so the conversation history and consent records do not die with it.
That does not make the graveyard disappear. Numbers still get recycled somewhere. But it means retiring one is routine, not a crisis, because nothing important was welded to it.
What you can do today, whatever stack you use
The takeaway
A phone number is a loan, not a gift. Treat the end of its life with the same care as the beginning, and design so that your agent's identity does not die in the graveyard along with it.
This is the kind of lifecycle problem that Dial handles at the infrastructure layer, so that your agent can keep its identity while the plumbing underneath changes.