Mercury SMS Release Notes

Find out all about the latest features to be added to Mercury SMS

For all the news of the latest features that have been added to Mercury SMS, make sure you take a look at the Release Notes below.

Release Notes - Version 1.13

Version 1.13  Release Notification
6 June 2018

Download PDF

A new version of Mercury SMS (version 1.13) will be released on the AppExchange on Thursday 7 June 2018. This notification has been issued to existing Mercury SMS users. It contains an overview of the new features available with this release, along with instructions on how to upgrade to the new version.

What’s new?

This release comprises of a number of enhancements to existing functionality, along with some new features. You’ll find details of all the new features below.

Bulk SMS Manager Enhancements

A number of small enhancements have been added to the Bulk SMS Manager, which are detailed below.

Duplicate Management

Previously, if you had more than one record in the set of records that you’ve selected that contained a matching number, an SMS would have been sent to each instance. Now, where duplicates are found in the list, only one message will be sent to the recipient.

Please note, in order for the de-duplication process to apply, the number must match exactly once white space and special characters have been removed. For example, (207) 123 4567 will match 207-123-4567, but 1 207 123 4567 will not.

Merge field values will be taken from the first record (for example, if the first record had a name of Chris and the second record had a name of Christopher, the merged field value would be Chris). A Task will be stored against each record found. Inbound replies will only be matched back to the original record, not the duplicates.

Select All / Deselect All

Previously, when you wanted to select all of the records returned from a specific List View, you had to click through each page and tick the ‘Select All’ Checkbox. To allow you to quickly select all records in the list view, you’re now able to click the ‘Select All Records’ link, which will select all records returned in the List View, not just those on the current page. You can click the ‘Deselect All Records’ link to quickly deselect all records. See below for location of these links.

Send Later

You will now have the option to compose a message and chose to ‘Send Later’ rather than having to send it immediately.

To schedule the message to be sent at a later time, click the ‘Send Later’ button.

This will open up the ‘Schedule SMS’ window so you can set the Date and Time that you would like the message to be sent.

Task Tag

A new Field has been added to the Task Object called ‘Tag’. This field is available from the Bulk SMS Manager and from the Bulk SMS feature on the Campaign Object. The purpose of the field is to ‘tag’ the message so all Tasks sent or received as part of this Bulk SMS send can easily be filtered in reports.

Note: You may need to add this to your Task Page Layout and set the Field Level Security so the field is visible to your users.

SMS Inbox Enhancements

Two new features have been added to the SMS Inbox, each of which is detailed below.

New Message Sound

When a new inbound message is received, it’s now possible to have the SMS Inbox play a sound, notifying you of the arrival of the new message.

There is a new icon in the header of the SMS Inbox that lets you unmute / mute the notification sound.

To enable the audio notification, there is a new setting that has been added to the Setup & Configuration page within the Configuration section.

Restrict Permissions to look at other Users

A new field has been added to the User record that will allow you to specify whether a User has the ability to switch to view another User’s SMS Inbox messages.

If you want to disable the ability to switch, you can set the ‘Disable User Switch in the SMS Inbox’ field to TRUE. This will remove the ‘Select User’ picklist at the top of the SMS Inbox.

Note: You may need to add this to your User Page Layout and set the Field Level Security so the field is visible to your users.

System-wide Opt Out

Previously the SMS Opt Out feature was only available on the Lead and Contact Objects. The SMS Opt Out logic has now been enhanced to where you can configure it to work with any Object (Standard or Custom) in Salesforce.

To configure the Opt Out process for an Object, you need to create a Checkbox Field on that Object, ensuring it is labelled as follows:

Field Name: SMS Opt Out
API Name: SMS_Opt_Out__c

When an inbound message is now received containing the phrase ‘STOP’ any ‘SMS Opt Out’ field across any object will be updated to TRUE, preventing you from sending any further outbound messages to that record.

How do I upgrade?

Version 1.13 will be rolled on based on the following release schedule:

  • 7th June – Available to manually upgrade from the AppExchange
  • 16th June – Automatic Upgrade to all Sandbox Orgs
  • 23rd June – Automatic Upgrade to all Production Orgs

To manually upgrade to the new version of Mercury SMS in your organisation, please follow the steps below.

  1. Click aprika.com.au/me-app
  2. Click the ‘Get It Now’ button
  3. Enter your login details (if required)
  4. Click ‘Install in Production’
  5. Click ‘Confirm and Install’ (you may need to login again at this stage)
  6. Select which users you want to install for (‘Install for All Users’ is recommended)
  7. Click ‘Upgrade’
  8. Click Done

Feedback

Some of the new features included in this release of Mercury SMS have come from ideas submitted from existing clients. If you have an idea for enhancing Mercury SMS, you can submit it via email on mercury@aprika.com.au.

Questions?

If you have any questions regarding this release notification, please do not hesitate to contact us on support@aprika.com.au.

What's New Webinar - Version 1.12
Release Notes - Version 1.12

Version 1.12  Release Notification
5 January 2018

Download PDF

A new version of Mercury SMS (version 1.12) will be released on the AppExchange on Friday 5 January 2018. This notification has been issued to existing Mercury SMS users. It contains an overview of the new features available with this release, along with instructions on how to upgrade to the new version.

What’s new?

We are very excited to announce some really cool new features, along with some enhancements to existing features that will allow you to get even more value out of using Mercury SMS. You’ll find details of all the new features below.

Bulk SMS Manager

Previously to send an outbound SMS to a group of records via a List View, you could only do this in Salesforce Classic as it was not supported in Lightning Experience. Furthermore, if you wanted to do a Bulk SMS from a Custom Object, then you were required to create a Custom Button on that Object.

The Bulk SMS Manager now means you’re able to send your outbound messages in bulk to any Object without any configuration. Furthermore, the Bulk SMS Manager works in both Salesforce Classic and Lightning Experience.

You can access the Bulk SMS Manager via the navigation menu in either Salesforce Classic or Lightning Experience, as shown below:

The Bulk SMS Manager allows you to send an outbound message to records within any Object that contains a Phone field in 3 simple steps:

  1. Choose your Data Source
  2. Select your Recipients
  3. Compose your message

Data Source

