Twilio error 21610 means the person you're texting replied STOP (or a similar keyword) to the number you're sending from, so the provider blocked the message. The message never goes out. It's the system working as intended, and the fix is to stop texting that contact from that sender.

The response will usually read "Attempt to send to unsubscribed recipient". If you're seeing it in volume, the real problem isn't the code. It's that your own system doesn't know who has opted out.

Why 21610 happens

When someone texts STOP, STOPALL, UNSUBSCRIBE, CANCEL, END or QUIT to a number, the messaging provider records the opt-out for that sender and that recipient. Every later send from that number to that contact is rejected with 21610. The block is tied to the pair, so a different sender number can reach the same person unless your own rules say otherwise.

That pairing matters for your product. If your platform sends from several numbers, the provider only protects you on the number that got the STOP. Your own opt-out list has to cover the rest.

Causes worth checking

SituationWhat happenedWhat to do
Recipient replied STOPNormal opt-outMark the contact as opted out in your database
Your app never read the STOPInbound webhook missing or failingFix inbound handling so STOP reaches your records
Bulk list importA list included people who had opted out earlierCheck the list against your opt-out records before sending
Another number sent firstThe contact opted out on a different senderDecide your scope rules and honor them
Contact replied by mistakeWanted to stop one thread, not everythingWait for them to text START, don't resubscribe them yourself

How a contact resubscribes

The standard way back in is for the contact to text START, UNSTOP or YES to the same number. Once they do, sends work again. You can't clear the block on their behalf, and you shouldn't try to. A STOP is the person's decision, and texting around it is a compliance problem, not a technical one.

A checklist to fix it

  1. Don't retry. A 21610 will not clear on a second attempt.
  2. Record the opt-out on your side. Treat the failure as a signal and mark the contact as unsubscribed in your own data.
  3. Check your inbound path. If STOP replies aren't reaching your system, you'll keep hitting 21610 until they do. See receiving SMS with inbound webhooks.
  4. Screen lists before each send. Compare every list against your opt-out records, including opt-outs from other tools you used before.
  5. Suppress across senders. Decide whether one STOP blocks the contact on all your numbers. The safer default is yes.
  6. Show the user why. If you're a platform, tell your customer "this contact opted out" and not "send failed".
  7. Keep the record. Opt-out history is evidence if you're ever asked about it. Keep it, even for deleted contacts.

For the full picture of handling STOP properly, our guide to handling SMS opt-outs goes deeper, and SMS opt-out management covers the data side.

What about messages that look like opt-outs but aren't?

Not every reply is a clean keyword. People write "please stop texting me" or "take me off your list". Carrier-level keyword handling only catches the standard words, so the free-text replies are left to you. If your system ignores them, you'll keep texting someone who asked you to stop, and that's the kind of thing that ends in a complaint. Our post on reply keywords that aren't STOP covers how to handle these.

How this shows up on Ready

On Ready, an opt-out is honored before the message goes anywhere. Opt-outs and numbers on your Ban list are refused up front and not charged, so you get a refusal at send time and not a carrier error after the fact. A STOP always blocks that number in the sub-account that received it. Whether it also blocks the parent account and the other sub-accounts is decided by Ready, so check the per-number status when it matters.

Ready also recognizes clear free-text opt-outs, such as "please stop texting me" or "do not text me", and not only the single keywords. Odd wording that no list catches still needs a person to read the replies.

You can read opt-out state through the API:

  • GET /v1/opt-outs lists opted-out contacts on the account.
  • GET /v1/opt-outs/:phone checks one number.
  • GET /v1/opt-outs?scope=all adds the account's whole Ban list.

The plain list leaves out some entries, such as a STOP from a deleted contact, so it isn't a complete mirror. If you're migrating from another provider or sending from a second tool, check GET /v1/opt-outs/:phone before you send. The details are in the docs at https://docs.tryready.com/api/opt-outs, and error handling is at https://docs.tryready.com/api/errors.

If you're moving off Twilio, bring the history with you. Preserving opt-out history in a Twilio migration walks through it.

The short version

Twilio 21610 is a recipient's STOP doing its job. Don't retry, record the opt-out in your own system, make sure inbound STOP replies reach you, and screen every list before you send. The only way back is the contact texting START. For the wider set of codes, see SMS error codes explained and SMS API error codes and troubleshooting.