Skip to content

Commit 31b6dfc

Browse files
authored
Update opt-out-api-concept.md
1 parent 89eb02e commit 31b6dfc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/communication-services/concepts/sms/opt-out-api-concept.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.subservice: sms
1313
---
1414
# Opt-Out management overview
1515
The Opt-Out Management API enables you to manage opt-out requests for SMS messages. It provides a self-service platform for businesses to handle opt-out requests, ensuring compliance with regulations and protecting customer privacy.
16-
Currently, opt-out handling includes configuring responses to mandatory opt-out keywords, such as STOP/START/HELP. The responses are stored and the list of opted-out numbers is maintained in the Azure Communication Services Opt-Out database. This database management is automatic.
16+
Currently, opt-out handling includes configuring responses to mandatory opt-out keywords, such as STOP/START/HELP and others. The responses are stored and the list of opted-out numbers is maintained in the Azure Communication Services Opt-Out database. This database management is automatic.
1717
The Opt-Out database contains entries added when a recipient sends an opt-out keyword. An entry includes the fields: Sender, Recipient, and Country. If a recipient opts back in, the corresponding entry is deleted.
1818
To learn more about how opt-out is handled at Azure Communication Services, read our [FAQ](https://learn.microsoft.com/azure/communication-services/concepts/sms/sms-faq#how-does-azure-communication-services-handle-opt-outs-for-short-codes.md) page.
1919

0 commit comments

Comments
 (0)