01Who this is for
- Founders of agencies that send promotional texts need to stay compliant and avoid delivery failures.
- Customer support managers who rely on SMS alerts must respect opt out requests to keep communication lawful.
- Small business owners using HighLevel for appointment reminders must manage unsubscribed contacts to maintain deliverability.
02Opt out blocks, explained
The feature monitors replies that contain opt out keywords such as STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, or QUIT. When a contact sends one of these keywords, the platform marks the number as unsubscribed and blocks any further outbound messages from the associated phone number, sender ID, or Messaging Service. The block also applies if the contact’s profile has Do Not Disturb enabled.
If an outbound attempt is made to an unsubscribed or DND enabled contact, the Twilio API returns error 21610. HighLevel does not bill for the blocked attempt and the message is never sent. To resume messaging, the contact must reply with an opt in keyword like START or YES. The opt out status cannot be overridden manually.
All of this logic lives in the SMS/MMS sending flow of HighLevel, which uses Twilio or other integrated messaging platforms. Compliance settings are enforced automatically, and any attempt to send to an unsubscribed contact results in the error response.
03How businesses use opt out blocks
- Real estate agency. The agency reviews its contact list for numbers that have replied STOP. It removes those numbers from future property alert campaigns and asks the owners to text START to re subscribe before sending new listings.
- Dental practice. When a patient sends STOP after a reminder, the practice’s HighLevel profile marks the number as DND. The staff then updates the patient’s profile to block SMS and contacts the patient by phone instead.
- Ecommerce store. The store’s marketing workflow checks for opt out keywords before launching a promotion. Numbers that have opted out are excluded from the bulk SMS blast, ensuring compliance and avoiding delivery errors.
04The numbers and rules that matter
- Error 21610 is returned when a recipient has opted out.
05How to set up and use opt out blocks in HighLevel
Identify that a contact has opted out
- Check the contact’s record for a STOP reply or a Do Not Disturb flag that prevents SMS delivery.
Review possible reasons for the block
- Consider whether the recipient replied with an opt out keyword, the number was reassigned, or DND was enabled on the profile.
Apply the recommended solution
- Remove the unsubscribed number from the list or ask the recipient to text START (or YES) to re subscribe before sending again.
Understand Twilio’s response to an opt out
- When a blocked send is attempted, Twilio returns error 21610 and HighLevel does not charge for the attempt.
Know the opt out keywords
- Messages are blocked if the contact replies with STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, or QUIT.
Know the opt in keywords
- The contact must reply with START or YES to lift the block and receive messages again.
Observe the scope of an opt out
- If a contact opts out from a Messaging Service number, the block applies to all numbers tied to that service.
06Things to know before you rely on it
- Opt out applies to every number in a Messaging Service, not just the single number that received the STOP reply.
- You cannot manually re add a contact who has opted out; the recipient must send an opt in keyword.
- No charge is incurred for messages blocked by an opt out error.
07If something goes wrong
- Message blocked with error 21610. Confirm the contact has replied STOP, then request they text START or YES to resume messaging.
08How it connects to the rest of HighLevel
- Set up SMS compliance and opt out handling SMS compliance settings
- Check SMS delivery errors and troubleshooting steps SMS delivery troubleshooting
- Read best practices for SMS deliverability and avoiding restrictions SMS deliverability best practices
Michael's take

Be careful with contacts who have sent STOP or who are marked DND. HighLevel will not let you push messages to them and you’ll see Twilio error 21610, which protects you from compliance violations but also stops the conversation dead in its tracks.
When you respect those blocks and keep your lists clean, you stay compliant and avoid wasted spend. Let contacts opt back in with START or YES, and you’ll keep the line of communication open without risking penalties.