Thanks for using Twilio for Salesforce! Installation generally takes just 10-20 minutes. To use Twilio for Salesforce, you will need the following:
- A Twilio account - sign up here if you still need one!
- Are you a nonprofit or social enterprise? After signing up for Twilio, apply to Twilio.org for $500 in API credits (~80,000 free messages) and a discount on all Twilio products and services.
- Access to the Twilio for Salesforce preview - sign up to get that access here.
- Administrative access to a Salesforce instance
- A thirst for adventure
Got all those things? Then let's get started!
We recommend reading this entire guide, but for a click-by-click view of the install process, check out this brief video outlining the major configuration steps needed to use the package. Then, seriously, READ THE GUIDE - there are important pointers about using the package for production use cases.
To use Twilio for Salesforce, you will need to find or create the following resources within your Twilio account.
- Twilio Account SID
- Twilio API Key / Secret Pair
- A Messaging Service (learn more about them here if you'd like)
This one is easy! Navigate to your Console dashboard and copy the "Account SID" value from the front page. Leave this page open, or copy the value to a text file - you'll need it when you configure the Salesforce package.
Next, you'll need to create an API Key and Secret to allow your Salesforce instance to communicate with Twilio. There are a few places you can create and manage these keys within the Twilio console, but let's grab them from the Tools section of the Programmable SMS console, which we'll need to use again in a minute anyway. Once there, create a new API key pair by pressing the plus button.
Give your API key a name - anything you like. This next bit is important though! Make sure you create a "Master" API key!
Click the "Create API Key" button, and you should be shown two long strings which are the API credentials you must provide in your Salesforce configuration so that you can communicate with Twilio. As noted in the UI, you should save these credentials in a secure location/text file, because they will only be shown once!
A messaging service is a resource within Twilio that allows API users (like your Salesforce organization) to send and receive SMS messages using one (or many!) virtual Twilio phone numbers. Using Twilio's extra-special Messaging Copilot technology, you can configure your messaging service to operate at any scale, or in a variety of countries around the world. To get started, we'll create a messaging service that's powered by one Twilio number.
First, navigate to the Messaging Services section of the Twilio console. Create a new messaging service by clicking the plus (+) button.
Give your messaging service a name - it can be anything you want. Choose the "Notifications, Two-Way" use case - you can choose another one if you know exactly what you're doing, but don't sweat it if you don't. This setting should be sufficiently versatile for your Salesforce work.
After creating your messaging service, navigate to the "Numbers" section of its configuration UI.
Here, you'll configure a "pool" of virtual Twilio phone numbers from which your users/customers will receive SMS messages. When SMS messages get sent out from Salesforce, those messages will come from one of the numbers in this pool. How many and what kind of numbers you need in this pool will depend greatly on your use case, and how many messages you will need to send per day.
|Message Volume||Number Pool Needs|
|Less than 250 messages per day||At least one Twilio phone number|
|Less than 1,000 messages per day||At least four Twilio phone numbers|
|More than 1,000 messages per day||Consider a short code (US and Canada), with multiple long codes to use as a fallback based on volume. Contact a Twilio expert to help plan for your needs.|
|More than 1,000 international messages per day||At least one Twilio number, ideally local in the country where you plan to send messages. Check international coverage for SMS here. Contact a Twilio expert to help plan your strategy for international messaging.|
For more information on capacity planning, check out our FAQ on the topic.
That's all you'll need on the Twilio side! Let's take a look at how to install and configure the Twilio for Salesforce package.
During the preview, you'll need to install the Twilio for Salesforce package outside of the App Exchange flow.
Once you get the link, you'll be prompted to install the package in your organization:
Follow the prompts to install the package. If you haven't enabled it already, you may need to enable My Domain for your organization to install the package.
Next, you'll need to configure your Twilio account credentials using the account SID and API keys you created in the last step. In Lightning Experience, you'll find a new page in the Launcher UI to configure Twilio.
Go to this page and enter your Twilio account credentials, which you collected or created earlier. After validating your Twilio credentials, select the Messaging Service you created earlier from the dropdown which appears.
Hit save, and you're all set with your Twilio configuration.
The last step before using the Twilio features in your Salesforce install is to add any users who should have access to Twilio functionality to one of the two new permission sets that were added to your org during installation - "Twilio User" and "Twilio Administrator". A "User" will be able to send and view messages, and generally access all the features of the package. An "Administrator" will be able to view and configure Twilio API credentials.
If you need help finding this feature in the Salesforce Setup UI, check out the video at the top of the page.
That's it! You can now start using Twilio for Salesforce to set up appointment reminders, engage with donors, and generally automate all the things!
Now that your Twilio for Salesforce install is all set, it's time to start sending some messages!
- Send automated SMS messages from Process Builder
- Send bulk SMS messages to Campaign members
- Message Contacts one on one from their Salesforce record page