Conversation API

The Conversation API does not provide the Customer with access to any underlying messaging or social channel. Access to and use of any underlying messaging or social channel may be ordered from Sinch by the Customer subject to separate Order Form(s). For avoidance of doubt, this includes when Free Tier pricing for Conversation API applies to the Customer.

Data Retention. The standard retention period for conversation data applied by Sinch is 180 days. The standard retention time for contact data is indefinite. Customer understands that this is part of the functionality of the service. Customer can change the retention period for both categories by itself. Information is given in the service specification and within the dashboard. A change of retention time is considered an Instruction in accordance with the applicable DPA. The implementation is done automatically (without human interference) and the Customer understands that when it changes the retention time, this goes into immediate effect. Sinch does not take any responsibility and/or liability for the (changes to the) retention time made by Customer.

Data Localisation. The Services ordered under this Order form present a choice on hosting locations. This is set from the start of the Service, configured by Customer self-serve via dashboard.sinch.com or upon request to the Customer account manager at service setup. If Customer wishes to change the Hosting Location after setup, it needs to contact Sinch and Customer understands that changing the Hosting Location may lead to additional fees.

The Services are still in an initial phase and are thus being continuously improved. This also includes pricing models. The Customer explicitly acknowledges and agrees that this section sets out an initial pricing model regarding the Services, and the pricing model (including fees) may be changed in Sinch’s sole discretion subject to 30 days’ notice. Discounted fees based on (i) total number of active “Charged” Tiers per Customer and higher Included MAUs thresholds are available as defined in the table below. For avoidance of doubt, the rates set out in the tables below will not be exceeded.

• Each Conversation API provisioned to the Customer shall incur a fixed monthly recurring platform fee (“Platform Fee”) as set out in the table below. A Conversation API shall be considered “active” as per the first calendar month it routes one hundred (100) or more messages. The Platform Fee will be charged irrespective of the configuration of the underlying messaging channels associated with each relevant Conversation API.
• In addition, Fees shall be incurred per Monthly Active User. A “Monthly Active User” or “MAU” is one unified contact who has sent and/or received a message within a specific calendar month routed through a Conversation API to an underlying messaging channel. When using several channels for communication (e.g. SMS and Whatsapp), it is the sole responsibility of the Customer to merge the identity of such Monthly Active User for it to be counted as one.
• Free Tier pricing will apply (i) during an initial testing phase for a maximum of 100 MAUs, or (ii) if the Customer only uses a single messaging channel when sending messages through Conversation API. Upon the event of Customer using more than one channel, Charged Tier pricing will apply. Pricing is set out in the tables below.
• Channel message fees always apply in accordance with standard rate card pricing.

Conversation API Pricing

Here you will find the pricing tables for Conversation API

Discounts to Monthly Platform Fee based on the number of active apps:

*A Single Conversation API “App” Supports single, similarly named Sender-ID’s across Sinch supported channels. Eg. WhatsApp “Sinch Europe”, Facebook Messenger “Sinch Europe” would require one Conversation API “App”, but WhatsApp “Sinch Europe”, Viber “Sinch Europe” and WhatsApp “Sinch USA” would require two Conversation API “App’s”