NetSuite | 2023 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 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.8.1 - 19 Dec 2023

Bug fixes and refinements

• Update released to fix an issue with timestamp of Batch Messages in the Conversational User Interface history.

Version 5.8.0 - 5 Dec 2023

Batch MMS

Sending batch Multimedia Messaging Service (MMS) messages is now available within the Batch SMS composer. With the updated attach button, PNG, JPEG, or GIF images up to 409 KB can now be sent to recipients in Australia and the United States through saved searches, and the images are saved as attachments in the recipient message history.

Bug fixes and refinements

• Update released to fix a blank page issue impacting the templates list when templates include custom metadata records.
• Batch SMS Bug fix effecting certain transaction record scenarios.

Version 5.7.1 - 10 Nov 2023

New SMS Templates UI

To help with Unicode detection in templates we have updated the New Template page. Here's what the old version looked like:

The new version:

• All of the field options are still there, on the left.
• We've added a toggle switch to automatically detect Unicode characters in your template. When this is switched to on, Unicode characters in your message will highlight, as shown in the above image.
• We've also added an alert that will appear below your message if Unicode characters are present - learn more about Unicode and character limits here.

• Template List Refresh - we've updated the design of the Template list to make it easier to preview and search for templates:
  • A) We've added the ability to search by Template name or content.
    B) You can now preview the content of each template.
    C) You can sort by the last modified date.
    D) You can sort by the user who last modified templates.
    E) We've added actions inline with each templates to Edit, View or Delete.
    
    

Bug fixes and refinements

With the latest update, the Webhook Configuration page now features enhanced security, keeping API secrets and Token secrets obfuscated for an added layer of protection.

Version 5.6.0 -23 Oct 2023

Bug fixes and refinements

• Batch SMS Improvements - this update brings enhancements to the Batch SMS sending, resulting in a processing speed increase of up to 40% more messages sent for the same time period.

Version 5.5.1 -21 Aug 2023

Bug fixes and refinements

• Expandable Message Composer - when you're writing a long message in Conversations, you can now increase the size of the message composition window to see the entire message:
  
• Resolved Batch SMS scenario where a saved search with 0 recipients is allowed to send.
• Resolved Bug affecting customers who have customised set-ups where the Conversations Button had been added to non-standard records. The correct SMS button is now showing for the specific record.

Version 5.5.0 -24 Jul 2023

Single & Batch SMS UI Refresh

In the spirit of consistency, we've levelled up our Single and Batch SMS screen to align with the experience in the Conversations Window. The refresh includes:

• The same handy Unicode alert when special characters are detected in your message.
• The same easy-to-use toggle switch to highlight Unicode characters so you know exactly where to find them if you want to remove them to keep your SMS costs down - learn more about Unicode and character limits here.
• New separate Send and Schedule buttons  - again, this is just a cosmetic tweak, the function will remain the same - conveniently now located on the message composition page, removing the need to navigate to another tab.

• We've introduced the new-look preview screen that updates in real-time when you start typing in the compose message window.

  

  

Version 5.4.2 - 16 Jul 2023

Bug fixes and refinements

• The ampersand symbol now displays correctly when sending from the conversations window.

• Sender IDs that are set for a workflow are now properly recognised.

• When sending Batch SMS to recipients from a saved search that includes the field type "invoice", message deployment is successful and send receipts are created.

Version 5.4.1 - 1 Jun 2023

Bug fixes and refinements

• Remedied inconsistent scheduling for recurring Batch SMS due to daylight savings time - only customers outside of the US were impacted.
• Resolved where the SMS preview in the conversations window was displaying HTML characters.
• Extra tweaks to the size of the conversations window when opened - the bottom edge of the window is now properly displaying within the boundary of the browser window.

Version 5.4.0 - 23 May 2023

Unicode in the Conversations Window

No more bill shock! Now you can clearly see when you're using Unicode as part of your message.

• 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.

  

  Note: The cost of messaging depends on how many messages are sent, and the number of messages sent is influenced by how many characters are used to write them. Learn more about character limits here.

• As part of the update to include the Unicode alerts, there's also a new separate button for Scheduling your message. Don’t worry, it’s only a small cosmetic tweak, the function still operates the same.

  

Bug fixes and refinements

• Adjusted the size of the conversations window when opened, removing the need to scroll across.
• Resolved the issue where scheduling a message would intermittently change the date format.

Version 5.3.0 - 28 Mar 2023

Bug fixes and refinements

• Sender IDs in the Conversations window are now displaying the sending number and name label, consistent with Single and Batch SMS.
• alphanumeric sender IDs (Business Name) and their grouping label have been removed from the Sender ID field in Single and Batch SMS for USA, CA, and NZ ONLY, consistent with the Conversations window.

• Fixed Batch SMS Scheduling

  • We've updated the code for processing the recipient list of a scheduled batch message. The recipient list is now processed at the specified sending date and time, instead of once daily.

  • Deployment scripts for scheduled and recurring messages have been improved. They now run hourly, instead of a single daily deployment. This will greatly improve the accuracy of the message sending time.

    Note: The new process flow will not apply to existing Recurring Batch SMS jobs. You'll need to disable the recurring batch job and create a new one.

Version 5.2.0 - 28 Feb 2023

Sender IDs in Workflows

We've taken the ability to select a Sender ID when sending SMS from NetSuite, and levelled up by also giving you the ability to specify a Sender ID for a workflow. Any Sender IDs you have in the MessageMedia Hub will be added to NetSuite when the integration is installed or updated. If you'd like to view a list of your Sender IDs in NetSuite, you can:

• Go to MessageMedia SMS > Preferences > MessageMedia Preferences
• Click on New MessageMedia - Preferences button, or click on Edit | View next to the current preferences record.
• Then select the Workflow Sender IDs tab:

• You can also find a list of your Sender IDs by going to:
  • Go to Customization > Lists, Records, & Fields > Record Types
  • Locate the record for MessageMedia – Workflow Sender ID
  • Then click on List:
    
  • This will show you all your Sender IDs that have been set up in the Hub:
    

FAQs

• How often are Sender IDs synced?
  Scheduled - there's a scheduled script that runs every day at 1 AM for each relevant time zone (AEDT, NZDT, GMT, or PDT).
  Automatic - NetSuite will automatically sync with the Hub during any upgrade, and at the time of installation.
  Manually - there's a Sync Sender ID button (under MessageMedia SMS > Preferences > MessageMedia - Preferences) that you can use at any time to perform a manual sync.
• I’m not seeing an updated Sender ID list. What should I do?
  NetSuite pages don’t automatically refresh, you'll need to either refresh your browser or switch between the sub-tabs (e.g. Notes and Workflow Sender IDs).
  
• If I already have workflows set up but haven’t set up Sender ID, will my workflow be impacted?
  No, these workflows will work as before and use the default number already set up.
• What if I delete a Sender ID from my Hub account?
  If you delete a Sender ID in the Hub, any NetSuite workflows specifically using that Sender ID will fail to trigger and will result in an error message and no record of the transaction. When the two platforms are synced, the deleted Sender ID will appear in red with a cross next to it, and the status will be updated to Deleted. This means you'll have to edit your workflow to include an active Sender ID - you can learn how to do that here.
  
  If the Sender ID isn't assigned to any workflows, the deleted Sender ID will just be removed from NetSuite during the next sync event.

• If I'm a new customer and have no API credentials, when will I see my Sender IDs? 
  You won't be able to see your Sender IDs until you set up your API credentials.

  Note: Only Sender IDs assigned to workflows are listed in your NetSuite preferences. For Batch SMS, Single SMS, and Conversations retrieve your Sender IDs when you click the Sender ID dropdown menu. Check out the Release Notification for Version 5.1.0 below for more information.

Bug fixes and refinements

• Sender IDs are now searchable in the Conversations window (currently not searchable in Single and Batch SMS).
• In the Conversations window, alphanumeric sender IDs (Business Name) and their grouping label have been removed from the Sender ID field for USA, CA, and NZ ONLY.
• Removed the ability to click the "Send" button twice, meaning there's no chance of accidentally doubling your SMS bill.

Version 5.1.0 - 19 Jan 2023

Sender IDs

Now you have the ability to select a Sender ID when sending Single SMS, Batch SMS, and from Conversations. The Sender ID will be pulled from the MessageMedia Hub, and it will be displayed as a phone number and label:

This label can be changed from the MessageMedia Hub - you can learn more about configuring Sender IDs here.
When sending any message - Single SMS, Batch SMS, and Conversations - the Sender ID will be saved in the generic SMS record:

FAQs

• What does the Sender ID look like?
  It'll be the same phone number and name in the Hub.
• Can you update the name within NetSuite?
  No, not at this stage.
• What happens if there is no Sender ID?
  Messaging will behave as it did before, whereby the MessageMedia Hub chooses the default Sender ID.
• Will there be a Sender ID selected by default in single SMS, batch SMS, conversations, and workflows, or does the customer need to select it?
  The default Sender ID that would be selected is the default Sender ID that was set in their Hub account, but if using a shared number the default will be left blank.
• Do I need to configure anything to set up Sender ID?
  No need to configure a thing, the integration just pulls the number you have directly from the Hub. As long as the Sender IDs in your MessageMedia account are verified, you're good to go.
• What happens with individual API credentials that are set up in NetSuite?
  The hierarchy to retrieving the API credential is: Individual, then global. If there's an individual API credential for that user, we'll use that to retrieve the sender list.
• Is Sender ID a required field in Batch SMS and if not does it just select the default?
  It’s not required. it will just use whatever is selected on the drop-down.
• Is there a page where a list will show all Sender IDs or is it just a drop-down when I go to select Sender ID?
  For single SMS, Batch and conversations we pull these numbers directly from the MessageMedia Hub, we do not save it to NetSuite, you can only see the list through the dropdown or on their hub account
• Does that mean with single SMS, batch SMS, and conversations, there's a call to the hub every time a message is sent?
  Every time the customer opens the window to write a message, we will call the Sender ID list.

Bug fixes and refinements

• You can now create a recurring batch SMS when your saved search has zero recipients.
• When a Batch SMS is finished (with or without error), its status has been updated to Finished or Recurring rather than Stuck in Queue.
• Removal of line break at the beginning and end of messages that was occurring for some Batch SMS – line breaks appeared only on some phones, depending on the messages app that the phone was using.
• Improved error logging for Batch SMS.
• Phone number validation improvement:
  • Have resolved where some US Customers have recipient phone numbers in a format that starts with 64 (e.g. 646-658-7370). The platform would then recognize that number as an invalid international phone number, so the script takes the default country code preference (usually US) so that it knows to add a +1 and the message is successfully sent to +1 646-658-7370.
  • Originally the validation would occur at the first step and validate that number as a valid New Zealand number (e.g. +646-658-7370).
  • We have now changed the flow so that the script validates the number with the default preference in the first step using the MessageMedia preference or recipient address to determine that a +1 needed to be added.
• Removal of the “is recurring active” checkbox under Recurring Options as this is managed under Recurring SMS Job.