The business that sends the text is responsible for having consent to send it, and that stays true when software sends it for them. A platform can still end up in the dispute, though, so the useful question is how to shrink the risk for both sides. This isn't legal advice. Talk to a lawyer about your own setup.
If your product lets customers text their own contacts, you sit in the middle. Your customer chose the recipients and wrote the message. Your code sent it. Plaintiffs, carriers and regulators don't always stop at the first name they find. Here's how the pieces fit, and what you can control.
Who is responsible for what
Think in three layers: consent, registration and the platform's own conduct.
| Layer | Who owns it first | Where the platform gets pulled in |
|---|---|---|
| Consent to text (TCPA) | The customer who collected the opt-in | The platform built or ran the feature that sent without checking |
| Brand and campaign registration (10DLC) | The business that sends, as the registered brand | The platform submitted false or vague details, or let one customer's traffic ride on another's registration |
| Opt-out handling | Both | The platform's code ignored or lost a STOP |
| Message content | The customer | The platform supplied templates, or knew the content was a problem |
The pattern is simple. The sender owns the consent. The platform owns what its own product does with that consent claim.
Consent: the sender's job, the platform's record
Under the TCPA, a marketing text needs the recipient's prior express written consent. Statutory damages are often cited at $500 to $1,500 per text, which is why a single bad list matters. Our plain-English TCPA rules for texting walks through what counts as consent.
A platform can't verify a customer's opt-ins from the outside. What it can do is make the customer say, per send, that they have consent, and keep a record. On Ready, an API send can set consent_attested, and the attestation is recorded with who sent, to how many and when. Until January 20, 2027 (UTC), an API send without it still goes out with a warning and leaves no attestation. From that date it's refused with 403 api_consent_attested_required.
Be honest with your customers about what that record is. It's an attestation, not proof of each contact's opt-in. Ready doesn't store a per-contact consent record. The sender keeps that in their own form or CRM. (The one exception is a sign-up on a Ready-hosted opt-in page, which is stored per contact.)
Registration: tell the truth, one brand per sender
Carriers expect the registered brand to be the business actually sending. When a platform texts for many customers, the clean structure is one registration per customer, filled in with that customer's real business details. Pooling everyone under the platform's brand blurs who's responsible and puts every customer at risk when one misbehaves.
Ready gives each customer a sub-account with its own numbers and carrier registration for this reason. Our guide to 10DLC for SaaS platforms covers the structure. Whatever you use, don't submit made-up descriptions or sample messages. A rejected campaign is an inconvenience. A misrepresented one is a bigger problem.
What a platform can do to reduce its exposure
None of these make you immune. Each one lowers the odds and strengthens your position if something goes wrong.
- Know your customer. Collect real business details before enabling sending. See our post on know-your-customer for SMS sub-accounts.
- Require consent attestation on every API send and keep the record.
- Honor opt-outs automatically. A STOP always blocks that number in the sub-account that received it. Check
GET /v1/opt-outs/:phonebefore sending from another tool or after a provider migration. - Enforce quiet hours based on the recipient's area rather than trusting each customer to schedule correctly.
- Screen for litigators. Known TCPA-litigator and DNC numbers can be flagged or blocked before send, if you switch that on.
- Put it in your terms. Your customer agreement should say the customer is the sender, warrants consent, and indemnifies you. A lawyer should write that clause, not a blog post.
- Keep the ability to pause. Be able to suspend one sub-account without touching the others.
What Ready can't take off your plate
Ready records attestations, handles STOP, holds texts for quiet hours and offers litigator scrubbing. It doesn't make consent valid. If your customer's list was bought or scraped, no platform feature fixes that, and compliance remains the sender's ultimate responsibility. Ready also isn't HIPAA compliant and doesn't sign BAAs, so keep health details out of texts.
Cold contact is another line. Texting goes to people who consented or replied. Cold outreach belongs on phone and mail. Don't build a product feature that invites cold-list texting and hope the attestation covers it.
A short way to explain it to customers
Customers read terms rarely and onboarding screens often. Put the split where they'll see it:
- You own your contact list and your proof of consent.
- We record your attestation on each send and stop texts to anyone who opts out.
- We reserve the right to pause sending if complaints spike or registration is rejected.
That is honest, short and promises no protection nobody can give. (Your own terms should back up point 3.)
The takeaway
Responsibility starts with the sender, and a platform earns its share by what its product allows. Reduce that share with real business details at signup, per-send consent attestation, automatic opt-outs and a way to pause one customer. For a launch-ready list, use our SMS compliance checklist for SaaS. When you want to see how sub-accounts and registration fit together, start with the registration docs.