Stay in the loop with Sinch SMS updates
This is where you’ll find the latest releases, features, and improvements to the Sinch SMS for Salesforce integration.
Follow this page to get notified when new updates are live.
Planning to update your app?
We recommend doing this at the start of the week - that way, our support team is ready to help with any questions as you go.
Version 1.40 - 06 Dec 2023
SMS for Reports
We've introduced the ability to send an SMS message to all records within a report.
The reports feature in Salesforce allows you to segment your report across multiple objects and fields, which means that now when you're sending a single SMS to multiple recipients, you can really refine the recipient list to better engage with your target audience.
FAQs
-
Am I restricted to only sending 2000 messages like Bulk SMS?
No, you can send messages to up to 2 Million records.
-
Do I need any particular fields in my reports for this feature to work?
Yes, you need to include the Object ID and the phone number of each record.
Bug fixes and refinements
- The Message Feed now properly loads in the Field Console.
- When using short trackable links:
- The character count will now display the correct number of characters used in your message.
- Existing templates that feature short trackable links can now be edited.
- Templates that include MMS images will now properly load onto the UI.
Version 1.37 - 06 Nov 2023
Default 'Send To' Number
We've introduced the ability to send an SMS message to all records within a report.
We’ve now enabled the ability for our customers to set their default send to number.
We understand that not everyone uses Mobile phone as their send to number, so we want to create an easy to use Advanced settings feature for customers to select the right number to default to, saving time and effort when sending your messages. This includes all standard objects and custom objects.
To update your default send to number please go to the Setup & Configuration page, expand the Advanced Settings, then go to Set your default send to number. Select the object and default number. Click Update.
If this is left blank the default will remain as Mobile number.
In-App Notifications for New Releases
We want to make sure our customers are notified of the latest release with a link to our Release Notes, rather than relying on an email update getting to the Salesforce User.
Notifications will be shown on the following pages:
- Setup & Configuration page
- Account Management page
- Template
- Send SMS and Bulk SMS
This will be shown to all users (admin and standard user).
To remove the notification, click on the cross at the top right hand side of the pop up.
Bug fixes and refinements
- Ability for pending TFN to send messages - note that daily limits apply for toll free numbers that haven’t been verified yet.
- Updated Default sender account on Bulk SMS - if you’ve started composing a message and realise you need to change the Sender ID, your message will remain saving you time retyping this message. Only messages during a trial will be replaced with a generic message.
- When Unicode warning message was shown, this was hiding the last SMS in the Message Feed, this has now been resolved so you can see both the warning message and your last message in the feed.
Version 1.32 - 25 Sep 2023
Easy Onboarding
We've introduced the ability to send an SMS message to all records within a report. You can get set up quicker than ever before and start communicating with your customers.
The new onboarding process simplifies set-up by reducing the number of configuration steps from 10 down to 4.
Note - Existing customers keep the current (legacy) Setup & Configuration page.
FAQs
-
I'm an existing customer, do I need to use oAuth?
No, there's no change required for existing customers at this time. If this changes in the future, we'll let you know. If you're on the older UI screen and click Connect existing account, this will update your Setup and Configuration page to the new screen.
Bug fixes and refinements
- Customers using Service Appointment and Objects without a name field can now successfully send SMS.
- The outbound scheduler has been removed from the set-up and configuration page as it has been turned on by default for all new customers.
- Improved error tracking when an error occurs during a flow or bulk message job.
- Removed the Sender ID when Cloaking is enabled.
- Resolved the issue where following sending a message via a sub-account, the Sender ID would automatically return to the account default - the sender ID will now remain set to the most recently selected/used.
- Improved phone number validation for Person Account object.
- Updated the MMS file extension to be lowercase as some files were failing to send.
- Confirmed that Mercury SMS is compatible with Salesforce Summer '23 release.
Version 1.31 - 11 Jul 2023
Unicode Highlighting in the Message Feed
We’ve introduced a warning when you’ve included Unicode characters in your message.
There’s also an easy-to-use toggle switch that highlights any Unicode characters, so you know exactly where they are if you want to remove them to keep your SMS costs down. Learn more about Unicode character counts here.
Short Trackable Links
If you have Short Trackable Links (STL's) enabled, the character count in the message builder will now show the STL.
- You'll also be informed if STLs are not enabled.
- You can preview the STL to see how it will appear to your recipients when they receive your message.
- Link clicks for STLs will appear in the message feed. You can also see link clicks in your Salesforce reports.
Bug fixes and refinements
- Keyword improvement - now when your customers text in a keyword, there doesn't need to be a space between the keyword and their answer for the keyword to be recognised. For example, #email email@example.com and #emailemail@example.com will both work.
- Updated more fields to be in alphabetical order - this will make it easier to find the field you want to use.
- Renamed the "none" license to "universal" - this will make it easier to understand license types.
- Added US API end point to improve performance for US customers.
- Added loading icon to show that pages are loading.
- Improved error logging for bulk sends.
Version 1.27 - 27 Mar 2023
To ensure you get the most out of this update, we recommend that you assign the Universal Permission Set to all users. If your organisation is using Custom Mercury Permission Sets, the update will not correctly take effect.
Delivery Status in the Message Feed
We've added a delivery status to sent messages in the message feed. Now when you're sending 1:1 messages in real-time, you don't have to navigate away from the message feed to confirm your messages are successfully delivered.
Bug fixes and refinements
- Streamlined the Sending Experience - We've updated all Send SMS pages so whether you’re sending from the Bulk SMS Manager or via the single Send SMS view, the experience will be consistent.
Version 1.24 - 01 Feb 2023
Add a new Permission Set named 'Mercury SMS None License'
Users with a Salesforce Platform license are now able to send SMS through Mercury SMS. When first installing Mercury SMS, if the admin clicks to install Mercury SMS for all users, they are not required to assign permission sets to users. In release 1.23, we created a new custom Field, and because users did not have permission sets assigned, it caused them to not be able to send SMS. This new permission set allows them to continue sending SMS.
If you have users that cannot send SMS, please go into the Setup and update their permission set to 'Mercury SMS None License'.
Version 1.23.1 - 31 Jan 2023
Bug fixes and refinements
- Resolved where some users couldn't receive inbound MMS.
- Automatically updated incorrect Account IDs for some users as it caused them to not be able to send SMS.
Users do not have to do anything for these changes to take effect.
Version 1.23 - 12 Jan 2023
Sender IDs
You now have the ability to select a Sender ID when sending a message, and you can use this feature when sending messages using:
- Single SMS
- Bulk SMS
- Message Feed
- SMS Templates and Workflows
- No changes need to be made to your account, if you have multiple Sender IDs they will automatically show when sending an SMS.
- The Sender ID will default to the Sender ID a user has used most recently.
- If you don't have additional Sender IDs but would like them, please set this up in the MessageMedia Hub.