Before you launch texting in your SaaS, make sure every customer is registered for 10DLC, every recipient has agreed to be texted, opt-outs are honored automatically, and you can prove all of it later. That's the short version. The longer version is a checklist of about a dozen items, and this post walks through them in the order a launch team hits them.

This isn't legal advice, and compliance is ultimately the sender's responsibility. What follows is risk reduction and good practice, written for the CTO or head of product who has to decide what the platform enforces and what it leaves to each customer. Penalties under the TCPA run $500 to $1,500 per text, which is why it's worth doing this before launch, not after.

1. Decide who the sender is

In a platform, your customer is the sender and you're the one who built the pipe. That split matters for registration, consent and liability. Each customer is a separate business with its own brand, its own recipients and its own opt-in records. Write down which duties sit with you (enforcing quiet hours, honoring STOP, rejecting unregistered traffic) and which sit with the customer (collecting consent, writing honest copy). Our post on the agency and client liability split draws the same line for agencies.

A sub-account per customer is the clean way to enforce this. On Ready, each customer gets a sub-account with its own numbers and carrier registration, so one customer's problem doesn't touch another's.

2. Register every customer for 10DLC

Texting US numbers from a local number requires carrier registration: a brand, and a campaign that describes what the messages are. Unregistered traffic gets carrier-filtered, so skipping this step means texts that quietly don't arrive.

On Ready, brand and first campaign registration is one line at $25 a month per customer, each extra campaign is $20 a month, and each number is $2 a month. Most approvals take 2 to 7 days. Ready registers businesses with an EIN only, so a customer without one can't register. Build that into your onboarding so you ask for the business details early. The 10DLC registration API post shows how to do it in code, and what 10DLC is is the plain-English version.

3. Get consent, and keep the evidence

Texting someone who never agreed is the core TCPA risk. The recipient should opt in to the kind of messages you'll send, in words that make that clear, and the customer should keep a record of when and how.

Here's what Ready records and what it doesn't. On an API send that sets consent_attested, Ready records the sender's attestation: who sent, to how many, and when. That builds an audit trail, but it isn't a per-contact consent record. Ready stores no per-contact consent for those sends, so the customer keeps it in their form or CRM. (The exception is a sign-up on a Ready-hosted opt-in page, which is stored per contact with time, IP and exact wording.) An API send without consent_attested still goes out today, with a warning and no attestation, so make your platform set it, and set it only when it's true. See opt-in wording examples for copy that holds up.

4. Handle opt-outs without a human

A recipient who texts STOP must stop receiving texts. Ready honors inbound STOP and UNSUBSCRIBE automatically and carries the opt-out across campaigns, and it catches clear phrases such as "please stop texting me" and "take me off". Odd wording no list catches still needs a person reading replies, so keep the inbox visible to the customer.

On the API side, opted-out numbers are refused up front and not charged. If you send from another tool, or you're migrating from another provider, check GET /v1/opt-outs/:phone before you send, since the list endpoint doesn't cover every case. Our opt-out API post has the details.

5. Respect quiet hours

Texts shouldn't land at night in the recipient's time zone. Ready enforces quiet hours by the recipient's area. Campaigns, drip campaigns and automations wait up to 24 hours for the window. An API text is held only if the window opens within 6 hours, and otherwise it comes back as a 409 QUIET_HOURS_BLOCK, so your code has to retry later. A reply to a contact who texted the account in the last 24 hours can go out at any hour.

Some states set stricter windows than the default, so check the rules where your customers' recipients live. Our state-by-state compliance post is a good starting map.

6. Scrub for litigators and Do Not Call

Known TCPA-litigator and Do Not Call numbers can be screened out before a send. On Ready the scrub reports matches, and it blocks sends only on accounts with send-time scrubbing turned on. Screening is charged $0.003 per segment for each of Scrub lists and Number validation when switched on, and the standalone scrub is $0.005 per contact. Decide whether your platform turns it on by default for customers who buy lists or collect numbers at scale.

7. Keep the content clean

Registration describes what you'll send, and the messages should match it. Beyond that:

  • Identify the business in the message.
  • Include opt-out language. Unless the account turns it off, Ready adds "Reply STOP to opt out" and the business name to the first text to each contact.
  • Keep protected health information out of texts. Ready isn't HIPAA compliant and doesn't sign BAAs, so a reminder like "Your results are ready, please log in." is fine and a diagnosis isn't.
  • Watch for restricted categories. Advocacy, political and fundraising texts need Ready's written OK first, so email support@tryready.com before the first send and wait for our reply.
  • Be careful with links, which draw carrier scrutiny; see carrier filtering and public shorteners.

8. Plan for the audit

When someone complains, you'll need to show consent, registration, the message that was sent and the opt-out that was honored. Log them in one place per customer. Keep message history, attestation records, your own consent records and the registration details. Write down your retention policy before launch, and tell customers where each record lives so they aren't surprised.

The checklist on one page

ItemWho owns itDone when
Sub-account per customerPlatformEach customer has own numbers and registration
10DLC brand and campaignPlatform and customerApproved before volume sends
Consent captureCustomerRecord is kept and attestation set
STOP handlingPlatformOpt-outs block sends, tested
Quiet hoursPlatform409 handled in your code
Litigator and DNC scrubPlatform settingPolicy decided for each account
Content rulesCustomerMessages match the registered campaign
Audit logBothEvidence retrievable per customer

Mistakes that show up at launch

Most launch problems are ordering problems. Teams build the send button first and the guardrails later, and then the first customer imports a list before anyone has decided what counts as consent. A few patterns are worth ruling out early:

  • Letting a customer send before registration is approved. Ready lets an account send up to 500 texts a month before it registers, and after that it has to register.
  • Treating cold lists as normal practice. Cold contact is by phone and mail. SMS should go to people who consented or who replied.
  • Setting consent_attested to true in code regardless of the situation. The flag is the customer's promise, so wire it to a real consent field.
  • Forgetting that replies cost money and carry duties. A STOP, a HELP and an angry reply all arrive in the same inbox.

The practical takeaway

Compliance at launch is mostly a set of defaults you choose. Make registration part of onboarding, make consent attestation mandatory in your own API calls, handle STOP and quiet hours in code, and keep records where you can find them. Ready handles registration, opt-outs, quiet hours and screening on its side, and the SMS API for SaaS platforms post covers how a platform ties those together. When you're ready to try it, pricing has the current figures.