When someone replies STOP, two things must happen: the carrier-level reply is honored, and your own system never texts that number again. A CPaaS can handle the first part at the number level and still leave the second part to you. That difference matters most to a platform sending for many customers.
What the API layer does
On a Twilio-style API, a STOP to a number can make the platform block later sends from that number to that recipient, and a send attempt then fails with an error such as 21610. We explain that error in what to do when Twilio returns 21610. The blocking is per sender and number, though, so a contact who opted out of one number can still be texted from another unless your own code remembers.
That leaves you to build:
- A list of opt-outs you store yourself.
- A check before every send, including bulk and scheduled ones.
- Handling for START and for free-text phrases like "stop messaging me".
- A way to share opt-outs across numbers and campaigns for the same customer.
None of it's hard on its own. Doing it correctly for every customer, forever, is the cost.
What Ready does
Ready honors inbound STOP and UNSUBSCRIBE, and the opt-out applies to the contact across campaigns. It also catches clear phrases such as "do not text me" and "take me off". An opt-out is refused up front on the next send and isn't charged. Your code can read opt-outs with GET /v1/opt-outs and look up one number with GET /v1/opt-outs/:phone. See the docs for the fields.
Be precise about limits:
- The plain
GET /v1/opt-outslist covers opted-out contacts on that account. It leaves out a STOP from a deleted contact and dialer do-not-call entries, so it isn't a complete mirror. Add?scope=allfor the account's whole Ban list. - Odd wording no phrase list catches still needs a person reading replies.
- Ready doesn't store a per-contact consent record from a keyword reply. Keep consent in your own form or CRM.
Side by side
| Task | Typical CPaaS | Ready |
|---|---|---|
| Honor STOP at the number | Yes | Yes |
| Block the same contact across numbers | You build it | Built in at the account level |
| Catch "please stop texting me" | You build it | Clear phrases caught |
| Refuse the send before billing | Depends on setup | Refused and not charged |
| Export opt-outs | Your own store | Opt-out endpoints |
Why it matters at platform scale
One missed STOP is a complaint. A pattern of missed STOPs is a carrier problem and, in the US, can create TCPA exposure for the sender. Compliance stays with the sender either way. Built-in handling reduces the chance of a gap, not the sender's duty. See what a STOP means beyond the keyword.
Frequently asked questions
If I move from Twilio, does my STOP list come with me?
No. Export it yourself and import it before sending. The opt-out history guide walks through it.
Does Ready handle HELP?
Yes, STOP, START and HELP are answered automatically.
The practical takeaway
Decide where the opt-out source of truth lives, then make sure every send path checks it. If you'd rather not own that code, try Ready.