Check out these release notes to keep on top of all the latest improvements and additions to the SMS for Dynamics app. We’ll keep adding to this list with every release, so follow this page to be notified whenever we add something new.
To access new features and maximise your SMS for Dynamics experience, make sure you update SMS for Dynamics to the latest version - this article can show you how.
Current Version
1.87
Release
February 2025
2025 Release Notes
Version | 1.8.7
Release | February 2025
Here's an overview of everything that's included in this update:
New Feature
-
Workflow Sender ID and User Support:
Businesses with multiple Sender IDs on their account can choose which Sender ID or Alphatag (refer to the Sender IDs section for more details) will appear as the sender on the recipient's handset. Additionally, they can specify which user’s activity will be logged in the communication timeline when the message is received.
-
Custom entities outside of Accounts, Contacts and Leads are now supported.
To leverage the new features:
- Select Version 1.1 when adding the SMS for Dynamics.Workflow
- When setting the properties for the flow:
- Sender ID - Optional Field to enter the provisioned Dedicated number, Toll Free number or 10 DLC in E.164 international format (e.g. +614xxxxxxxx) so it appears on the phone as the sender. Shortcode in local format without the country code and Alphanumeric (Alpha Tags) sender IDs that have been provisioned can be entered without spaces. If this is left blank the sender ID will default to the Sinch Engage Account settings.
- From - Optional field to specify the user the message will be logged as from in the communication timeline, reply messages will be routed back to the user. This can be a dynamics field eg Lead Owner. If this is left blank the from references the user who triggered the workflow.
- ToNumber - Recipient mobile number field to receive the message.
- Message - This is where you create your message.
- Is Opt-Out? - To send to recipients who haven't opted out.
- CreateSMSRecord - To log the message. For Custom Entities, if CreateSMSRecord is set to True then creating a new activity must be enabled on the entity. Otherwise CreateSMSRecord must be set to False.
Small Tweaks & Bug Fixes
- Missing Permission warning banner when sending user needs to have their Permissions updated to receive replies
- Conversational UI performance improvements.
- Resolved duplicate inbound notifications issue.
-
Resolved an issue with users sending to each other.
Comments
0 comments
Article is closed for comments.