The Data Source Tab on the Bulk SMS Manager allows you to select the Object, Phone Field and List View. You’re also able to optionally select another three fields to be displayed in the ‘Select Recipients’ Tab. You can then click next to move to the ‘Select Recipients’ Tab.

Select Recipients

The Select Recipients Tab on the Bulk SMS Manager will display all of the records matching the filter criteria in your selected List View. You’re able to select the record(s) you wish to send the outbound message to and then click next to compose your message.

Compose Message

The Compose Message Tab on the Bulk SMS Manager enables you to write out a message manually or select from a template. You’re also able to include merge fields, specify the MessageMedia account you wish to send the message from and preview your message. Once you’re ready, simply click ‘Send Now’ and the message will be sent to the selected recipients.

REST API

To date, Mercury SMS has been using MessageMedia’s older legacy API. We’re pleased to announce that we are now also integrated with their new REST API. This provides a lot more functionality and will be the API we use for all future developments. The legacy API features within Mercury SMS will continue to work, but all new functionality will require a MessageMedia account with REST enabled.

There are a number of immediate benefits available as part of the REST integration. These are summarised below:

  • Delivery Notifications – you can now report on the delivery status of SMS messages within Mercury SMS. This is a new field added to the Task Object called ‘SMS Status’. Note, this is a service MessageMedia will need to enable for your account and will incur a per message fee directly from MessageMedia
  • Inbound MMS – as explained below
  • Thread Matching – enhanced thread matching, as explained below
  • Error Handling – the ‘SMS Status’ field will be updated if the message was unable to be delivered

To begin taking advantage of the REST API, you will need to submit a request to MessageMedia by emailing support@messagemedia.com. You will also need to provide them with your ‘Web Push URL’. Once this has been done, they will provide you with REST credentials for your existing MessageMedia Account(s), you’ll find additional fields on the Setup & Configuration and Account Manager pages for you to enter these credentials.

In support of this new feature, a new Custom Object has been added. The ‘SMS Message’ Object will contain records for any inbound message received. This object will be used to manage the creation of the Tasks for inbound messages, as well as updating the Task’s ‘SMS Status’ field if you choose to have Delivery Notifications enabled. A benefit of this new object is that the Site Guest User will only need access this one object, rather than needing access to all of the various objects you may need it to associate inbound messages to. You will need to ensure your Site Guest User has full read/write access to this Object. To do this, navigate to Setup > Sites > Mercury > Public Access Settings > Edit and ensure the Custom Object Permissions for ‘SMS Messages’ looks as shown below.

You will also need to check the Field Level Security for this Object for the Site Guest User. To do this navigate to Setup > Mercury > Public Access Settings > Scroll down to Field Level Security > Click View for ‘SMS Message’ and ensure all Fields are TRUE for Read and Write access, then click Save.

You will also need to activate the Remote Site called ‘MessageMedia_Rest’. The Remote Site will already be created once you’ve been upgraded, but will require activation. To do this, please navigate to:

Setup > Remote Site Settings > Edit ‘MessageMedia_Rest’

Set ‘Active’ to TRUE > Click Save

You’ll now be ready to use the new REST API service.

Inbound MMS

You are now able to receive inbound MMS. The photo will be attached to the Task record and will appear in the SMS Inbox and Message Feed, as shown below:

The file will be related to the Task record created as a result of receiving the inbound message:

Note: At this time, MessageMedia only supports Inbound MMS in Australia and United States.

To begin using the ‘Inbound MMS’ feature, you will need to submit a request to MessageMedia by emailing support@messagemedia.com. You must already have REST enabled on your account and will also need to provide them with your ‘Web Push URL’. Please note, there will be a monthly charge for the Inbound MMS feature. This will be invoiced by MessageMedia.

Minor Enhancements

We have also made the following minor enhancements to assist with reporting requirements.

SMS Inbox

You are now able to view the SMS Inbox for all users or a different user. There is a ‘Select User’ picklist at the top of the SMS Inbox that allows you to switch to look at the inbound messages for another user, or all users.

 

To assist you with identifying whether an inbound message still needs to be attended to, a tick will appear along with each inbound message if the Status = Completed. Therefore enabling you to quickly see if the Task Status is set to Completed, or if it is still requiring your attention. See below for some examples:

Web Hook

A number of enhancements have been added to the Web Hook feature, including:

  • Specify the MessageMedia Account you want to send the message from
  • Specify whether the message should be ‘Cloaked’

The structure of the Web Hook will now be as follows:

MercuryAPI.sendSMS(String phoneNumber, String messageBody, String selectedAccount, String cloakedNumber)

An example of sending a message via the Web Hook would look like this:

MercuryAPI.sendSMS(‘+61418165511’, ‘This is my test message’, ‘Customer Service’, null)

SMS Keyword – Field Update

As part of the new REST API enhancement, a Known Issue with the SMS Keyword ‘Field Update’ feature has been resolved. Previously when an inbound SMS was received that triggered a Field Update, all records with the matching phone number were updated. With the enhanced REST API matching, only the record that sent the outbound message will be updated.

Phone Short Field Formula

We have modified the Formula in the Phone Short Formula Fields to accommodate additional characters. Previously it was only substituting spaces. It will now substitute additional characters, such as:

+ ( ) –

The Formula Fields on the Lead and Contact Objects will be updated automatically. However, if you’ve created your own Custom Fields, we recommend you update the formula to be the same as shown below (substituting MobilePhone with the appropriate API name of the Phone Field this Phone Short Field relates to).

SUBSTITUTE( SUBSTITUTE( SUBSTITUTE( SUBSTITUTE( SUBSTITUTE( MobilePhone, '+', ''), ')', ''), '(', ''), '-', ''), ' ', '')

How do I upgrade?

Version 1.12 will be rolled on based on the following release schedule:

5th January – Available to manually upgrade from the AppExchange
13th January – Automatic Upgrade to all Sandbox Orgs
20th January – Automatic Upgrade to all Production Orgs

To manually upgrade to the new version of Mercury SMS in your organisation, please follow the steps below.

  1. Click aprika.com.au/me-app
  2. Click the ‘Get It Now’ button
  3. Enter your login details (if required)
  4. Click ‘Install in Production’
  5. Click ‘Confirm and Install’ (you may need to login again at this stage)
  6. Select which users you want to install for (‘Install for All Users’ is recommended)
  7. Click ‘Upgrade’
  8. Click Done
