The safest multi-tenant SMS design gives every customer of your SaaS product its own sub-account, with its own numbers, its own carrier registration, its own opt-out list and its own usage ledger. Share nothing a carrier or a regulator can tie back to another tenant.

This post lays out that design layer by layer, and shows where a messaging API like Ready carries part of the load. We make Ready, so the examples lean on it, but the architecture applies to any provider.

Start with the tenant boundary

One tenant in your product should map to exactly one sub-account at the messaging layer. Store the sub-account ID on your tenant record and never send a text without resolving it first.

The reason is containing the damage. Carriers judge a registered brand and its numbers on the content they carry. If customer A's list draws complaints, the damage should land on customer A's brand and numbers. Customer B's appointment reminders should keep delivering. With Ready, you create and list sub-accounts with POST /v1/sub-accounts and GET /v1/sub-accounts, covered in the sub-accounts docs.

A practical test: if you deleted one tenant tomorrow, could you remove its numbers, registration and history without touching anyone else? If the answer is no, something is shared that shouldn't be. Run that thought experiment on your schema before you write any sending code.

Numbers belong to the tenant

Give each tenant its own numbers and never pool them. A shared number means one tenant's sending reputation bleeds into the others, and an opt-out on a shared number gets ambiguous fast.

Numbers are GET /v1/numbers and POST /v1/numbers. Each number costs $2 a month, and it sits on that tenant's registered campaign. If you turn on local presence, Ready sends from the account's number closest to the contact's area code, and it chooses among numbers the account already has. It doesn't buy or rotate numbers.

Registration is per tenant, and it's the long pole

Every US business texting from a local number needs a registered brand and campaign. The brand is the customer's legal business, not yours. Treat registration as a state machine in your onboarding flow: collected, submitted, in review, approved or rejected.

Ready registers businesses with an EIN only, so a sole proprietor without one can't register. Registration is $25 a month per customer for the brand and its first campaign, and $20 a month for each extra campaign. Most approvals take 2 to 7 days. You can drive it by API with POST /v1/registration/brand, POST /v1/registration/campaign and POST /v1/registration/confirm, and read status at GET /v1/registration or subscribe to the registration_approved, registration_in_review and registration_rejected webhook events. Our 10DLC registration API guide covers the flow and the rejections.

Plan for the slow path as well. A rejected campaign has to go back to the customer in words they can act on, such as a missing opt-in description or a vague sample message. Store the rejection reason on the tenant so your support team can see it without asking engineering.

Opt-outs: scope them on purpose

A STOP always blocks that number in the sub-account that received it. Whether it also blocks the parent and the other sub-accounts is decided by Ready for every account, not by a setting you can change, so don't assume either way. Before a send from another tool, or during a provider migration, check GET /v1/opt-outs/:phone for the answer on one number.

Note that GET /v1/opt-outs lists only opted-out contacts on that account. Add ?scope=all to include the account's Ban list, which holds a STOP from a deleted contact. Only a STOP held on another account of the same agency family needs the per-number check, GET /v1/opt-outs/:phone.

Billing isolation

Each tenant needs its own usage ledger. Meter segments, not messages: a text with one emoji can cost three segments instead of one, and replies bill like sent texts. Itemize carrier fees on their own line so a customer can read the bill.

LayerOne per tenantShared
Sub-accountYesNo
NumbersYesNo
RegistrationYesNo
Opt-out listYesScope set by Ready
Usage ledgerYesNo
API key and codeYour choiceOften shared by the platform

Ready bills $0.0075 a segment plus a $0.0045 carrier fee, $0.012 all-in, excluding screening. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing. See the pricing page for the rest. How you mark up that cost is its own topic, covered in the white label SMS API guide.

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

Sending safely from shared code

Your sending code is the one shared piece, so make it tenant-aware. Three habits help:

  1. Resolve the tenant's sub-account before every send, and fail closed if it's missing.
  2. Send an Idempotency-Key header with a new UUID per text, so a retried job never double-sends.
  3. Set consent_attested only when your own records back it.

Quiet hours add a wrinkle. An API text is held if the window opens within 6 hours and refused with 409 QUIET_HOURS_BLOCK otherwise. Send "hold_until_allowed": true and it is held up to 24 hours instead, with a 202 and a queue_id, so your code needs no resend queue. A reply to someone who texted in the last 24 hours goes out at any hour.

Where this design stops

Be clear about what the platform can't do for you. Compliance remains the sender's responsibility, and Ready doesn't keep a per-contact consent record, so your forms or CRM do. Ready isn't HIPAA compliant and doesn't sign BAAs, so keep health details out of texts. It sends SMS over one provider with no failover between providers, and it doesn't sell toll-free numbers.

If that fits, read about the buyer's side in our SMS API for SaaS platforms post, then try a first send from the API quickstart. You can sign up to get started.