This article takes you through the steps to use Twilio as your route for sending Responder SMS.  Twilio is most commonly used with our USA clients.  We have our own routes for many countries, but for the USA and Canada, we recommend using Twilio.

Step 1 - Add Your Twilio Credentials to LeadByte
Go to Admin > Tech Hub > SMS Providers.  You should see Twilio as a SMS Provider.  Click Select and Credentials.  You will need to add your Twilio Account SID and your Twilio Auth Token.  If you do not see Twilio as an SMS Provider, please raise this as a support ticket and we shall enable it.

Step 2 - Create Responder and or Delivery SMS.
You will need to create your SMS Responder, read how here.  When you create a Responder you will need to select Twilio as the SMS Provider.  When you create a Push, you will need to create a Sender Name.  You can do this by clicking "Edit List".  To send successfully via Twilio, the number must be an active Twilio Number.  It should be the number without the "+" and without spaces.

If you want to send an "On Success" SMS to a buyer via a delivery you will need to open a ticket with support and provide the phone number you would like to add as your sender name. This can not be done from the UI. 

Step 3 - Test Responder and or Delivery
When you test the Push you will get a message "SMS added to the queue for delivery" if you have set it up correctly.  This is your green light to activate the Responder/Delivery so you can start messaging your leads/buyers.  Anything else will be a failed send to Twilio.  This will not be listed in their logs.  It will likely be an incorrect SID or Auth Token or the Sender does not match the Active Number in Twilio.  Please raise this as a support ticket if you can't get it working after checking the above three items.

Step 4 - Monitor (SMS logs and Reporting)
When you are live, we advise that you check two things:

1. SMS Responder Report under Reports.  This will give you an indication if SMS are sending OK.
2. SMS Logs under Responder > SMS Logs.  This will give you insight into what is being sent.  If messages are failing, you will see this here (including the reason).  The most common is "The requested URL returned error: 400 Bad Request".

Was this article helpful?
0 out of 0 found this helpful