As of April 16th, 2025, a breaking change was introduced to the Conversation API. The default processing mode changed from CONVERSATION to DISPATCH.
This change impacts all new Conversation API apps created after this date. Apps created prior to this date are unaffected by this change.
Please review your configurations and update any dependencies accordingly.
By default, Conversation API uses the DISPATCH processing mode, which handles messages without storing information about contacts and conversation. Note that, while this information is not stored in DISPATCH mode, you may still engage in two-way messaging with regular recipients. The metadata regarding the contact and conversational thread is simply not stored in Sinch's systems.
You may also use the CONVERSATION processing mode. Each mode is described below.
| Processing Mode | Behavior |
|---|---|
DISPATCH |
|
CONVERSATION |
|
You can set the processing mode in two ways:
On the App: the selected processing mode will be applied to every new MT and MO.
On individual MTs: only the MT will be sent in the selected processing mode. The processing mode won't carry over to the MO. For example, if the user responds a dispatch MT but the App is in
CONVERSATIONmode, a new Contact and Conversation may be created if they don't already exist. You should carefully evaluate this option as it's meant to be used by campaign dispatching services that initiate conversations.
In general, DISPATCH mode is simpler to use. It is the default processing mode and, although certain pieces of information are note stored while using DISPATCH mode, you are still able to engage in two-way message while using this default mode.
However, depending on your needs, you may find a use for CONVERSATION mode.
Below are some general considerations and guidelines for making Conversation API calls while using CONVERSATION mode.
Contacts are created in CONVERSATION mode. Therefore, when using a Conversation API app set to CONVERSATION mode, the following API calls can be made by including and populating the contact_id field of the recipient object:
Since contacts and conversations are created in CONVERSATION mode, these operations will return successfully contact_id or conversation_id are provided when using a Conversation API app set to CONVERSATION mode: