Who owns the phone number when a client leaves is decided by your contract and by whose account the number sits in, not by who pays the monthly bill. If nobody wrote it down, you'll find out at the worst moment: the client wants their texting line moved on a Friday and you each think it's yours.
This guide is for agencies, white label resellers and the platforms behind them. It covers three separate things people lump together: the number, the carrier registration, and the contact and consent history. We're not lawyers, and this isn't legal advice. Have your own counsel review any contract language before you use it.
Three assets, three different answers
The direct answer: treat the number, the registration and the data as separate assets, and decide each one in writing.
| Asset | What it is | Who usually should hold it | What can go wrong |
|---|---|---|---|
| Phone number | The line customers text | The client, if they use it to talk to their own customers | The agency account holds it and the client can't move it |
| Registration | The brand and campaign approved for the client's business | The client's business identity, filed under the client's own details | The brand is tied to the agency's account and can't transfer cleanly |
| Contacts and history | Contact list, conversations, opt-outs, consent records | The client, as owner of its customer relationships | Opt-outs lost in the move, or consent proof missing |
"Usually should" is a negotiation position, not a rule of law. Some agencies keep numbers as part of a service and say so. What matters is that the client knew before signing.
The number
The direct answer: a number belongs to whichever account holds it, so a client who wants to take it with them needs a port or a transfer that you have agreed to in advance.
On Ready, each customer is a sub-account with its own numbers. That structure makes the cleanest setup possible: the client's number sits in the client's sub-account, separate from every other client's. It also makes the question concrete. When the relationship ends, you decide whether that number is released, ported out, or left to stay with an account the client takes over.
Practical points:
- Put the answer in the contract before the first number is bought.
- Say how long you'll cooperate with a port request after notice, and what you'll charge, if anything.
- Say what happens to the number if the client doesn't claim it: released, held for a set period, or kept.
- A client can't text from a number it doesn't control, so plan the cutover. Our Twilio migration and number port checklist lists the steps that carry over to any move.
Ready's texting runs on local 10DLC numbers and the iMessage blue line. It doesn't sell toll-free numbers.
The registration
The direct answer: a registration is filed for a business, so it should carry the client's own business details, and a clean exit depends on that.
Each Ready sub-account has its own carrier registration (10DLC). Ready registers businesses with an EIN only, and a registration is billed monthly per customer. Most approvals take 2 to 7 days. The registration is the reason a number can send reliably, because unregistered traffic gets carrier-filtered.
Two things to settle in the contract:
- Whose details are on the brand. If you registered under your agency's name for all clients, a departing client has no registration of its own to bring along, and a new platform has to file a fresh one. Our post on A2P 10DLC for agencies explains why per-client registration is usually the safer design.
- Who pays during the notice period. Registration and number charges keep running until the account closes, and the contract should say who covers them.
If the client moves to another provider, expect to register again there. Plan for a gap, and don't promise the client that texting will continue uninterrupted unless you've tested the move.
Contacts, consent and opt-outs
The direct answer: the most important thing to move cleanly is the list of people who opted out, because texting one of them again is the costliest mistake in a migration.
Ready honors STOP and clear opt-out phrases automatically. A new provider doesn't know about those opt-outs unless you hand them over. Export them before the account closes: GET /v1/opt-outs lists the opted-out contacts on a sub-account, and GET /v1/opt-outs?scope=all adds the whole Ban list, including a deleted contact's STOP and dialer do-not-call entries. A STOP held on another account in the same family is only visible through the per-number check, GET /v1/opt-outs/:phone. See the opt-outs docs.
On consent, be careful about what Ready holds. It records the sender's attestation on bulk and API sends, but it doesn't store a per-contact record of when or how someone agreed (a sign-up on a Ready-hosted opt-in page is the exception, and support@tryready.com can send a copy of those). The proof of consent usually lives in the client's form, CRM or your own system, so the contract should say who keeps it and who hands it over.
Then there's message history. The GET /v1/messages list pages through conversations with before_id, so you can export a client's history to give them a copy. Decide how long you keep your own copy afterward, and say it.
A contract checklist
The direct answer: put these questions in your services agreement, answer each one in a sentence, and have a lawyer check the result.
- Which party holds each number, and in whose account?
- Can the client port or transfer a number out, on what notice, and for what fee?
- What happens to unclaimed numbers after termination?
- Whose business details are on the registration, and who is responsible for keeping them accurate?
- Who pays the registration and number fees during notice and wind-down?
- Who owns the contact list, conversations and consent records?
- Within how many days will you deliver an export of opt-outs, contacts and message history?
- In what format, and who pays for it?
- How long will you keep copies after the account closes, and when do you delete them?
- Who is responsible for consent to text each contact? (For most agencies this is the client, and it should say so.)
- What notice is required before either side ends the service?
- For a white label setup, does the client's end customer see your brand, and does that end at termination?
For white label platforms
The direct answer: if you resell Ready under your own brand, you're the agency in this story, and your customers' customers are the client.
The same three assets apply one level down. Your product should make it possible to export a sub-account's numbers, opt-outs and history without a support ticket. Build that export before your first customer asks. Our guide to the white label SMS API covers the architecture, including how sub-accounts keep each customer separate.
Frequently asked questions
Does the agency or the client own the number?
It depends on the account that holds it and what the contract says. Decide it before you buy the number, and write down whether the client can port it out.
Can a client take their registration to a new provider?
A registration is filed for a business with one provider, so expect the new provider to file its own. If it was filed under the client's own business details, that's quick to repeat, and it's a good reason to file per client.
What should I export when a client leaves?
Export the opt-out list, the contacts, the message history and the numbers with their registration status. Opt-outs matter most, since a new provider can't honor a STOP it never saw.
Next step
Open your standard client agreement and answer the twelve checklist questions in it, even if the answer is "the client owns it." Then check that your setup can actually deliver on those answers. If you want to see how sub-accounts keep each client's numbers and registration apart, sign up and set one up, or read the 10DLC explainer first.