What's New Webinar - Version 1.11
Release Notes - Version 1.11

Version 1.11 Release Notification
10 February 2017

Download PDF

A new version of Mercury SMS (version 1.11) will be released on the AppExchange on Friday 10 February 2017. This notification has been issued to existing Mercury SMS users. It contains an overview of the new features available with this release, along with instructions on how to upgrade to the new version.

What’s new?

We are very excited to announce some really cool new features that will allow you to get even more value out of using Mercury SMS. You’ll find details of all the new features below.

SMS Inbox

By far, the coolest feature to come in this release is the SMS Inbox. The SMS Inbox automatically displays inbound messages as they’re received. It shows all inbound messages assigned to you as an individual user. You get visibility of the message, a link to the record it relates to (e.g. Lead, Contact, Case, etc.), as well as a link to message (Task).

You’re able to add the SMS Inbox to your Salesforce Classic Side Bar, your Lightning Experience Home Page, Salesforce1 and your Service Cloud Console.

Let’s take a quick look at the SMS Inbox:

Mercury SMS Text Message Salesforce CRM MessageMedia

The SMS Inbox works in real-time. It will automatically load any new inbound messages, there’s no need for you to click refresh to see if you’ve received any new messages.

Add to Salesforce Classic

A Custom Component is included that can be added to your Salesforce Classic Sidebar. To add this to the Home Page Sidebar, follow the instructions below:

Click Setup > Customize > Home > Home Page Layouts > Edit

In Step 1, ensure ‘SMS Inbox’ is set to TRUE

Mercury SMS Text Message Salesforce CRM MessageMedia

Click Next. In Step 2, choose where you would like the SMS Inbox to appear in the Narrow (Left) Column

Mercury SMS Text Message Salesforce CRM MessageMedia

Click Save

Note: You can also make your Custom Sidebar Components visible on all pages by following the instructions below:

Click Setup > Customize > User Interface > Set ‘Show Custom Sidebar Components on All Pages’ to TRUE > Click Save

Mercury SMS Text Message Salesforce CRM MessageMedia

This will enable you to have your SMS Inbox visible on all pages within Salesforce Classic as per the screenshots below:

Mercury SMS Text Message Salesforce CRM MessageMedia

Add to Lightning Experience

You can add the SMS Inbox to your Home Page in Lightning Experience. To do this, you need to create a custom Home Page via the Lightning App Builder, which you can do by following the instructions below.

Click Setup > Setup Home > User Interface > Lightning App Builder > New > Home Page > Click Next >

Select ‘Standard Home Page > Click Next > Enter Label (Name of Page) > Click Finish

Drag Components on to the Page as required. The ‘MercuryFeed’ Component needs to be added to the page to provide you with access to the SMS Inbox. To replicate the default Home Page with the SMS Inbox added, set it up as follows:

Mercury SMS Text Message Salesforce CRM MessageMedia

Click Save > Set this page as the default Home page > Click Next > Click Activate

Mercury SMS Text Message Salesforce CRM MessageMedia

Navigate back to the Home Page and you’ll see that you now have access to the SMS Inbox – awesome!!

Mercury SMS Text Message Salesforce CRM MessageMedia

Add to Salesforce1

If you would like to have the SMS Inbox available from your Salesforce1 mobile app, it’s a simple case of adding it to your navigation menu.

Click Setup > Administer > Mobile Administration > Salesforce1 Navigation > Ensure SMS Inbox in the selected list > Click Save

Mercury SMS Text Message Salesforce CRM MessageMedia

The SMS Inbox will then be available in the menu options on Salesforce1.

Mercury SMS Text Message Salesforce CRM MessageMedia

Add to Service Cloud Console

If you use the Console within Salesforce.com, you’ll be excited to hear that you’re able to configure the SMS Inbox to work within the Console environment.

First of all, you need to create a Console Component, which you can do by following the instructions below.

Click Setup > Customize > Console > Custom Console Components > New > Enter details as below > Click Save

Mercury SMS Text Message Salesforce CRM MessageMedia

Next, you need to add the Console Component you’ve just created to the Console.

Click Setup > Create > Apps > Edit your Console App > Add Console_SMS_Inbox to the selected items in the ‘Choose Console Components’ section > Click Save

Mercury SMS Text Message Salesforce CRM MessageMedia

Now, when you use the Console, you’ll be able to access the SMS Inbox as illustrated below. When you click the record link (e.g. Case, Lead, etc.) it will automatically load the record in a new tab within the Console.

Mercury SMS Text Message Salesforce CRM MessageMedia

User Default Account Assignment

If you have multiple MessageMedia accounts, you can now specify a default number to use every time individual Users send messages. To support this, a new field has been added to the User object called ‘Mercury SMS Default Account’. Note: this field will need adding to the Page Layout manually.

To set a default account to a User, edit the User’s record and enter the MessageMedia Account Name into the Mercury SMS Default Account field and click save.

Mercury SMS Text Message Salesforce CRM MessageMedia

When a User has set their default account and they go to send an SMS, this account will automatically be selected by default.

Mercury SMS Text Message Salesforce CRM MessageMedia

The default account will also be used for messages using the SMS Feed, SMS Templates and messages triggered via Workflow Rules.

Support for Master-Detail Child Objects

We are pleased to announce that Mercury SMS now supports child objects in Master-Detail relationships. Previously it was not possible to send messages from these Objects due to no record owner being present.

Mercury SMS now supports Master-Detail Objects down to 5 levels.

Support for Assets Object

You are now also able to send text messages from the Asset Object. The Owner for messages sent from the Asset, defaults to the Owner associated via the Account record. If that doesn’t exist, it references the Contact Owner.

Bulk SMS to Users

You will now be able to send a Bulk SMS to Users via a new Visualforce Page that has been added. It will be accessible via the ‘SMS to Users’ Tab, which can be added to the navigation menu by following the steps below.

Click Setup > Create > Apps > Edit your app > Add ‘SMS to Users’ to the Selected Tabs within the ‘Choose the Tabs’ section > Click Save.

