Yes! Switch works with all phone systems. But not all phone systems can use the API method of installation so you may need to use the call forwarding method.

There are two ways two set up Switch - via call forwarding and API. Many of our customers use call forwarding to set up Switch as it's simple and compatible with all phone systems. The API offers more control and customization for handling call data, but isn't compatible with some phone systems such as Aircall, Zendesk, and TalkDesk.

In short, if you want a straightforward setup, call forwarding is a great option. But if you want a more robust option, find out if your phone system supports API and try this installation.

No list at the moment. Common AVRs, Aircall, Zendesk, and TalkDesk cannot use API and would require installing using the call forwarding option.

No, not at the moment.

Yes, Switch will work almost anywhere in the world, except New Zealand and Saudi Arabia (due to local SMS laws).

Switch is charged based on how many calls you deflect with it each month. A deflected call is counted when the user selects the option to switch on the phone call. You will be charged even if the end user never sends a message in the messenger. The pricing model is tiered based on your usage, with the price points found here

You can easily see how many calls you've deflected by filtering the Conversations report by “Phone switch”. You can also keep tabs on all your Switch usage through the “Monitor” tab in Switch settings. Find out more about reporting here.

No, we currently only support provisioning US numbers for Switch.

By default, Switch creates a new lead when a conversation starts. You can change this in Switch settings. If you opt to identify existing users, Switch will associate the conversation with existing users in Intercom who have a matching phone number. If no matching phone number exists, a new lead will be created. And if two users with the same number already exist, the conversation will be attached to the user who was seen last.

Conversation is created only when user sends a message and not when SMS is sent or Messenger link (sent in SMS) is clicked.

Switch only tries to merge profiles when the conversation first comes in. If there is no phone number match at this stage, nothing will merge.

This is the message you add to your IVR which lets your customers know they can switch to chat in the Messenger. Here are a few example scripts you can adapt to your business:

Switch will check to see if the phone number can receive an SMS. If not, it will prompt the caller to put in their mobile number so it can send an SMS to them. Canada is the only country from which we cannot detect if the phone number is a landline or a mobile phone.

Yes, the SMS sent to your customers from Switch is completely customizable across all the languages you have set up to support.

No. Call forwarding does not support creating CDAs. This prevents teammates from creating multiple different rules or Workflows for switched conversations.

It's still possible, but it would be based on different things. For example, with call forwarding you could create multiple rules depending on user data.

Example: from switch is true and phone starts with "+1" to route to the US Support team (or phone starts with "+44" to route to the UK support team).

What's possible in the API is passing through CDAs directly from the call, so if the caller pressed 1 to talk to support then switched, you could route based on the fact they already selected 1 on the phone.

Yes, we use the the first 3 digit of the country code is used to find the user language. For eg if it +49 then SMS will be sent in German if the language is set in Messenger settings.

From Phone Switch: This attribute is not visible in UI. When a user opts which option a note is attached in the conversation and this identifies whether the attribute is set to true or false. Main used to set up automation rules

Page URL: "starts with https://via.intercom.io" or "contains via.intercom.io" used for triggering bots

Channel: Phone Switch used in reporting

Yes. Our developer docs are here 📚

No, there is no attribute to identify the leads/users. Only way to identify is the conversation via From phone switch attribute.

That will be different because we use it to track if the user clicks each time and see if it was switched successfully or not.

This is possible if the phone system supports an API call. As part of the API call, you can specify custom attributes. These attributes will create or match existing CDAs in Intercom, which will be populated on the user’s profile and can be used to target rules and Workflows.