Sinch Community

Currently, the following channels are available through the Conversation API: Note: More social channels will be added in the future –and you will have access to these new channels as they become available.   Conversation API can support any combination of these channels.   Visit the Sinch Documentation site to learn more about how we support these channels.   Learn more about Sinch Conversation API. ... View more

As Conversation API is a building block API, you can integrate Conversation API directly into your communications platform. Whether that's a customer data platform, marketing automation platform, or CRM. The possibilities are as diverse as your imagination.   The Sinch Developer Documentation site contains comprehensive documentation and tutorials, which show you how you can quickly intergrate Conversation API into your platform.   Learn more about Sinch Conversation API. ... View more

The Sinch Developer Documentation site contains comprehensive documentation and tutorials, which show you how you can quickly create and configure your first Conversation API app.   Read our Conversation API Getting Started Guide which takes you through all the different steps of creating your first app with Conversation API.   Learn more about Sinch Conversation API. ... View more

The Sinch Developer Documentation site contains the full range of API references for Conversation API. The Developer Documentation site also contains comprehensive documentation and tutorials, which show you how you can quickly create and configure your first Conversation API app.   Learn more about Sinch Conversation API. ... View more

If you are interested in trialling Conversation API then we have a free tier for trial usage. Please contact Sinch to discuss how to proceed.   Learn more about Sinch Conversation API. ... View more

Conversation API is suitable for any scenario where a client wishes to send / receive messages across multiple messaging channels with the convenience of a single point of integration and intelligent message format handling (Transcoding).   Here are some sample critical and non-critical use cases for Conversation API:   Use Case Description Customer care and service Two-way messaging for technical, services and product support for users, including customer inquiries and resolution. Notifications and alerts Real-time account, travel, transaction, disruption updates, delivery receipts, reminders Two-factor authentication and verification One-time passwords for account resets, banking transactions and user validation. Market research and insights Conduct surveys, polls, and experience feedback. Marketing Personalized offers and content based on user preference for receiving such messages. Product updates Updates on availability of a specific product, new product releases, or feature updates and changes to an existing product Newsletters Regular Newsletters   Learn more about Sinch Conversation API. ... View more

You can check if messages have been successfully delivered by viewing Delivery Receipts or Reports (DLR’s) also referred to as acknowledgements, which can be sent directly to the defined Webhook.   Visit the Conversation API callbacks section of the Sinch Documentation site for more details about how this works.   Learn more about Sinch Conversation API. ... View more

Conversation API supports 2-way SMS Service through the Sinch XMS service. The Conversation API changes the callback of the associated service plan automatically so a service plan should be configured for the sole use of the Conversation API.   Visit the Conversation API section of the Sinch Documentation site for more details.   Learn more about Sinch Conversation API. ... View more

Whitelisting is optional. Callback security can be ensured using HMAC (a type of authentication to ensure that a Callback cannot be "Spoofed") signed Callbacks.  These can be configured through the Sinch Dashboard.   Refer to the Conversation API Validating Callbacks section of the section of the Sinch Documentation site to learn more.   Learn more about Sinch Conversation API.   ... View more

Security is built-in “by Design”. The conversation API has been independently reviewed by a third-party security consultancy. Data is encrypted in transit and at rest before reaching the channel specific API’s where their service encryption is adopted.   Data retention policies are configurable for each Conversation API App. For further detail on the security architecture, please reach out to your Sinch Account Manager.   Learn more about Sinch Conversation API ... View more

Sinch offers the Conversation API SMS Service in all countries where Sinch offers SMS services. Sinch is a leader in the mobile messaging market and we have a vast amount of direct connections.   Over the years we have built relationships with suppliers and operators that allow us to reach all four corners of the globe. Serving over 200 destinations and thousands of networks, we are confident we can get your message to your audience.   Note: When sending messages to different countries, customers are obligated to comply with all applicable regulations and requirements pertaining to that country. Our self-service portal contains comprehensive Country Information pages, which detail regulatory and compliance information to help you communicate successfully with different countries.   ... View more

Yes, users have the ability to deregister from channels to stop receiving messages, but the opt-out method will differ according to the channel.   Refer to the Conversation API Opt-in & Opt-out section of the Sinch Documentation site for more details.   Learn more about Sinch Conversation API.   ... View more

One of the main challenges with chat messaging channels is that they require data connectivity to use. If the customer you’re engaging with doesn’t have access to mobile networks or wi-fi then in this case you can use failover which allows you to set rules so that if the user device does not receive the message you can automatically switch to SMS, and then return to social channels when they have full connectivity.   Similarly, if it’s an important alert or notification that you need to make sure the user has seen – such as one-time password, or an account breach, in this case too you can utilize fallback or failover rules so that, if the customer doesn’t receive or view the message, then you can automatically switch to another channel.   The Sinch Conversation API allows you to make sure urgent messages are quickly received by giving you the option to set conditional fallback channels to ensure the user can always read the message.   Learn more about Sinch Conversation API. ... View more

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. ... View more

Conversation API supports OAuth2 authentication.   Learn more about Sinch Conversation API. ... View more