Salesforce | 2026 Product Release Notes
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.
Current Version: 1.85
Each new release of Sinch SMS for Salesforce is first available for manual upgrade on the AppExchange. We then automatically roll it out to Sandbox Orgs, followed by Production Orgs.
- Released to Sandbox commencing 16 November 2026
Version 1.85 - 16 Nov 2026
Rich RCS for Salesforce: Rich cards and carousels
Sinch SMS for Salesforce has been updated to support rich card and carousel content on the RCS channel. This addresses the previous limitation where RCS messages sent from Salesforce were restricted to text and suggested replies, with no support for media, rich cards or actions.
Selecting an RCS sender in SMS Templates now opens a rich card editor in place of the plain message box. The editor supports two message types: rich cards and text messages.
Rich cards: Each card supports a media item, a title of up to 200 characters, a description, and up to four buttons.
Carousels: Up to 10 cards per message. Cards can be added, duplicated, reordered by dragging, and switched using the tabs above the card.
Prebuilt layouts: Four starting layouts are provided - Product carousel, Promo card, Event invitation, and Featured product. A blank card is also available.
Button actions: Buttons can be configured as a reply, a link, a call, or a location. Apply to all cards copies a card's button set to every other card in the carousel.
Card height: Medium or Large, applied to all cards in the message.
Merge fields: Insert field is available in card titles and descriptions, so card content is populated per recipient at send time.
Text messages: Plain RCS text with up to four buttons, rendered to the recipient as suggestion chips.
Rich RCS for Salesforce: Rich cards and carousels
RCS templates now support an SMS fallback, configured on the template itself. Where a recipient's device or carrier cannot receive RCS, the fallback SMS is sent instead. This addresses the previous limitation where RCS did not support SMS fallback.
Fallback is enabled per template using the SMS fallback option below the card editor.
A fallback sender and a fallback message are both required once the option is enabled. The template will not save without them.
The template preview gains an SMS tab showing the fallback message as the recipient will receive it.
Fallback configuration is stored on the template and applies wherever that template is sent from.
Send test for RCS templates
A Send test action has been added for RCS templates. It sends the saved template to a nominated mobile number, entered with its country code, so card rendering can be verified on a handset before a bulk send.
Send test uses the saved version of the template, not unsaved changes in the editor. Save the template before sending a test. Send test is available for RCS templates only.
Rich message rendering across sending surfaces
Rich card and carousel content now renders in the Message Feed, SMS for Report, and Bulk SMS Manager.
Message Feed: Sent and received RCS cards render in the conversation with their buttons. Carousels can be paged through. Selecting an RCS template in the composer displays it as a read-only card with merge fields resolved for that record.
SMS for Report: Selecting an RCS template replaces the message text box with a read-only card. Cards are sent as defined on the template, with merge fields resolved per recipient.
Bulk SMS Manager: RCS templates are offered at the Message step and displayed as cards, then summarised at the Review and send step.
In the Message Feed and SMS for Report, Edit as text converts a selected template into editable plain text, which is then sent as a standard message rather than as cards.
The template picker lists only templates the selected sender is able to send, for the object being messaged. Changing to a sender that does not support RCS displays a warning that the template will be sent as plain text.
Files that exceed the size limit or use an unsupported format are rejected with a message. Existing message content is retained. Current limits:
- Cards per carousel: 10
- Buttons per card: 4
- Card title: 200 characters
- Card media: PNG, JPG or GIF, up to 2 MB
- Video on RCS text messages: MP4, up to 10 MB
- Card height: Medium or Large, applied to all cards
- Button types: Reply, link, call, location
- Merge field support: Card titles, card descriptions, and text messages
- Recipients per bulk send: 2,000 using Select all. Sends above 100 recipients are processed in the background.
You can install the managed package from the 1.85 install URL. We recommend upgrading at the start of the week, so our support team is available to help with any questions as you go.
Version 1.70 - 22 Jan 2026
Sinch SMS System User permission set
We've added a new permission set, Sinch SMS System User, for Salesforce integration and API users that send messages but don't use the Salesforce interface.
Integration users often can't be given a Sinch Universal License, so many customers use a custom permission set instead. Custom permission sets don't pick up new fields or Apex classes when the package is upgraded, which can stop messages sending until an admin adds the missing permissions. This new permission set is managed in the package, so it updates automatically with every release and doesn't need a seat license.
It includes:
Access to the Apex classes used to send SMS, WhatsApp and RCS messages
Full access to all Sinch objects and fields, including those added in release 1.65
Access to the package's custom settings
As it’s for API use only, it doesn't include application visibility, Visualforce pages or tabs.
If you’re already set up, you don’t need to do anything. If your integration user uses a custom permission set, we recommend switching to Sinch SMS System User so future upgrades don't need manual permission changes. Test in a sandbox before upgrading production.
Version 1.69 - 16 Jan 2026
Campaign Members performance improved
We've optimized how the package handles Campaign Members, so campaigns with very large data volumes run more efficiently. This is beneficial for customers with large Salesforce data sets, particularly those with more than 10 million records.
The improvement applies automatically when you upgrade to this version. As with any package upgrade, we recommend testing in a sandbox before upgrading production.