This feature is for future use. Requests using dispatch mode result in status 400.
By default, Conversation API always associates new messages with a Contact and a Conversation. If there's no existing contact or active conversation, new ones are created. This is the
CONVERSATION mode intended to be used by the majority of apps.
This behavior may not be desired for use cases in which contacts and conversations are not leveraged, mainly unidirectional high volume SMS campaigns. Such use cases may find the
DISPATCH processing mode more attractive in order to achieve a higher throughput and prevent storage of unused information. Dispatch mode aims to address this necessity by handling messages without maintaining contacts and conversations.
Dispatch mode can be set in two ways:
On the App: dispatch mode will be applied to every new MT and MO. Conversation API won't create contacts and conversations at all.
- On individual MTs: only the MT will be sent in dispatch mode. The dispatch mode won't carry over to the MO. Therefore, 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.
Since contacts and conversations are not created in dispatch mode, bear in mind it will limit the usage of APIs involving them. These operations will return status 400 in case a
conversation_id are provided for an app in dispatch mode: