Menu

Expand
Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Changelog

Version 4.21

  • Fixes an issue where allowing Twilio for Salesforce's license to expire would cancel the scheduled job that fetches messages from Twilio. The scheduled job now automatically restarts when an admin visits the Twilio Configuration page.

Version 4.16

  • Adds a toggle to the Personal Phone Numbers configuration panel that allows users to receive chatter notifications when a message is sent to their personal phone number.
  • Adds a configuration banner that shows how much longer the trial will last.
  • Fixes an issue where certain configuration settings would not change when saved.
  • Fixes an issue where Sandbox orgs were required to have licenses assigned, despite this functionality not being available in the Sandbox. Sandbox orgs no longer require licenses.

Version 4.12

  • Fixes an issue where production instances of Twilio for Salesforce would show a "hasAccessToApp of null" error for users who were not provisioned a license.

Version 4.10

Features:

  • Bulk assign personal phone numbers using data loader. Previously Salesforce users needed to have each phone number assigned individually in a process that required several clicks. Now, Admins can upload a spreadsheet of User IDs and phone numbers to provision personal numbers for many users at once.
  • Opt-ins for 1:1 SMS Component. Previously Opt-ins would only stop messages from being sent via campaigns. Now, Admins can require that an opt-in be present in order for Salesforce users to message from the 1:1 SMS Component. If a recipient does not have an opt in, a Salesforce user won’t be able to message them from either the contact record or the SMS Inbox.
  • Messages to personal phone numbers appear in the SMS Inbox. Previously, a user would only see an SMS appear in their inbox if is was sent from a Lead or Contact record that they owned. Now, any message that is sent to a Salesforce user’s personal phone number will appear in that user’s inbox.

Bug Fixes:

  • Fixed the “De-referencing null object” error. When a Salesforce user did not have a first name set, the package would throw a “De-referencing null object error”.
  • SMS Campaigns Component permission set bug fix. We identified Twilio for Salesforce’s permission sets did not require all of the fields needed by the SMS Campaign Component. In some cases, if a user had certain field visibility restricted this would cause an internal server error on the campaign component.

Version 4.6

1:1 Messaging

  • Added the SMS inbox component

  • Supports sending and receiving images with MMS

  • Shows message delivery status

  • Tracks last message delivery status on contact

SMS Campaigns

  • See campaign potential deliverability

  • Send images in campaigns

  • Schedule campaign messages for future sends

Process Builder

  • Now supports initiating outbound chatbots / Voice IVRs with Twilio Studio

Configuration

  • Schedule messages to be archived

  • Set personal phone numbers for Salesforce users

  • Determine if everyone can see all messages in the inbox, or just ones on leads/contacts that belong to them

Opt-In Handling (New)

  • Define an opt-in keyword that a user can text: creates a record that the user opted in

  • Associate a campaign with the opt-in keyword

Version 3.0

  • Added the ability for SMS to be pushed into Salesforce from a Twilio function. Previously, messages would appear in Salesforce within 15 seconds if a user was viewing the contact, or would be pulled into the organization every 15 minutes as a process. With SMS message pushing enabled, messages appear in real time.

Version 2.3 and below

  • Basic 1:1 SMS Messaging component (no delivery status tracking or MMS).
  • Basic SMS Campaign Component (no delivery status tracking, MMS, or scheduled sending).
  • Send SMS from Process Builder (no "Send to Studio" Apex class).
Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.