Onboard texting as a short pipeline with a visible status for each customer: details collected, sub-account created, registration submitted, number active, first send done. Each step is one API call or one screen, and each can fail on its own, so each needs its own state in your product.

Our post on 10DLC for SaaS platforms explains why every customer needs its own brand and campaign. This one starts after you've accepted that, and covers the work of getting customer number 1 to their first text, then customer number 200.

What does the onboarding pipeline look like?

Five stages, in order, with a status your support team can read at a glance.

StageWhat happensWhere it lives
1. DetailsCollect legal business info and sample messagesYour onboarding form
2. Sub-accountCreate the customer's isolated accountPOST /v1/sub-accounts
3. RegistrationSubmit brand and campaignRegistration API calls
4. NumberBuy or assign a numberPOST /v1/numbers
5. First sendSend a test text, check the resultPOST /v1/messages

Store the stage on your customer record. When someone asks "why can't I text yet?", the answer should be one field, not a debugging session.

What should you collect up front?

The registration needs the customer's legal details, so collect them while they're motivated. That's the business's legal name, EIN, address and website, plus what they'll text and how people agree to it.

Ready registers businesses with an EIN, so a customer without one has to get one first. Ask about it early rather than at submission, because it's the item that stalls onboarding. A sole proprietor can't register on Ready without one.

Also collect two things people forget. First, the sample messages, written in the customer's voice with their business name in them. Second, how their contacts opt in, in plain words. Carriers read both. Consent language that passes registration shows what reviewers look for, and the 10DLC registration API post covers the developer flow in more depth.

How do you create the sub-account and register?

Create the sub-account when the customer turns texting on, then submit their registration through the registration endpoints. Brand and campaign submission and confirmation are separate calls, and you can poll GET /v1/registration for status. The docs list the request shapes at the registration API page, so we won't repeat them here.

Show the status in your UI in plain words: "Submitted," "In review," "Approved," or "Needs changes." Most approvals take 2 to 7 days, so tell customers that up front. A silent wait is the number-one source of "is it broken?" tickets.

Charges for registration start at submission: the first month, $25, with no setup fee. After that it's $25 a month for the brand and first campaign, and $20 a month for each extra campaign. For how to pass that through in your plans, see pricing 10DLC into SaaS plans.

What can the customer do while registration is pending?

They can start in a limited way, which is worth building into the flow. An account can send up to 500 texts a month before it registers, at its normal per-text rate, then it has to register. An account that bought its number before registering sends on Ready's shared registration while its own is in review, at the same per-text rate.

Every text is charged at the normal rate from the first one. A card on file and a number of the account's own are required to send. The number is $2 a month, with the first month charged when it's activated.

So your onboarding can let a customer send a few real texts on day one, instead of staring at a waiting screen.

What goes in the first-send checklist?

Run these checks before you mark a customer as live. Most of the support tickets in the first week trace back to one of them.

  1. Number is active and belongs to the customer's sub-account.
  2. Registration is approved, or the customer knows they're on the pre-registration path.
  3. Opt-in is real. The customer confirms they have consent for the first list they'll text, and your send sets consent_attested only after that.
  4. Test text delivered to the customer's own phone, with their business name in it.
  5. STOP works. Reply STOP from that test phone and confirm the contact is blocked.
  6. Quiet hours are understood. Tell the customer that a text outside the window may be held or refused, and what to do.
  7. Webhook receives the reply, and your inbox shows it.

Ready adds "Reply STOP to opt out" and the business name to the first text to each contact unless the account turns that off, so a first message near the segment limit can tip into a second segment. Check the length in the test.

What breaks at customer number 50?

Manual steps and silent states. A flow your team babysits for ten customers collapses at fifty, so automate the checks and surface the failures.

  • Stuck registrations. Alert on any customer in review longer than the usual window, and on any "needs changes" state nobody's picked up.
  • Refused sends. Show customers why a send was refused (opt-out, quiet hours, invalid number) in plain words. See pre-send refusal error UX.
  • Idempotency. Always send an Idempotency-Key so a retry doesn't double-text a customer's patient or client.
  • Tenant mix-ups. Keep each customer's API calls scoped to their own sub-account.

Who does what: your platform or the customer?

You build the flow and the status screens. The customer supplies true business details and honest consent. Compliance is ultimately the sender's responsibility, and your job is to make doing it right the easy path.

Ready doesn't store a per-contact consent record, so the customer's form or your CRM must keep when and how each person agreed. The hosted opt-in page is the one exception, and it's stored per contact. Plan where that record lives before launch, not after the first dispute.

The practical takeaway

Treat texting onboarding as five stages with one visible status, collect the legal details and sample messages up front, use the pre-registration allowance so customers aren't idle, and gate "live" on a seven-item first-send check.

Start with a single test customer. Create an account, then follow the API quickstart and the sub-accounts docs through the pipeline above.