Mercury SMS Text Message Salesforce CRM MessageMedia

You will then see the ‘SMS to Users’ Tab in your navigation menu as below.

Mercury SMS Text Message Salesforce CRM MessageMedia

The page lets you select the appropriate list view of Users. You can then select the individual Users that you want to send a message to and click the ‘Send SMS’ button to open up the Compose Message page.

Mercury SMS Text Message Salesforce CRM MessageMedia

Note: Messages sent & received to a User record are Assigned To the User and the Subject is “SMS: Sent (User)” or “SMS: Received (User)”. There will be no Related To value, therefore, unless you are a System Administrator, only the individual User will be able to view these Task records. As a System Administrator, to view User SMS messages, it is recommended that you create a report that includes all Tasks that contain “(User)” in the Subject.

Target Number Identification

Inbound messages now have the target number populated in the ‘Sent To’ field on the Task record. This will enable customers using multiple MessageMedia accounts to identify which number the inbound message was sent to.

Web Push URL

The Web Push URL has been updated so it no longer references the ‘Instance’ of your Salesforce.com Org (e.g. NA1, EU0, AP4, etc.). Some clients experienced issues receiving inbound messages when Salesforce.com transferred them to a new instance (e.g. moved them from NA1 to NA4).

The enhancement to the Web Push URL means there is no reference to the instance so ongoing, clients will not experience any disruption, should Salesforce.com migrate them to a new instance.

Note: There is no action required by customers to take advantage of this enhancement.

Minor Enhancements

We have also made the following minor enhancements to assist with reporting requirements.

  • The Mercury SMS logo has been removed from the Inbox App page to ensure more page real estate is available for the SMS Feed
  • Picklist Fields on various pages such as the Compose Message, SMS Feed and SMS Template have been sorted in alphabetical order

How do I upgrade?

Version 1.11 will be rolled on based on the following release schedule:

10th February – Available to manually upgrade from the AppExchange
17th February – Automatic Upgrade to all Sandbox Orgs
24th February – Automatic Upgrade to all Production Orgs

To manually upgrade to the new version of Mercury SMS in your organisation, please follow the steps below.

  1. Click aprika.com.au/me-app
  2. Click the ‘Get It Now’ button
  3. Enter your login details (if required)
  4. Click ‘Install in Production’
  5. Click ‘Confirm and Install’ (you may need to login again at this stage)
  6. Select which users you want to install for (‘Install for All Users’ is recommended)
  7. Click ‘Upgrade’
  8. Click Done

Feedback

Some of the new features included in this release of Mercury SMS have come from ideas submitted from existing clients. If you have an idea for enhancing Mercury SMS, you can submit it via email on mercury@aprika.com.au.

Questions?

If you have any questions regarding this release notification, please do not hesitate to contact us on support@aprika.com.au.

What's New Webinar - Version 1.10
Release Notes - Version 1.10

Version 1.10 Release Notification
23 September 2016

Download PDF

A new version of Mercury SMS (version 1.10) will be released on the AppExchange on Friday 23 September 2016. This notification has been issued to existing Mercury SMS users. It contains an overview of the new features available with this release, along with instructions on how to upgrade to the new version.

What’s new?

We are very excited to announce some really cool new features that will allow you to get even more value out of using Mercury SMS. You’ll find the details of all the new features below.

Inbound Keyword Actions – Field Update

We have introduced a fourth Keyword Action option, where you’re now able to perform a ‘Field Update’ on a particular Object. This is in addition to the existing ‘Keyword’ actions you have available in Mercury SMS, which are:

  • Create a Lead
  • Create a Case
  • Create a Campaign Member

For example, you may set up a Field Update Keyword Action as per the below example.

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

Using the example above, when an inbound SMS is received as below:

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

The Lead ‘Email’ field would be updated with the value ‘colin.johnson@aprika.com.au’.

The below table provides further information on the types of fields you’re able to update using this new Keyword Action.

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

Please Note:

In order for the Field Update Keyword Action to work, the Mercury SMS ‘Site Guest User’ will need View and Edit access to the field.

Other Considerations:

Validation Rules, Workflow Rules, Processes & Triggers will run as usual on the Field Updates. These may prevent the update from occurring, or trigger further actions based on the field being updated.

Invalid response values: If the response is invalid for any reason, the field will not be updated. However, the inbound message will still be linked to the relevant record.

Please note that a Lead, Case or Campaign Member Keyword Action will take priority over a Field Update Keyword Action. It is therefore not recommended to have Field Update Keyword Actions that use the same Keyword as any of the other Keyword Action options.

SMS Feed Enhancements

The ‘SMS Feed’ that lets you have a real-time chat with Leads or Contacts (launched as part of Version 1.9) has been such a huge success with clients, we’ve made it available in a range of other use cases.

Standard Object Message Feed

Out of the box, you can now add the SMS Feed to the following Standard Objects:

  • Account
  • Opportunity
  • Case

To add the SMS Feed to the relevant Object, simply edit the Page Layout and add the ‘SMS Feed’ Custom Button and click Save. You will then be able to access the SMS Feed as per the below screenshot.

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

Please Note:

The Opportunity SMS Feed will only work with Phone fields stored directly on the Opportunity. It does not support Contact Roles. Prior to sending an SMS via the SMS Feed for any of these objects, you will need to select the Phone field you want to send to.

Custom Object Message Feed

As everybody seems to love the SMS Feed (we do too!), we’ve also made it possible for you to make it available to any Custom Object you have in your own Salesforce.com org. There’s a little bit of customisation required for this to happen, but we’ve listed out the steps below for you. If you get stuck on this, we’d be more than happy to assist you if you contact our support desk on support@aprika.com.au.

Step 1 – Create a Visualforce Page

In order to access the SMS Feed from a Custom Object, you need to create a very simple Visualforce Page. Please follow the steps below:

Click Setup and in the Quick Find box, type ‘Visualforce’ and click on the ‘Visualforce Pages’ link

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

Click New and then enter the following information into the appropriate sections of the Visualforce Page.

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

Copy & Paste the following code:

 

 

Your page should look like this:

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

Click Save. Your new Visualforce Page is now ready to be added to the Page Layout.

