Issue
Customers may experience confusion regarding eligibility for Group MMS (Group Texting) in Twilio Conversations, and how opt-out keywords (like "STOP") are processed within group threads to maintain A2P 10DLC compliance. This often stems from older documentation suggesting the feature is restricted, and a lack of clarity on whether a "STOP" reply from a single user applies strictly to the business sender or the entire peer-to-peer group.
Product
Twilio Conversations Classic
Resolution
Eligibility: As of October 2024, Group MMS in Conversations is Generally Available (GA) for all Twilio accounts. The previous limitation (from March 2022) that restricted the feature strictly to pre-existing accounts is no longer in effect.
Opt-Out Behavior & Compliance:
- Application-to-Person (A2P) Messages: When a participant in a Group MMS thread replies with an opt-out keyword like "STOP", Twilio's standard opt-out logic automatically blocks all future platform-originated API messages to that specific recipient, raising Error 21610 (Attempt to send to unsubscribed recipient). This mechanism natively satisfies A2P 10DLC compliance requirements to cease business-originated communications.
- Person-to-Person (P2P) Messages: Messages sent directly from one participant's mobile handset to the rest of the group are routed natively by cellular carriers and bypass the Twilio platform entirely. These messages are classified as P2P carrier traffic and fall outside the scope of A2P 10DLC compliance and enforcement.
-
Best Practices: Upon receiving the opt-out event via the status webhook (
OptOutType), it is strongly recommended that businesses update their internal logic to remove the opted-out participant from the Twilio Conversation resource. While this will not stop carrier-level P2P messages between the end-users, it prevents unnecessary API requests and keeps backend states synchronized.