You can launch SMS without building a registration team if your messaging provider files the brand and campaign for each of your customers and exposes that as an API. With Ready, each customer gets a sub-account, and you register that customer through the registration endpoints. We handle the filing. You still own the information you collect and the consent behind every text.
That split is the whole story, and it's worth being exact about it. "We handle registration" can mean three very different things, and the gap between them is where launches stall. Below is what the work really involves, what Ready does for you, and the parts no provider can take off your plate.
What carrier registration actually asks of a platform
In the US, business texting on local numbers runs through 10DLC. Each business that sends registers as a brand, and then registers a campaign that describes what it will text and how people opt in. If you want the background, start with what 10DLC is. Unregistered traffic gets filtered by carriers, so it isn't optional once you send real volume.
For a platform, the weight comes from multiplication. You don't register once. You register once per customer, because the customer is the business doing the texting. That means:
- Collecting legal business details from every customer.
- Collecting a clear description of what they'll send and how recipients opt in.
- Submitting, tracking, handling a rejection and resubmitting.
- Doing all of it in your onboarding flow, so a new customer isn't sent off to a carrier portal.
If you do that by hand, it becomes a support queue. If you do it through an API, it becomes a step in your product.
What Ready handles
Ready sits on a messaging provider's connections and does the registration filing as part of the account. In practice:
- A sub-account per customer. Each customer has its own numbers and its own registration. You create it with
POST /v1/sub-accounts. See the sub-accounts docs. - Registration by API.
POST /v1/registration/brand,POST /v1/registration/campaignandPOST /v1/registration/confirmsubmit it, andGET /v1/registrationreads its status. The field-level details are in the registration docs, and we don't reproduce them here so this post doesn't drift from the docs. - Self-serve filing. Filling it in takes a few minutes, and most approvals take 2 to 7 days.
- No setup fee. The charge at submit is the first month, $25. After that it's $25 a month for the customer's registration (the brand and its first campaign), $20 a month for each extra campaign, and $2 a month per number.
- Messaging protections once registered. Automatic STOP handling, quiet-hours enforcement, number validation and TCPA and Do Not Call scrubbing sit in the same API.
For the walkthrough of the flow, see our 10DLC registration API guide and the developer-oriented registration flow post.
What stays your responsibility
This is the section to read twice, because the marketing version of "we handle it" skips it.
| Area | Who owns it |
|---|---|
| Filing the brand and campaign with the carrier network | Ready, from the details you submit |
| Collecting accurate legal business details from your customer | You |
| Describing the use case truthfully, with sample messages that match real traffic | You |
| Getting recipients' consent, and keeping the record | You (the sender) |
| Keeping message content inside the registered use case | You |
| Deciding which of your customers you'll onboard | You |
| Compliance overall, including the TCPA | The sender, with tools from us that reduce risk |
A few specifics worth spelling out:
- Consent is yours.
consent_attestedon a send is your promise the recipient agreed to texts. Ready records that attestation per send, but it isn't a per-contact consent record: Ready stores no per-contact opt-in time, wording or page URL, so you keep that in your own form or CRM. (A sign-up on a Ready-hosted opt-in page is the exception, and that one is stored per contact.) Our guides on documenting SMS consent and a consent record schema show how to build it. - Accuracy matters more than speed. A campaign whose description doesn't match what the customer sends gets throttled or rejected later. Treat your onboarding form as the quality gate.
- Ready registers businesses that have an EIN. A customer who is a sole proprietor without one can't register through Ready. Plan an alternate path for those customers, such as getting an EIN first, or not offering texting to them.
- Health information stays out of texts. Ready isn't HIPAA compliant and doesn't sign BAAs.
Building the onboarding step
Here's the shape of an onboarding flow that keeps registration inside your product. It stays at the level of the endpoints we can name.
- Create the sub-account when the customer turns texting on.
- Collect the business details in your own form, with validation for the fields you know are common causes of rejection: legal name that matches the tax record, a real website, a real use-case description.
- Submit the brand and campaign through the registration endpoints, then confirm.
- Show status in your UI by reading
GET /v1/registration, and tell the customer plainly that texting to recipients waits on approval. - Buy or assign a number with
POST /v1/numbersonce the customer is ready to send. - Hold your first sends until the registration is through, except for the small number of texts an unregistered account may send. An account can send up to 500 texts a month before it registers, and after that it has to register.
Every text is charged at the account's normal per-text rate from the first one, a card on file is required, and a number of the account's own is needed to send. Surface that in your pricing page so customers aren't surprised. For the broader launch picture, see SMS API for vertical SaaS onboarding, and for how long customers wait, how long 10DLC takes.
What to decide before you start
- Who pays for registration: you, or the customer through your pricing. The fees are per customer, so model them against your plan prices. Our SaaS 10DLC fixed-cost pricing post works through that math.
- What you do when a customer is rejected: who contacts them, and what the fix flow looks like.
- What you do with a customer who can't register: the sole proprietor case above.
- Whether you need extra vetting. Optional brand vetting costs $79 Standard or $179 Enhanced, one time, and only matters for higher-volume senders. Standard registration is all most senders need.
Frequently asked questions
Can my customers skip registration?
Not for sustained business texting on local numbers. Unregistered traffic gets filtered by carriers. An account can send a small number of texts a month before it registers, but after that it has to register.
Does Ready take on my compliance obligations?
No. Compliance is the sender's responsibility. Ready's scrubbing, STOP handling and quiet-hours enforcement reduce risk, and they don't make a sender immune to a TCPA claim.
Do I need to talk to carriers myself?
No. You submit through Ready's registration endpoints, and we file it. Ready is a layer over a messaging provider, not a carrier itself.
Next step
If you're mapping the launch, create a sub-account in a test run, submit a registration for a real business of your own, and time the flow end to end. The registration docs cover the request details, and pricing lists the figures in full.