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 NetSuite 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 5.0.4 - Nov 2022
Improved messaging
MMS different file types and sizes (depending on your carrier you can send different message types – for example, jpg, mp4 etc and different sizes per carrier – please check with your carrier to confirm). Remember - MMS messages are charged at a higher rate than normal SMS messages, so make sure you double-check your costs before sending.
- With sent messages if there was an unsuccessful delivery status it would be stuck as submitted, we've updated our labels to read failed rather than submitted.
- Invalid merge field notification is shown when a customer clicks send, rather than when they’re typing the message.
Improved phone hierarchy
If the user sets the phone field preference to "Any", we've improved how the platform looks for the next available phone number in this order:
- ‘Mobile’
- ‘Work’
- ‘Alt. Work’
- ‘Home’
- ‘Office’
Bug fixes and refinements
- Attach file button is only shown when the phone number is MMS enabled (this will only be out when Sender ID is out).
- Improved UI - long initials are now not cut off but sized to fit.
- Removing deprecated code to ensure the efficiency and performance of the app and technical team (1248).
- When selecting all in Batch SMS - the status and total selected should equal processed plus failed accounts.
Version 5.0.3 - Oct 2022
Bug fixes and refinements
- Removed additional curly brackets {} that were being added in merge fields when loading a template.
Version 5.0.2 - Sep 2022
Bug fixes and refinements
- MessageMedia's Netsuite SMS platform has recently extended the conversations button to additional records enabling you to easily see two-way conversations and the message history in one centralised location.
- We've also added the Conversations feature on Partner and Employee records. It's now included on Customer, Lead, Prospect, Employee, Contact, Vendor, and Partner Records
Version 5.0.1 - Sep 2022
Bug fixes and refinements
- Following customers upgrading from V4.8.2 to the SDF bundle, they were getting an "insufficient permission” suitescript error when attempting to edit a field. This has now been fixed and the records are now saved without error.
Version 5.0.0 - Aug 2022
Conversations feature
We've made the process of sending and managing 1:1 SMS messages a lot easier by combining the SMS button and the Conversational UI button into one Conversations feature. The Conversations button allows you to easily send messages to and from your customers in one place.
There's also a handy files area that lets you quickly find incoming files that have been sent via an MMS rather than having to wade through a multitude of messages to find the file you're after.
All configuration information on the single SMS button, including the header and footer, has now been merged under one button called "Conversations”.
The Conversations feature is included in Customer, Lead, Prospect, Contact, and Vendor records.
Version 4.8.2 - Aug 2022
Bug fixes and refinements
Updated batch message status from "Stuck in Queue" to "Finished". Stuck in Queue would occur when recipients in a batch SMS job have an invalid number – the status is now updated to Finished with the correct number of failed SMS saved on the record
Version 4.6.1 - Jun 2022
Bug fixes and refinements
- Updated phone number validation. Previously the phone number validator would strip leading zeros first, then add a “+” and would then try to validate. This can result in a valid phone number even if the number is invalid. The phone number validation process is now:
- The phone number is validated against the default dialling country set in preferences. Leading zeros will be stripped and the number will add a '+' in front of the number.
- If no default dialling country is set in the preference, the phone number is then validated using the country of the entity. Leading zeros will be stripped and the number will have a '+' at the start of the number.
- If both the default dialling country and country of the entity are not set. The phone number will be validated as is. This assumes that the phone number entered could have the correct dialling country. Leading zeros will not be stripped and the number will be preceded by '+'.
Version 4.5.0/4.5.1 - Mar 2022
Bug fixes and refinements
Previously reply communications record was only attached to the recipient customer entity and no record was attached to the originating Sales Order. This release includes a reply communications record for replies to messages sent via the sales order for both the originating Sales Order and the recipient customer entity.
Version 4.4.0 - Mar 2022
Bug fixes and refinements
Implemented date filters to reduce the volume of messages needing to be migrated, and warning messages when a large amount of data is being migrated. When large volumes are being migrated, it would take a significant amount of time to process.