When your customers text through your product, your terms of service are the first line of defense and your acceptable use policy (AUP) is the second. Most platforms bolt a paragraph about messaging onto a generic contract and hope for the best.

A clear SMS section does more. It tells customers what they own, gives you a lawful reason to pause a sender, and lines up with what your messaging provider expects of you. This guide covers what to include. It's general information, not legal advice, so have your lawyer review the final text.

Why do platforms need SMS-specific terms?

Generic terms say "don't break the law." That's true and useless at 2 a.m. when a sub-account is sending something that will get your registrations flagged.

Specific terms give you three things:

  • A documented duty on the customer, so consent isn't ambiguous.
  • A defined list of banned content, so enforcement isn't a debate.
  • A right to act fast, so suspension isn't a breach on your side.

They also carry weight with carriers and providers. Registration reviewers read websites, privacy policies and terms. Our post on 10DLC website, privacy policy and terms requirements covers what they expect from the sender's own pages.

What should the consent clause say?

Start with who owns consent. The customer, as the sender, is responsible for getting permission before texting anyone, and for keeping proof. Put that in plain words.

A workable consent clause covers:

  • The customer represents that every recipient has agreed to receive the texts, in the form the law requires for that message type.
  • The customer keeps records of that agreement and produces them on request within a stated time.
  • The customer honors opt-outs, and doesn't re-add someone who has said stop.
  • The customer won't text purchased, rented or scraped lists.

Compliance is the sender's ultimate responsibility, and your terms should say so without hedging. That doesn't remove your operational risk, which is why you add the clauses below. For the liability split in more detail, see agency and client compliance liability.

If you capture consent in your own product, link the customer to guidance on documenting SMS consent.

What content should you prohibit?

List categories outright. Short, concrete bans are easier to enforce than vague ones. Here's a starting list to adapt:

CategoryExample of what to ban
Deceptive messagesPhishing, fake invoices, impersonating another brand
Illegal goods or servicesAnything unlawful where the recipient lives
Harassment and threatsAbusive or repeated unwanted contact
Unconsented marketingPromotions to people who never opted in
Protected health informationDiagnoses, medications, test results in a text
EvasionSnowshoeing across numbers, hiding the sender's identity
Regulated sensitive topicsItems your provider or carriers restrict

On health data: Ready isn't HIPAA compliant and doesn't sign BAAs, so a platform building on it should bar protected health information from texts. Reminders without the sensitive detail are fine, such as "Your results are ready, please log in."

For regulated topics, point to a short list and say you may add to it. Political, advocacy and fundraising texts are a good example of a category to handle by exception. Ready's own acceptable use policy asks senders of those to get written approval first, and a platform building on Ready would be wise to add a matching step for its own customers.

When can you suspend a sub-account?

This is the clause you'll be glad you wrote. Say you may suspend or limit a sub-account, with or without notice, when:

  • A carrier, a provider or a regulator asks you to.
  • Complaint or opt-out rates suggest the customer lacks consent.
  • Messages break the prohibited content list.
  • The customer won't provide consent records you've asked for.
  • You reasonably believe the account is being used for fraud.

Then describe what happens next. Be specific about notice, a way to respond, and what you'll do with the customer's data. Our post on handling SMS opt-outs is a useful companion for the part about stop requests that must keep working even when an account is suspended.

A tiered approach helps. A first problem might get a warning and a request to fix it within a stated window. Fraud or an urgent carrier demand skips straight to suspension.

How should pass-through fees and fines be handled?

Money clauses are where platforms get surprised. Decide in advance and write it down:

  1. Carrier and messaging fees are passed through to the customer at cost, or at the markup you've disclosed.
  2. Registration and number charges are the customer's, including recurring ones.
  3. Fines, penalties or surcharges a carrier or provider assesses because of a customer's traffic are the customer's.
  4. Charges for texts sent are owed even if the messages were blocked or filtered after the send, when that's how your own bill works.
  5. Disputes about usage have a deadline.

Ready itself bills the carrier fee as a separate line, passed through at cost, and the bill calls it the carrier fee. Mirroring that in your invoices makes the pass-through easy to understand. See our post on 10DLC fines and enforcement for where penalties come from.

Add an indemnity too: the customer covers claims that arise from their messages, including consent claims. Your lawyer will want to shape that language.

What else belongs in the policy?

A few smaller clauses cover the gaps:

  • Contact details for abuse reports. Give a monitored address for people who get unwanted texts.
  • Cooperation. The customer agrees to answer your questions and provide records during an incident.
  • Changes. You may update the AUP, with notice, as carrier rules change.
  • Data. Say what you keep and for how long. Our post on SMS data retention covers that.
  • Numbers. Say what happens to a customer's numbers when the account ends. See phone number release and recycling.

Keep the document readable. A customer who understands the rules breaks them less often, and a policy you can summarize in a page is one your support team can actually enforce.

Frequently asked questions

Do I need a separate SMS policy, or can it live in my terms?

Either works. Many platforms put the legal duties in the terms and keep a shorter acceptable use policy as a linked page, so it can change without a full contract update. What matters is that the customer accepts it and that you can point to the acceptance.

Should the terms require customers to follow carrier rules?

Yes. Say the customer must follow the rules of the carriers and your messaging provider as they change, and give yourself the right to act when those rules require it. That keeps your commitments to your provider and to your customers in step.

Can a platform copy another company's AUP?

Copying won't fit your product, and it may breach the other company's copyright. Use public policies as a checklist for topics, then write your own version and have a lawyer review it.

The practical takeaway

Good SMS terms do four jobs: they put consent on the customer, list what's banned, give you a clean right to suspend, and settle who pays for fees and fines. Write them in plain words, then have counsel review them.

When you're ready to see how the registration side lines up, read 10DLC for SaaS platforms and the KYC checklist for sub-accounts.