Step 2 – Add Feed to Page Layout

You have two options to choose from here. You can embed the Visualforce Page directly on to the Page Layout (illustrated in the left hand image below). Alternatively, you can create a Custom Button, add that to the Page Layout and then access the SMS Feed in a ‘pop up’ window (illustrated in the right hand image below).

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

Embedding the Feed on the Page Layout

You will need to edit the Page Layout. Click Setup > Create > Objects > Select Object > Scroll to Page Layouts > Click Edit

  • Select ‘Visualforce Pages’ – you will see the Visualforce Page you created in the previous step
  • Add a ‘Section’ to the Page Layout called ‘SMS Feed’ and make it 1 Column wide
  • Drag the Visualforce Page into this new Section
  • Click the Wrench Settings Icon for the Visualforce Page and make Height (in pixels) 600 and click OK
  • Click Save

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

Creating a Custom Button

You will need to create the Custom Button before being able to add it to the Page Layout. Follow the steps below to create the Custom Button.

  • Click Setup > Create > Objects > Select Object > Scroll to Buttons, Links, and Actions
  • Click New Button or Link
  • Configure the Settings as per the image below

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

  • Click Save
  • Click on the Button Name
  • Click the ‘Window Open Properties’ Button
  • Configure the Settings as per the image below

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

Your Custom Button is now ready to be added to the Page Layout. To do this, follow the instructions below.

  • Click Setup > Create > Objects > Select Object > Scroll to Page Layouts > Click Edit
  • Select Buttons – you will see the SMS Feed button you created in the previous step
  • Drag the SMS Feed button to the Custom Buttons section
  • Click Save

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

Please Note:
When using the SMS Feed with Custom Objects, you will first need to select which Phone field you want to send to in the Advanced Settings section of the Feed. Once you’ve made this selection, you can switch to the Basic Settings section.

Salesforce1 Message Feed

To allow you to use Mercury SMS whilst you’re on the move, you will now be able to access the SMS Feed via the Salesforce1 Mobile App.

You can access the SMS Feed by clicking on the icon at the bottom of the screen as per the screenshots below.

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

To add the SMS Feed icon to the Actions bar, you will need to edit the Page Layout of the relevant Object in Salesforce.com. You will need to add the ‘SMS Feed’ Action to the Salesforce1 and Lightning Experience Actions section.

Mercury SMS Salesforce CRM System Text Message Messaging Outbound Inbound Chat Keyword

Minor Enhancements
We have also made the following minor enhancements to assist with reporting requirements.

  • When an Inbound SMS is received and is Thread Matched to an outbound SMS, the ‘Number of Replies’ field on the outbound message is populated. This will enable you to analyse how many of your outbound messages are being responded to
  • The ‘Sent To’ field on the Task Object is populated for outbound messages so you’re able to identify which phone number the message was sent to

How do I upgrade?
To upgrade to the new version of Mercury SMS in your organisation, please follow the steps below.

  1. Click aprika.com.au/me-app
  2. Click the ‘Get It Now’ button
  3. Enter your login details (if required)
  4. Click ‘Install in Production’
  5. Click ‘Confirm and Install’ (you may need to login again at this stage)
  6. Select which users you want to install for (‘Install for All Users’ is recommended)
  7. Click ‘Upgrade’
  8. Click Done

Feedback
Some of the new features included in this release of Mercury SMS have come from ideas submitted from existing clients. If you have an idea for enhancing Mercury SMS, you can submit it via email on mercury@aprika.com.au.

Questions?
If you have any questions regarding this release notification, please do not hesitate to contact us on support@aprika.com.au.

What's New Webinar - Version 1.9
Release Notes - Version 1.9

Version 1.9 Release Notification – 10 June 2016

View AS PDF

A new version of Mercury SMS (version 1.9) will be released on the AppExchange on Friday 10 June 2016. This notification has been issued to existing Mercury SMS users. It contains an overview of the new features available with this release, along with instructions on how to upgrade to the new version.

What’s new?

We are very excited to announce some really cool new features that will allow you to get even more value out of using Mercury SMS. You’ll find the details of all the new features below.

Inbound Keyword Actions

You can now configure Mercury SMS to carry out specific actions when an inbound message is received containing a particular phrase, or ‘Keyword’. There are three types of action that can be invoked when a message is received containing the Keyword, these are:

Create New Lead
The person sending the inbound message will be added into Salesforce.com as a new Lead. The Lead Assignment is managed using active Assignment Rules. If there are active rules, but no match is found, the Default Leader Owner is assigned. If no rules exist, the Mercury Site Guest User will be assigned as the Lead Owner.

Add Campaign Member
If the person sending the inbound message is identified as a Lead or Contact, they will be added as a Campaign Member. If Duplicate records are found, they will all be added to the Campaign. If no existing Lead or Contact is found, a new Lead will be created and added to the Campaign.

Create New Case
A new Case will be created. If the inbound message is identified as relating to an existing Contact, the Case will be related to the Contact and their Account. The Case Assignment is managed using active Assignment Rules. If there are active rules, but no match is found, the Default Case Owner is assigned. If no rules exist, the Mercury Site Guest User will be assigned as the Case Owner.

A new Custom Object called ‘SMS Keywords’ has been included in the package. You can configure your own Keyword, specifying which action should be carried out. The table below outlines the fields included in the SMS Keywords Object. There are three Record Types, matching each of the Action types.

Screen Shot 2016-06-10 at 11.29.37 AM

The following fields will be populated based on the mobile number and message.

Mercury SMS Release Notes Version 1.9

Please note: The Keyword must not contain spaces and it must be the first word in the message string.

Thread Matching

Previously, when an inbound message was received, Mercury SMS would create a Task relating to each ‘matching’ record. Therefore, if there was 1 x Lead, 2 x Contacts and 1 x Cases with a matching phone number, a total of 4 Tasks would be created.

A new feature has been introduced where an inbound message is matched to an outbound message via a ‘Thread Id’. This ensures the Task is associated to only the record that the outbound message relates to.

For example, if there was 1 x Lead and 2 x Contacts all with the same mobile number and a User sends an SMS Message to the Lead, the outbound message will be created as a Task, related to the Lead. When the person responds, the inbound message will be matched using the outbound thread ID. It will therefore be related to the same Lead record as the original outbound message.

