All channels offer a ‘sent’ acknowledgement when a message is delivered to the platform. Using these acknowledgements customers can create fallbacks based on delivery and read acknowledgements.
The following table shows the type of acknowledgements, which are available for each channel:
|
|
SENT
|
RECEIVED
|
READ
|
|
|
Message received by platform
|
Message received by the apps on user’s device
|
User launched mobile/ social apps
|
|
SMS
|
Yes
|
N/A
|
N/A
|
|
MMS
|
Yes
|
Yes
|
N/A
|
|
RCS
|
Yes
|
Yes
|
Yes
|
|
WhatsApp
|
Yes
|
Yes
|
Yes
|
|
Facebook Messenger *
|
Yes
|
Yes
|
Yes
|
|
Instagram
|
Yes
|
Yes
|
Yes
|
|
Viber
|
Yes
|
Yes
|
Yes
|
|
KakaoTalk
|
Yes
|
Yes
|
No
|
|
Telegram
|
Yes
|
No
|
No
|
|
WeChat
|
Yes
|
No
|
No
|
|
LINE
|
Yes
|
No
|
No
|
|
Apple Messages for Business
|
Yes
|
No
|
No
|
* - For Facebook Messenger note that the READ receipt is only supported when the hosting is done outside EU.
Visit the Conversation API callbacks section of the Sinch Documentation site for more details about how acknowledgments or delivery reports work.
Learn more about Sinch Conversation API.
