Twilio Error 21610: Message to an Unsubscribed Recipient

Updated

Short answer: Twilio returns error 21610 when you text someone who has opted out of messages from your number or Messaging Service, usually by replying STOP. Twilio will not send to that number from that sender again until the person texts START. Take the number off your sends, and do not text them from a different number instead.

What error 21610 means

Twilio's title for this code is "21610: Attempt to send to unsubscribed recipient". The error page says:

"The person you are trying to message has opted out of receiving messages from your Twilio phone number, Channels sender, or Messaging Service."

It adds: "You will not be able to send to the phone number specified in the 'To' parameter until the subscriber identified by the phone number has responded with "START"."

Twilio's opt-out guide explains how the block works. When someone texts an opt-out keyword, Twilio "adds this phone number to a list of blocked numbers. Twilio checks this list before sending any future outgoing messages." Messages to that number then "will fail with Error Code 21610 asynchronously", so look for the code in your message logs and status callbacks.

Common causes

Twilio lists two:

  • "The end user handset has responded with "STOP" or another opt-out keyword."
  • "The phone number has been reassigned to a different end user recently."

By default, Twilio handles "standard English-language reply messages—STOP, UNSUBSCRIBE, END, QUIT, STOPALL, REVOKE, OPTOUT, and CANCEL—for long code numbers". It matches keywords "in a case-insensitive way", so "Stop" counts the same as "STOP".

Reassigned numbers are a risk with old lists. CTIA's Messaging Principles and Best Practices ask senders to "process telephone deactivation files regularly (e.g., daily) and remove any deactivated telephone numbers from any opt-in lists."

What to do when you get 21610

  1. Stop sending to the number. Twilio's first suggestion is: "Consider removing this phone number from your list of recipients." Take it out of campaigns, automations and future imports too.
  2. Let the person opt back in. Twilio suggests you "Request the recipient to resubscribe to your messages by texting in "START" or another opt-in keyword to your Twilio sender." START and UNSTOP are reserved opt-in keywords. When someone sends one, Twilio "removes the blocked number entry containing the user's number".
  3. Do not expect to lift the block yourself. Twilio says Advanced Opt-Out "currently does not support changing or reporting on blocked phone numbers via the Console or the REST API." The opt-in has to come from the person.
  4. Check toll-free numbers separately. For US toll-free numbers, Twilio says: "Only the keywords START and UNSTOP can fully undo the blocking. Twilio's supported keyword "YES" will not work to opt-in a previously unsubscribed user."
  5. Confirm consent before the next send. "Before sending messages to a recipient, ensure they have consented to receive messages from you."

The block is per sender, the rule is per person

Twilio's block covers the sender the person opted out of. Its Messaging Policy covers the person:

"When a recipient revokes their previously provided consent, also known as an opt-out, you may deliver one final message to confirm that the revocation of their prior consent or opt-out has been processed, but any subsequent messages are prohibited. You may not send messages to a recipient that has withdrawn their consent or opted out, unless that recipient elects to receive those messages again by providing subsequent express written consent."

So moving to another number or Messaging Service to reach the same person is not an option under Twilio's policy. CTIA's guidance also allows "one final opt-out confirmation message per campaign" and says "No further messages should be sent following the confirmation message."

Opt-outs in plain words

Not everyone replies with a keyword. CTIA says:

Standardized "STOP" wording should be used for opt-out instructions, however opt-out requests with normal language (i.e., stop, end, unsubscribe, cancel, quit, "please opt me out") should also be read and acted upon by a Message Sender except where a specific word can result in unintentional opt-out.

The FCC's rule on revoking consent, 47 CFR 64.1200(a)(10), also deals with wording:

If a reply to an incoming text message uses words other than "stop," "quit," "end," "revoke," "opt out," "cancel," or "unsubscribe," the caller must treat that reply text as a valid revocation request if a reasonable person would understand those words to have conveyed a request to revoke consent.

The same paragraph says revocation requests "must be honored within a reasonable time not to exceed ten business days from receipt of such request." It covers consent to calls and texts made under paragraphs (a)(1) through (3) and (c)(2) of that section, so ask a lawyer how it applies to your messages. Either way, read replies, not only keywords, and opt out anyone who asks in their own words.

If you send through HighLevel

HighLevel's article on this error adds a cause: "the contact may have DND (Do Not Disturb) status enabled in their contact profile." HighLevel sets DND by itself in some cases. Its DND guide says: "DND is enabled if a contact replies with opt-out keywords (e.g., STOP, UNSUBSCRIBE) or if specific error codes (30003, 30004, 30005, 30006) are received from the service provider."

On LC Phone, HighLevel's messaging policy says that after a STOP reply, "All upcoming and queued messages will fail, and a permanent DND is enabled at the contact level." That DND "cannot be revoked from the UI". The contact clears it by replying START, YES or UNSTOP to the number, and if that does not work, HighLevel asks you to "raise a support ticket". It cannot be undone in bulk either. Asked whether you can re-add a contact who opted out, HighLevel answers: "No. Opt-out status must be reversed by the recipient themselves".

  • Scope. "Opting out of a single phone number only blocks that number. But opting out of a Messaging Service blocks every number tied to that service."
  • Toll-free. HighLevel's error dictionary lists a related case under error 30004: a message "from a US/CA Toll-free number to an end user handset that has previously responded with "STOP" or another opt-out keyword."
  • Automation. The "Messaging Error - SMS" workflow trigger can filter on 21610, which HighLevel labels "User Replied with STOP (Opted Out)". HighLevel says the trigger "can be used for taking relevant measures to clean the contact list".
  • Opt-out rates. HighLevel's messaging policy sets opt-out thresholds for warnings and suspensions, and says "A good opt-out rate is typically 0–1%." See why GoHighLevel paused your SMS.

How to keep opted-out numbers out of your sends

  • Record opt-outs in your own system. With Advanced Opt-Out, Twilio adds an OptOutType value of START, STOP or HELP to the request it sends your Messaging Service's webhook when a keyword arrives. Twilio says "You may want to store this information". Check that record before each send.
  • Clean old lists. Remove deactivated numbers before you reuse or import a list, as CTIA asks.
  • Text only people who opted in, and keep proof. Twilio's policy says: "You are required to retain proof of all consents obtained from recipients for as long as needed to meet your legal requirements and at least until a recipient withdraws their consent."
  • Show the way out. Twilio's policy says the first message "needs to include the following language: "Reply STOP to unsubscribe," or the equivalent using another standard opt-out keyword". Precheckly's free A2P 10DLC sample checker checks that each sample names the brand and that at least one has opt-out wording.

Precheckly's Pro plan ($29 a month) audits your sending history, including texts sent after someone replied STOP. The Agency plan ($99 a month) keeps a consent and opt-out ledger, with opt-outs brought in from HighLevel, and checks contact lists against opt-outs and consent before a blast. See pricing.

For consent wording, see SMS opt-in language. For other failed texts, see Twilio error 30007, delivery errors 30003, 30005, 30006 and 30008 and the list of A2P 10DLC error codes.

Sources

Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.