To support this feature, a new field has been added to the Task Object called ‘Thread Id’. You may wish to add this to the Task Page Layout for reference, but is not essential.

Outbound Cloaking

Mercury SMS now provides you with the ability to ‘Cloak’ an outbound message. This means rather than the message being received as though your MessageMedia number has sent it, it will appear to have come from your own mobile number.

The cloaking functionality can be used in the following ways:

Complete User Override
A new field has been added to the User Object called ‘Cloak SMS Messages’. When this field is set to TRUE, all outbound messages sent by this User will be cloaked to come from their mobile number specified on their User record.

Manual Override
At the time of sending a message manually, the User can specify whether they want to cloak the message. They can choose to cloak using their own mobile as the ‘Sender’ or the mobile number of the ‘Owner’.

Set on Template
When creating Templates, you can specify whether they should be cloaked as the ‘Sender’ or the ‘Owner’. This cloaking setting will only apply when a template is being sent via a Workflow Rule. Using a template manually will require the settings to be specified at the time of sending the message.

Please note, when using the cloaking feature please be aware that the response will be sent to the cloaked number and will not be added to Salesforce.com. When cloaking to a List View selection of records, you will only be able to cloak as the ‘Sender’.

To use the Cloaking feature, you will need to Enable Cloaking on the Setup & Configuration Page within the ‘Configuration’ section. You will also need to request the feature to be enabled directly with MessageMedia.

Mercury SMS Release Notes Version 1.9

‘Message Feed’

The ‘Message Feed’ provides you with a chat-like experience, whereby you can quickly send outbound messages to a Lead or Contact and the inbound replies will appear in the ‘Feed’ in real-time.

The Message Feed works with the Lead and Contact Objects. It can be added to the respective page layout in Salesforce Classic or Lightning Experience.

Salesforce Classic

You have two options to choose from in how you access the Message Feed within Salesforce Classic:

  • Embedded in the Page Layout
  • Separate Window accessed via Custom Button

To have the Message Feed embedded on the Lead or Contact Page Layout, you will need to add the Visualforce Page ‘mercuryleadfeed’ or ‘mercurycontactfeed’ to the Page Layout. Once the Visualforce Page to the page layout, whilst in edit mode, click the ‘Properties’ wrench on the Visualforce Page Component and set the Height value to 600 pixels.

Mercury SMS Release Notes Version 1.9

Mercury SMS Release Notes Version 1.9

Once you have done this, you’ll see the Message Feed as per the below example.

Mercury SMS Release Notes Version 1.9

To use the Message Feed in a separate ‘pop out’ window, you need to add the ‘SMS Feed’ Custom Button to the Page Layout on the Lead and Contact pages. Once this is done, you’ll be able to click the button and it will open the Message Feed in a separate window for you to use as required.

Mercury SMS Release Notes Version 1.9

Lightning Experience

You can add the Message Feed to the Lead or Contact Page Layout for use in Lightning Experience. This requires the use of the Lightning App Builder. Below is an example page layout for the Lead Object using the Lightning App Builder.

Mercury SMS Release Notes Version 1.9

This can be configured using the Lightning App Builder, below is an example of how you may want to configure your page layout.

Mercury SMS Release Notes Version 1.9

Cirrus Insight Inbox App

We are extremely excited to announce that customers who also use Cirrus Insight, the Gmail / Outlook365 application will now be able to assess the Mercury SMS Feed feature, directly from your inbox! The Inbox App uses the same ‘Message Feed’ component as the Lightning Experience Message Feed.

Mercury SMS Release Notes Version 1.9

Installing the Inbox App

To install the Mercury SMS Inbox App, please visit www.cirrusinsight.com/inbox-apps. From here, you’ll be able to click on the Mercury SMS app and you’ll then be take to the Inbox Apps Gallery, where you’ll see a screen similar to the example below.

Mercury SMS Release Notes Version 1.9

All you need to now is click the ‘Add to Cirrus Insight’ button. You’ll then receive confirmation that the app will now be available, as per the screenshot below.

Mercury SMS Release Notes Version 1.9

You’ll then get confirmation that it has been installed.

Mercury SMS Release Notes Version 1.9

You can then return to Gmail or Outlook and you will see the Mercury SMS app available within Cirrus Insight. Please note, you may need to refresh Cirrus Insight first. To do this, simply click on the Settings Icon, click Account Info, click Refresh Cirrus Insight.

Sending SMS to Opportunity

In the last release of Mercury SMS we introduced the ability to send SMS messages to the Contact Roles associated to an Opportunity.

We have extended the functionality around the Opportunity even further. You now have the ability to send outbound messages directly to phone numbers contained on the Opportunity Object. You can send these manually or automatically via Workflow Rules & Process Builders using the Task option.

Sending SMS to Campaign Members

Previously, when sending to Campaign Members you were only able to perform a Bulk SMS from the Campaign record, choosing to send to all members, or those matching a specific Campaign Member Status value.

You are now also able to send an SMS to an individual Campaign Member. This can be done manually by clicking the ‘Send SMS’ button on the Campaign Member record. You can also send SMS Templates to the Campaign Member via a Workflow Rule or Process Builder by updating the ‘SMS Code’ field on the Campaign Member record.

Please note, you will want to add the following components to the Campaign Member Page Layout to support this functionality.

Button: Send SMS

Permission Set

A Permission Set has been included in the package that provides full access to Mercury SMS. The Permission Set is called ‘Mercury SMS Full’ and can be used to quickly provide new users with access to all components within the Mercury SMS Package.

How do I upgrade?

To upgrade to the new version of Mercury SMS in your organisation, please follow the steps below.

  1. Click aprika.com.au/me-app
  2. Click the ‘Get It Now’ button
  3. Enter your login details (if required)
  4. Click ‘Install in Production’
  5. Click ‘Confirm and Install’ (you may need to login again at this stage)
  6. Select which users you want to install for (‘Install for All Users’ is recommended)
  7. Click ‘Upgrade’
  8. Click Next (on Step 1. Approve Package API Access)
  9. Select who you want to grant access to (on Step 2. Choose security level)
  10. Click Next
  11. Click Install

