Release Notes - v5.113.3 (Crestone Peak)

Mogli SMS Release Notes - v5.113.4 (Crestone Peak)

What’s New

• Real-time message composing Insights.

• Incoming SMS records can be routed through a Connected App.

• Dedicated Full Access permission set for Community/Experience Cloud users

• Admin users can now turn off/on Mogli integrated objects 

Resolved Issues

• Bug fix for Mogli Integrated Objects with a Master-Detail Relationship

• Added restrictions to the Site Guest User for Async Tasks

• Bug fix for the Mogli Conversation View opt-out warning banner not updating in real-time

• Bug fix for inactive gateways being displayed in Mogli Conversation View picklist
• Bug fix for issue when creating SMS records that include attached files with long names 
• Bug fix for component error when changing record types 
• Bug fix for Mogli Visualforce page not being scrollable
• Bug fix for Mogli URL Save and Insert button 
• Bug fix for Mogli URL domain creating issues
• Bug fix for Mogli Notification issues with Anonymous leads and bulk messages
• Bug fix for Attachment field on SMS record not working correctly
• Bug fix for Twilio Intelligent Route gateways not displaying message segments
  • Please reach out to a Mogli representative to make sure your Twilio Intelligent route gateway is set up correctly

Update Details

Introducing real-time message composing insights!

Message composing insights gives the user real-time information about their message. This includes the encoding type, number of characters and segments, message channel instructions and limitations, and tooltips with additional information.

The message character and segment counter should be considered an estimate because some features that may affect the values, such as:

• Merge fields - merge fields are processed upon SMS creation. For example, {{Contact.Name}} will be counted literally, 16 characters in this case; whereas the character value will likely differ once the merge field is processed.
• Mogli URLs with personalized engagement enabled - the 6 character slug is processed upon SMS creation. 
  • Note: it will be counted as 7 characters because it is preceded by a slash: /aBCdEf) 
    
• Mogli scheduling links with pre-fill data enabled - the link shortening is processed upon SMS creation. For example, https://scheduler.mogli.com/booking/mike-45 will be initially counted as 43 characters, be shortened to https://scheduler.mogli.com/u/aBcdEf upon sending which will actually be 36 characters.
• Toll-free numbers - when a message is split into multiple segments, the number of characters per segment has a 1-character difference between toll-free and 10-digit-long-code numbers. The segment counter currently assumes all numbers are 10-digit-long-codes and does not account for toll-free numbers.
  • When an SMS exceeds 160 characters using GSM-7 encoding, it's split into 153-character segments for 10-digit-long-codes and 152 segments for toll-free numbers.
  • When an SMS contains 1 or more UCS-2 characters and exceeds 70 characters, it's split into 67 character segments for 10-digit-long-codes and 66 character segments for toll-free numbers.

This feature also includes…

Initial segment value vs. verified segment value

When an SMS record is created & sent, the value from the segment counter is placed on the SMS.Message Segments field. When the message is received and sent by the messaging partner, the status callback into Salesforce updates the SMS.Message Segments field with the actual value from the messaging partner, EXCEPT when using Twilio intelligent routing gateways. See message segment updates for Twilio intelligent routing gateways for more information.

Message character and segment counting and GSM-7/UCS-2/MMS encoding recognition

Message length limitation information

• Twilio: 1,600 characters

• Telnyx: 10 segments

WhatsApp 24-hour window information

Mogli Voice instructions

Incoming SMS records through a Connected App

Prior to Crestone Peak, incoming SMS records have been created by the SMS Site Guest User. Clients can now use a Connected App, which provides an authenticated connection between the client's Salesforce instance and the Mogli API. These processes will be run by the authenticated user, rather than the Site Guest User to create incoming SMS records. This feature requires configuration updates so please reach out to a Mogli representative if you are interested in this feature!

NOTE: By default, incoming SMS records will still be created by the SMS Site Guest User as they have been in the past.

Self Upgrade Instructions

Upgrading to Crestone Peak is simple.

1. Use a list view or report to identify any SMS records in "Queued", "Sending", or "Scheduled" status with a "Scheduled Delivery Date" in the past. If found, please reach out to help@mogli.com for assistance upgrading to avoid any potential issues. If none are found, continue to step 2.

   1. Note: When upgrading to Crestone Peak, ensure that the 'Receive Callbacks through Site Guest User' setting is enabled in the Mogli Application Settings (set to 'True') after you install if you do not intend to use the connected app for status callbacks.

2. Click here to install Crestone Peak in production (click here for sandbox).

3. Log in to Salesforce.

4. Install for Admins Only.

5. Confirm that the install has been completed by checking your email or navigating to Setup > Installed Packages and checking that Mogli SMS is version 5.113.4.