When a customer cancels, their texting numbers don't vanish. Someone else will eventually own them, along with whatever history the number carries: contacts who still text it, opt-outs, spam labels and registration ties.

Phone number recycling is easy to ignore until a new owner starts getting replies meant for a stranger. This post covers what happens to numbers at the end of a customer's life on your platform, and the policy to write before it matters.

What is phone number recycling?

Recycling means a number that one party stopped using is later given to another. It happens at two levels, and platforms touch both.

  • Consumer numbers. A person gives up a mobile number, the carrier holds it for a while, then assigns it to someone new. Your customer's contacts are these numbers.
  • Business texting numbers. A platform releases a number it rented for a customer, and the provider returns it to a pool that a different customer or platform can later get.

The first creates the reassigned number problem: you text a stored number, and it now belongs to a stranger who never agreed. Our guide to the Reassigned Numbers Database covers the consumer side in detail.

The second is the part a platform controls directly, and it's the focus here.

What happens when a customer cancels?

The moment a customer leaves, you face four decisions at once. Write the answer to each in advance.

  1. Do the numbers stop sending immediately, or after a wind-down period?
  2. Do you release the numbers, hold them, or let the customer port them out?
  3. What happens to the contacts, messages and opt-outs tied to those numbers?
  4. What do you owe the customer if people keep texting those numbers?

Skipping this leaves you improvising. A common failure is releasing numbers the same day, then fielding messages from the customer's own contacts for months, now arriving at someone else.

What are the risks of releasing a number?

Releasing is cheap for you and risky for everyone else. Here are the main ways it goes wrong.

RiskWhat happens
Misdirected repliesThe old customer's contacts text the number, and the new owner receives them
Lost opt-outsA contact who said stop on the old number gets texted by the new owner
Reputation carry-overA number flagged as spam keeps the label for its next user
Registration mismatchA number tied to a cancelled brand can send under stale details
Customer surpriseThe customer wanted to keep the number, and it's gone

The third one deserves a note. If you ever sent poorly from a number, that history can follow it. Our post on why a number shows up as spam explains how labels attach to numbers.

None of these risks is a reason never to release. Numbers cost money to hold, and holding them forever isn't a policy. They're a reason to release deliberately.

What does a good release policy look like?

This is general guidance, not a description of any one provider. Adapt it to your contracts and counsel.

Give the customer a clear exit window

Tell customers up front how long they have after cancellation to ask for their numbers. Thirty days is a common starting point, but pick a window your operations can honor. During that time the numbers stay assigned, don't send, and can be ported out if the customer wants them.

Quarantine before release

After the exit window, hold the number for a quiet period before it returns to a pool. The purpose is to let stray traffic fade: contacts stop texting a number that never answers, and the number's recent reputation resets. A longer quiet period costs a little more and prevents most of the misdirected-reply cases above.

Stop all sending first

On cancellation, block outbound messages from those numbers the same day. A cancelled account shouldn't be able to send campaigns while it winds down. Inbound can keep arriving so you can handle it, but nothing should go out.

Release only when the number is clean of obligations

Before you release, confirm:

  • No open balance that you'd need the number for.
  • No pending port request.
  • The registration tied to the number has been detached or closed on your side.
  • The opt-out history has been exported or archived.

Record every release

Log the number, the sub-account, the date, who requested it and why. When someone later asks why a number stopped working, you can answer in a minute.

What happens to opt-out history?

This is the most important part of the policy, and the easiest to lose.

A STOP is a legal and carrier-level signal. If a contact opted out of a customer's texts, that contact should stay opted out when the customer leaves, especially if the customer moves to another platform. On Ready, a STOP always blocks that number in the sub-account that received it, and GET /v1/opt-outs/:phone checks one number, with the docs at opt-outs.

Practical steps for a platform:

  • Offer the customer an export of their opt-outs before their data is removed.
  • Keep an archive of opt-outs tied to the customer's record for a defined period, so a returning customer isn't starting from zero.
  • Tell customers moving elsewhere to carry the list over. Our guide to preserving opt-out history in a Twilio migration walks through the idea, and the same logic applies to any move.

What about the number's new owner? A new customer shouldn't inherit the previous customer's opt-outs, because the opt-outs belong to the old sender relationship. They also shouldn't send to the old customer's contacts on the strength of an old conversation, which was never theirs. A clean quarantine and a fresh number history avoid both problems.

What about the contacts who keep texting the old number?

Someone will. Customers' contacts save the number and use it for years.

Decide who handles this and tell the customer:

  • During the exit window, inbound messages are still delivered or stored so nothing is lost.
  • After release, the platform doesn't promise to forward anything.
  • The customer should tell their contacts about the new number before cancelling.

A message such as "This number is no longer in service for that business" is one option for inbound traffic during a short quiet period. Check with counsel and your provider before automating replies from a number you no longer manage.

How do you reduce reassigned-number risk on your side?

Releasing numbers carefully protects strangers. Protecting your customers from texting strangers is the other half.

  • Validate numbers before sending. Ready's number validation endpoint is GET /v1/validate/:phone, covered in the validation docs.
  • Check the opt-out list for the number before a send from another tool.
  • Ask customers to remove contacts who report a wrong number, and honor "wrong number" replies as a stop.
  • Keep consent records with dates, so a customer can show when the person agreed.

Our guide to SMS phone number rotation covers a related question for platforms that move customers between numbers on purpose.

Frequently asked questions

How long should a platform hold a released number?

There's no universal number, and the right quiet period depends on your provider's pool rules and your own contracts. A common approach is an exit window for the customer followed by a further quiet period before the number returns to a pool. Ask your provider what it does after you release, and size your policy around that.

Can a new owner receive the old owner's text messages?

Yes, if contacts keep texting a released number, the new owner gets those messages. That's the main reason to quarantine numbers and to tell customers to notify their contacts before they leave.

Do opt-outs follow a number to its next owner?

They shouldn't, because an opt-out belongs to the relationship between a contact and the sender, not to the number. Keep the old customer's opt-out history with that customer, and give the next owner a clean start.

The practical takeaway

Treat number release as a process with four steps: a customer exit window, a sending stop, a quarantine and a logged release. Keep the opt-out history safe through all of it.

If you're writing the paperwork that goes with this, read our guides to SMS terms for your platform customers and SMS data retention.