Feedback

Some of the new features included in this release of Mercury SMS have come from ideas submitted from existing clients. If you have an idea for enhancing Mercury SMS, you can submit it via email on mercury@aprika.com.au.

Questions?

If you have any questions regarding this release notification, please do not hesitate to contact us on support@aprika.com.au.

Release Notes - Version 1.8

Mercury SMS Version 1.8

Release Notification 12 November 2015

A new version of Mercury SMS (version 1.8) will be released on the AppExchange on Thursday 12 November 2015. This notification has been issued to existing Mercury SMS users. It contains an overview of the new features available with this release, along with instructions on how to upgrade to the new version.

What’s new?

We are very excited to announce some really cool new features that will allow you to get even more value out of using Mercury SMS. You’ll find the details of all the new features below.

Send from Multiple MessageMedia Numbers

You’re now able to authenticate Mercury SMS with multiple MessageMedia accounts. Previously, you were only able to associate one MessageMedia account with Mercury SMS. This enhancement means you will be able to send from any of your MessageMedia SMS Numbers.

You still authenticate your ‘Default Account’ on the Setup & Configuration page as normal. You will now also have access to the ‘Account Manager’ page.

Mercury SMS Two Way Text Message Messaging Salesforce.com CRM MessageMedia AppExchange

You can also assign a meaningful ‘Account Name’ such as the physical number (e.g. 0400 123 456) or a descriptive name (e.g. Customer Service).

Your ‘Default Account’ specified on the Setup & Configuration page, along with any additional Accounts stored in your Account Manager page will be displayed and available when sending Outbound SMS messages.

Mercury SMS Two Way Text Message Messaging Salesforce.com CRM MessageMedia AppExchange

Send from any Object (Standard or Custom)

You will now be able to send an SMS from any Object within Salesforce.com, including Custom Objects. In order to be able to send from any Object, you will need to create a Custom Button and add it to the Object. Instructions for creating these Custom Buttons can be found later in this document.

Note: When sending to an Opportunity, the message is actually sent to the selected Contact Role record(s). When sending to a Campaign, the message is actually sent to the selected Campaign Member(s).

Send to any Phone Number Field

When sending Outbound SMS messages, you will now be able to send to any Phone field on the Object that you are sending from. When sending a message manually, you will have the ability to select which Phone field you want to send the message to, as per the illustration below.

Mercury SMS Two Way Text Message Messaging Salesforce.com CRM MessageMedia AppExchange

Note: When creating SMS Templates, you also have the ability to set the Phone number to send to. This Phone number is used when sending an SMS Template via a Workflow Rule.

Send to Contact Roles

You will now be able to send an SMS message to Contact Roles associated to an Opportunity. When you click on the ‘Send SMS’ button on the Opportunity record, it will display a list of any associated Contact Roles and you will be able to select the people you want to send the SMS to.

Mercury SMS Two Way Text Message Messaging Salesforce.com CRM MessageMedia AppExchange

The “SMS: Sent” Task(s) will be related to the Opportunity and visible in the Activity History.

Send Bulk Message from List Views

In addition to being able to send a Bulk SMS to Campaign Members, Mercury SMS now also enables you to send a Bulk SMS to a group of records selected via a List View.

To send a Bulk SMS via a List View, select the records and click the ‘Send SMS’ button, as per the below screenshot.

Mercury SMS Two Way Text Message Messaging Salesforce.com CRM MessageMedia AppExchange

You’ll then be able to type out the message, or select an existing template and send as normal. Note, it shows you how many records the SMS will be sent to.

Mercury SMS Two Way Text Message Messaging Salesforce.com CRM MessageMedia AppExchange

Note: The Bulk SMS via List View feature is available for all Standard and Custom Objects, excluding Opportunities and Campaigns. Custom buttons will need to be created and added to list views to support this feature. Instructions on this can be found later in this document.

Inbound Activity Status Setting

You can now specify the Status of the Task that is created when an Inbound SMS is received. Previously, it automatically defaulted to Completed, so it appeared in the Activity History. At the request of clients, you can now set the Status on the Setup & Configuration page.

Mercury SMS Two Way Text Message Messaging Salesforce.com CRM MessageMedia AppExchange

 

Inbound Phone Matching

By default, Inbound SMS messages are matched up against the Mobile field on the Lead and Contact Objects. You can now configure Custom Fields on any object to extend this inbound matching process. To do this, you need to create a Custom Field on the Object you want to match on. An example of the Custom Field is below:

Scenario: I want to start Inbound Phone Matching for the Phone field on the Lead Object called ‘Spouse Mobile Phone’.

Solution: Create a Custom Field on the Lead Object

Field Type: Formula (Text)
Field Label: Spouse Mobile Phone Short
Field Name: Spouse_Mobile_Phone_Short__c
Formula: SUBSTITUTE([FIELD NAME], ‘ ‘, ”)

Example Formula: SUBSTITUTE(Spouse_Mobile_Phone__c, ‘ ‘, ”)

Note: The API Name for the Formula Field must end in Phone_Short__c for it to be included in the Inbound Phone Matching process.

SMS Template Enhancements

A number of new features have been added to the SMS Template Object. You can now take advantage of the following functionality when creating SMS templates:

  • Create Templates for any Object (Standard or Custom)
  • Reference Parent Object Fields
  • Specify the default Phone field to send to
  • Specify the default MessageMedia Account to send from

Mercury SMS Two Way Text Message Messaging Salesforce.com CRM MessageMedia AppExchange

Workflow SMS Enhancements

Mercury SMS now enables you to send SMS messages to any Object via a Workflow Rule.

To send an SMS Message using an SMS Template, your Workflow Rule needs to create a new Task assigned to the Object you wish to send the SMS from, with the Comments field populated with the following:

{“template”:”[SMS TEMPLATE ID]”}

Example: {“template”:”a0290000007vbKVAAY”}

This will send the SMS via Mercury and you will then see a subsequent “SMS: Sent” Task record created, confirming the message has been sent.

Note: Clients using the legacy Workflow Rule feature can continue to do so as this feature is still supported.

Send Outbound SMS Messages to Users

