SMS opt-in or opt-out keywords

AI-generated summary

Genesys Cloud enables organizations to manage SMS communication preferences through automated opt-out and re-opt-in detection mechanisms that recognize industry-standard keywords and predefined phrases. The platform identifies single-word opt-out keywords (STOP, STOPALL, UNSUBSCRIBE, REVOKE, OPTOUT, CANCEL, END, QUIT, ARRET) and re-opt-in keywords (START, YES, UNSTOP) to automatically suppress or resume messaging, while HELP and INFO keywords provide program information for short codes only. Phrase-based detection evaluates inbound messages against predefined opt-out phrases such as "Stop texting me" and "Please remove me" to identify opt-out requests more consistently, though this approach applies only to opt-out requests while re-opt-in detection remains keyword-based. The opt-out detection service currently supports English, Spanish, and French, with planned expansion to Arabic, Dutch, German, Hindi, Japanese, Korean, and Portuguese. For unsupported languages, the system defaults to keyword-based detection, and organizations can request modifications to predefined opt-out phrases through care tickets. Opt-out detection is available only for SMS sender types that support inbound messaging; alphanumeric sender IDs cannot process opt-out requests through automated detection and require alternative opt-out methods such as agent contact, customer support channels, or embedded URLs or phone numbers. Administrators can configure message flows in Architect using the Message.Body variable and Decision action to filter opt-out messages from agent queues; however, interactions already queued or connected to an agent bypass Architect flow processing, and phrase-based detection messages may bypass filtering logic due to non-predefined keyword variations. When opt-out requests are detected, Genesys Cloud generates operational events for audit tracking, capturing recipient phone number, message timestamp, message ID, and outbound SMS number. Organizations can review opt-out events through the Developer Center (SMS Opt-Out Recorded and SMS Opt-In Recorded) and retrieve SMS opt-out suppression lists. Opt-out detection limitations include potential misclassification of messages and accuracy dependencies on message context, wording, and language. Organizations remain responsible for reviewing suppression status and can submit care tickets with High priority to report misclassified messages, providing specific details including outbound SMS number, recipient phone number, message content, OrgID, region, timestamp, message ID, expected classification, and justification while removing or redacting personally identifiable information. Genesys reviews reported messages to determine whether corrective action is required, supporting regulatory compliance and customer trust in SMS communications.

Genesys Cloud supports Short Messaging Service (SMS) opt-out detection to help organizations manage customer consent and comply with messaging regulations and carrier requirements.

Keyword-based opt-out

Genesys Cloud automatically recognizes and processes industry-standard SMS keywords for opt-out, opt-in, and help requests. Genesys Cloud recognizes the following single-word SMS messages as opt-out, re-opt-in, or help commands for the associated outbound SMS number.

Category	Keywords	Behavior
Opt-Out	STOP, STOPALL, UNSUBSCRIBE, REVOKE, OPTOUT, CANCEL, END, QUIT, ARRET	The customer no longer receives messages from the outbound SMS number.
Re Opt-In	START, YES, UNSTOP	The customer starts receiving messages from the outbound SMS number.
Help	HELP, AIDE, INFO	The customer receives information about the SMS program.

Note: Genesys Cloud routes HELP, AIDE, and INFO messages for short codes, but not for long codes or toll-free numbers. Genesys Cloud attempts to route all other keywords.

Phrase-based opt-out detection

Genesys Cloud extends SMS opt-out detection beyond single keywords by evaluating inbound messages against a predefined set of opt-out phrases.

When an inbound SMS message matches one of the predefined phrases, Genesys Cloud treats the message as an opt-out request and suppresses the recipient’s phone number from receiving additional messages from the associated outbound SMS number.

Examples of supported predefined opt-out phrasesClick to expand

Stop texting me.
Please remove me.
Unsubscribe me.
I don’t want these messages anymore.

Notes:

These examples are representative and do not include every supported opt-out phrase. If your organization needs changes to the predefined opt-out phrases, open a care ticket. By evaluating complete phrases instead of individual keywords, Genesys Cloud helps organizations identify and process opt-out requests more consistently, even when customers do not use standard opt-out keywords. This approach reduces the risk of sending messages after a customer withdraws consent, helping organizations support regulatory compliance and maintain customer trust in SMS communications.
Phrase-based opt-out detection evaluates inbound messages against a predefined set of supported opt-out phrases. It does not identify every possible opt-out request and may occasionally classify a message as an opt-out incorrectly. Detection accuracy depends on factors such as message context, wording, and the supported language. Organizations remain responsible for reviewing and managing suppression status to ensure that opt-out requests are handled appropriately.
Phrase-based detection applies only to opt-out requests. Genesys Cloud continues to detect re-opt-in requests by using keyword-based detection.

Genesys Cloud provides multiple methods to detect and process SMS opt-out requests. Click a collapsible for more information.

Language supportClick to expand

The opt-out detection service currently supports English, Spanish, and French. Genesys Cloud plans to expand language support in a future release to include Arabic, Dutch, German, Hindi, Japanese, Korean, and Portuguese.

For inbound messages received in unsupported languages, Genesys Cloud continues to use keyword-based opt-out detection. If keyword detection does not identify an opt-out request, organizations must review the message and manage suppression manually, as needed.

Sender type considerationsClick to expand

Opt-out detection is available only for SMS sender types that support inbound messaging. Because alphanumeric sender IDs do not support inbound messaging, Genesys Cloud cannot process opt-out requests through keyword-based or phrase-based detection for these sender types.

For alphanumeric sender IDs, organizations must provide an alternative method for customers to submit opt-out requests. For example, organizations can direct customers to contact an agent or customer support channel, or include an alternative opt-out option in the message, such as a URL or phone number.

After receiving an opt-out request through one of these alternative channels, organizations must update the recipient’s suppression status to prevent further messages. To suppress a recipient’s phone number, submit a Care ticket to add the number to the opt-out suppression list.

Routing considerationsClick to expand

If you do not want agents to receive opt-out keyword messages, configure your Architect message flow to filter these messages by using the Decision action and the Message.Message.Body variable.

If an interaction is already waiting in queue or connected to an agent when the customer sends an opt-out message, the agent may still receive the message. In this scenario, the interaction does not re-enter the Architect flow, so the configured filtering logic does not run.

Note:Architect-based filtering applies only to predefined keyword-based opt-out messages. Because phrase-based opt-out detection is not limited to predefined keywords, some messages that Genesys Cloud identifies as opt-out requests may still be routed to agents.

Opt-in and opt-out visibility

When Genesys Cloud detects an opt-out request, it generates:

An operational event and displays it in the Operational Console to indicate that the customer has withdrawn consent.
A corresponding operational event in the Operational Console when a customer restores consent.

Organizations can view relevant detection details, including the recipient phone number, message timestamp, message ID, and outbound SMS number. This visibility helps organizations track opt-out and opt-in activity, maintain audit records, and take follow-up action as needed. For more information about reviewing these events, see SMS Opt-Out Recorded and SMS Opt-In Recorded in the Developer Center.

Retrieve the SMS opt-out suppression list

For more information about retrieving SMS opt-out suppression lists, see Retrieve an SMS opt-out suppression list.

Review opt-out classification outcomes

If you identify an SMS message that Genesys Cloud incorrectly classified as an opt-out request, or that Genesys Cloud failed to recognize as a valid opt-out request, perform the following steps:

Review the original message content and the associated contact record.
Submit a care ticket along with the following actions:
- Set the subject line to SMS Opt-Out Detection Review.
- Assign the ticket priority to High.
In the ticket, include the following details:
- Outbound SMS number
- Recipient or contact phone number
- Message content
- Genesys Cloud OrgID & region
- Message and date timestamp
- Message ID
- Expected classification
- Provide justification as to why the message should or should not have been classified as an opt-out.
  Note: Remove or redact any unnecessary personally identifiable information (PII) before submitting message content. Include only the minimum information required to investigate the issue.
Genesys reviews the reported message and determines whether corrective action is required.

[NEXT] Was this article helpful?

Get user feedback about articles.