TPI Integration with Twilio
Overview
Conversive is a single-window service for all your messaging needs. To start messaging, you can buy SMS credits, Virtual mobile numbers, shortcodes/longcodes via Conversive, and experience power of messaging solution.
In Addition, Conversive has two offerings – BYOP & BYON which will be helpful for customers who want to adopt Conversive by purchasing user licenses and continue using their existing phone numbers or telecom connections.
“Bring Your Own Provider” or BYOP – This offering is for the customers who are already using SMS Aggregator in a standalone way or with Dialers and have long term contracts. They can start using Conversive without discontinuing the existing services. They can connect their existing SMS Provider with the Conversive Platform.
BYOP enables you to use a phone number provided by an external provider without losing the functional benefits of the Conversive Application.
Customers already connected with messaging providers such as Twilio, can continue using Native Conversive Application on Salesforce, Zoho, and other CRMs together and give your businesses the best of both worlds. This separation of Application and the underlying messaging provider gives businesses all the features and benefits of the application you know, but use a trusted provider at the messaging layer too.
TPI Integration with Twilio
Conversive offers a third-party API Integration feature. When a Conversive customer wants to use his own account at SMS Provider like Twilio and wants to use the Conversive App on Salesforce, TPI Integration helps.
The following sections talk about how Conversive TPI integration works with Twilio:
Requirements
Before you start TPI Integration of Twilio with Conversive, answer the following questions:
- Is it SMS integration Or WhatsApp Integration?
- Is MMS enabled for the incoming numbers that you are going to use for different countries?
- Are you going to send messages only in the USA or other countries as well?
- If your numbers belong to the master account at Twilio then we need Account SID & Auth token. (https://www.twilio.com/console/project/settings)
- If your numbers belong to sub-account at Twilio then we need the following information:
- Account SID of master account
- Credentials of the sub-account i.e.
- Account SID of sub-account
- AuthToken of sub-account
- https://www.twilio.com/console/project/subaccounts
Twilio Setup to be done by Customer
As a Customer, you need to make sure that the Incoming URL is set up correctly at your Twilio account for all numbers so that you can receive the responses.
Delivery reports of outgoing SMS sent will be synced with CRM as and when received from Twilio.
For Twilio number, Incoming URL should be set to below:
If the customer is using, Conversive USA Server:
- Primary URL: https://api.sms-magic.com/v1/sms/incoming/twilio
If the customer is using, Conversive EU Server:
- Primary URL: https://eu.api.sms-magic.com/v1/sms/incoming/twilio
Once the incoming URL is set, any incoming message terminating at number should get listed under message logs on Twilio console.
For Twilio-WhatsApp, please configure the Answer URL as follows:
1. Conversive US Server:
- Answer URL: https://api.sms-magic.com/messages/incoming/whatsapp/twilio
- Status URL: https://api.sms-magic.com/messages/status/whatsapp/twilio
2. Conversive EU Server:
- Answer URL: https://eu.api.sms-magic.com/messages/incoming/whatsapp/twilio
- Status URL: https://eu.api.sms-magic.com/messages/status/whatsapp/twilio
Conversive Setup to be done by our CS
For further assistance and to make sure that TPI Integration is working properly, contact our Customer Care Team at care@sms-magic.com.
You need to share the Account SID & Auth token with the Customer Success Agent of Conversive. They will set a specific route for that customer on the Conversive Server. Please share information in a secure way, using a key base.
Conversive Customer Support Agent will test incoming and outgoing on a test number to make sure TPI integration is working fine.