You are now able to send SMS messages to User records. This can be done directly on the User record by clicking the ‘Send SMS’ link in the Custom Links section.

Alternatively, if you want to send an SMS to a User regarding a particular record (e.g. the Owner of a Case), you can do so by ensuring their Phone Number is populated in a Phone field on the record in question.

For Example, “I want to send an SMS to the Owner of a Case”. In order to do this, I need to ensure their Phone resides in a Phone field on the Case record. So, I create a Custom Field called ‘Owner Phone’ and I create a Workflow Rule that ensures the value of this field is updated every time the record is modified to ensure it matches the Phone stored on the User record.

I now have a Phone field on the Case that holds the User’s phone number and I will be able to send an SMS to that number.

Creating Custom Buttons

If you want to send SMS messages from an Object that does not come with a pre-configured ‘Send SMS’ button, you will need to create a Custom Button. Depending on how you want to send the SMS (e.g. manually to an individual record via the Detail Page Layout, or to a bulk list via a List View), you will need to create a different Custom Button. Instructions for both options are below.

Detail Page Layout

Mercury SMS Two Way Text Message Messaging Salesforce.com CRM MessageMedia AppExchange

Note: The code you need to insert in the Button Box is below for easy access:

/apex/mercury__composemessage?id={![objectname].Id}

Note: you will need to replace [objectname] with the name of the Object you want to use this button on.

Once the button is created, you will need to add it to the Detail Page Layout.

  • Edit the Page Layout
  • Select Buttons
  • Drag the ‘Send SMS’ button to the Custom Buttons section
  • Click Save

Mercury SMS Two Way Text Message Messaging Salesforce.com CRM MessageMedia AppExchange

List View

Mercury SMS Two Way Text Message Messaging Salesforce.com CRM MessageMedia AppExchange

if({!GETRECORDIDS($ObjectType.Name)}.length > 0){
console.log({!GETRECORDIDS($ObjectType.Name)});
var popup = window.open(“{!URLFOR(‘/apex/mercury__composemessage’)}?ids=”+{!GETRECORDIDS($ObjectType.Name)}, “sms”, “width=800, height=300”);
}
else{
alert(‘Please Select Some Records.’);
}

Note: You don’t need to make any changes to this text.

Once the button is created, you will need to add it to the List View.

  • Navigate to the Search Layouts section for the Object
  • Click Edit for the ‘List View’ option
  • Ensure ‘Send SMS’ is in the ‘Selected Buttons list
  • Click Save

How do I upgrade?

To upgrade to the new version of Mercury SMS in your organisation, please follow the steps below.

  1. Click https://login.salesforce.com/packaging/installPackage.apexp?p0=04t900000005E5Y
  2. Enter your login details (if required)
  3. Click Continue
  4. Click Next (on Step 1. Approve Package API Access)
  5. Select who you want to grant access to (on Step 2. Choose security level)
  6. Click Next
  7. Click Install

Feedback

Some of the new features included in this release of Mercury SMS have come from ideas submitted from existing clients. If you have an idea for enhancing Mercury SMS, you can submit it via email on mercury@aprika.com.au.

Questions?

If you have any questions regarding this release notification, please do not hesitate to contact us on support@aprika.com.au.

Release Notes - Version 1.7

Mercury SMS Version 1.7

Release Notification 5 December 2014

A new version of Mercury SMS (version 1.7) will be released on the AppExchange on Monday 8 December 2014. This notification has been issued to existing Mercury SMS users. It contains an overview of the new features available with this release, along with instructions on how to upgrade to the new version.

What’s new?

Inbound SMS Notification

We have adjusted the method by which we issue notifications to Users when an inbound SMS message is received. We previously issued a standard Task notification email. This has been changed to send a standalone email to notify the User. This addresses the known issue published on the 5th November 2014 to overcome client settings relating to control of automated Task notification settings released in the Winter ’15 version of Salesforce.com.

Inbound SMS Notification Assignment

To provide flexibility to clients so the most appropriate User is notified when an inbound SMS message is received, you can now select which User should be notified out of the following options:

  • Owner – The User who is the Lead / Contact / Person Account Owner will be notified of the inbound SMS
  • Last Modified By – The User who last modified the Lead / Contact / Person Account will be notified of the inbound SMS
  • Last Message Sent – The User who sent the most recent outbound SMS to the Lead / Contact / Person Account will be notified of the inbound SMS

You can specify who should receive these notifications for your business by selecting the required value in the ‘Lead Task Assignment’ and ‘Contact/Person Account Task Assignment’ picklists and clicking ‘Save’ in the Configuration section of the Mercury SMS ‘Setup & Configuration’ Tab as per the screenshot below.

Mercury SMS MessageMedia Two-Way Text Messaging Message Solution Salesforce.com AppExchange

Message Character Length

The 280 character length restriction for an outbound SMS message has now been removed to enable clients to send longer messages where required. The previous counter that counted down from 280 has now been replaced with a counter that counts the length of the message string.

Mercury SMS MessageMedia Salesforce.com AppExchange Two-way Text Messaging Message Solution Outbound Send Workflow Rules

Note: Whilst there is no hard limit on the length of the message string, it is recommended you keep messages short to avoid using too many SMS credits per message.

How do I upgrade?

To upgrade to the new version of Mercury SMS in your organisation, please follow the steps below.

  1. Click https://login.salesforce.com/packaging/installPackage.apexp?p0=04t90000000If3f
  2. Enter your login details (if required)
  3. Click Continue
  4. Click Next (on Step 1. Approve Package API Access)
  5. Select who you want to grant access to (on Step 2. Choose security level)
  6. Click Next
  7. Click Install

Feedback

Some of the new features included in this release of Mercury SMS have come from ideas submitted from existing clients. If you have an idea for enhancing Mercury SMS, you can submit it via email on mercury@aprika.com.au.

Questions?

If you have any questions regarding this release notification, please do not hesitate to contact us on support@aprika.com.au.

No helpful answer? Here are some options

Training Videos

We know plenty of people prefer to watch rather than read…so we’ve put together a number of training videos.

To Videos

Contact Support

Can’t find the answer you are looking for then please feel free to contact support. Or have a look at the helpful links below.

Contact support

Start typing and press Enter to search