Skip to content
Conversation API/
Integrations
/
/
FAQs
Last updated

FAQs

Below are answers to frequently asked questions about the Sinch Omnichannel Connector for Salesforce Marketing Cloud:

Where will the Sinch Omnichannel Connector data be hosted?

For the initial release, the Omnichannel Connector data will be hosted in the Sinch AWS EU region. In the future, we will expand the hosting to other regions.

What is the support process when using Omnichannel Connector?

The support process is the same as the process for the Conversation API. You may submit a ticket to the Sinch 24x7 team, and they will triage the case. If they cannot resolve it, then the case will be escalated to Sinch tier-2 support and eventually to Sinch Dev team members.

Is the Sinch Omnichannel Connector GDPR compliant?

Yes.

Is the Sinch Omnichannel Connector LGPD compliant (Lei Geral de Proteção de Dados; aka: Brazilian General Data Protection Law)?

Yes.

I am an ASP client. Is Omnichannel Connector suited for me?

Yes, ASP clients can use the Omnichannel Connector app in their solution(s).

What is the expected throughput when sending outbound traffic using the Omnichannel Connector?

The maximum speed of the Salesforce Marketing Cloud's Journey Builder is 50 TPS (when using the custom activities). The Sinch Omnichannel Connector supports this throughput level.

Do I need to enable third-party cookies when connecting my Conversation API account and project to my Salesforce account?

Yes, in order to successfully connect your accounts, you must enable third-party cookies. This is true regardless of the browser you use when connecting the accounts. Note that, in some cases, third-party cookies may be blocked by default on certain browsers. If these cookies are not un-blocked, you may be unable to complete your integration.

Previous page
Next page