Ensuring that you keep track of which customers opt-in and opt-out of different messaging campaigns is essential. Additionally, several of Conversation API's channels require you to obtain recipient opt-in prior to sending certain messages.
The consent management functionality of Conversation API allows you to manage the registration of opt-in messages sent by your end-users. It does so by checking the text content of inbound messages, matching that content with a set of pre-defined opt-in phrases, and, upon identifying a match, sending an opt-in callback to your system via webhook trigger.
Once enabled, the consent management functionality will start processing mobile originated messages. For all mobile originated messages, the consent management functionality will check for the presence of keywords that identify the message is an opt-in or opt-out message.
Note the following:
-
The system checks for an exact match. So, for example, if the keyword start is set as the opt-in keyword, a message containing the text start will trigger the consent management functionality. However, a message containing the text start now please will not trigger the functionality.
-
The consent management matching process is case insensitive, so text like Start, START, starT, etc. would all trigger the functionality in this example case.
-
If no keywords are provided, a default keyword list is provided. For more information about how to customize keywords or auto-replies, see our article on keyword and auto-reply customization.
To activate this functionality, see our article How do I activate consent management?.
For information on Conversation API's consents endpoint, see our API reference documentation.
Learn more about Sinch Conversation API.
