Feel free to browse our FAQs section or download our user guide below!
If you have a question that isn’t answered here, please let us know and we’ll be sure to add it to the list!
Mercury SMS is licensed on a ‘per-organisation’ basis. This means you pay one set fee regardless of how many Salesforce.com users you have. Mercury SMS costs AU$100 per month. Payment is via Credit Card on a monthly subscription basis.
Mercury SMS messages are distributed via MessageMedia. A free trial account will be provided for evaluation purposes during the 14 day free trial of Mercury SMS. This can be upgraded to a live account once subscription to Mercury SMS has been completed. MessageMedia offers a variety of tariffs to suit each individual client’s volume.
Mercury SMS can be installed in the following Salesforce Editions:
If you are running a lower edition than those listed you would need to upgrade before being able to install and use Mercury SMS.
Yes. Aprika offers discounted rates for high licence volume and not for profit organisations across all of our products. If you fall into either of these categories, please contact us to discuss further.
If you would like to unsubscribe from Mercury SMS, we require a written request with 1 months notice as per our terms and conditions.
The best way to get help with Mercury SMS is by sending an email firstname.lastname@example.org.
Mercury SMS is licensed on a per company basis which means that there is no need for additional user licenses. If you are finding that some users can not access the application, you should check the profile and security settings for your organisation to ensure that the users have access to the package components.
Yes you can set a senderID as a name instead of a number, this is limited to 11 characters in length.
In doing so, as there is no number associated with the sending of messages, messaging becomes 1-way (i.e. outbound to the handset, with no functionality to receive replies).
There are costs involved in setting this up, see below (ex GST).
Setup & Activation: $100 (once-off)
Monthly Licensing Fee: $50/month
An alternative solution would be to use a dedicated number, meaning that all messaging coming from the NSR account would come from the same mobile number each time – this allows for the ability to not have the changing rotary of numbers when sending messages, but also keeps the functionality of a 2-way service allowing for replies to come back.
Costs to set this up are the same as the above.
Mercury SMS uses a text messaging provider called MessageMedia to deliver sms messages. Because of this requirement, it is not possible for us to provide a public test drive environment for this product, however we are happy to arrange a live demonstration for you upon request.
Inbound SMS activities will be assigned to a user based on the settings specified on the Mercury SMS Setup Page.
The choices for assignment are to assign the SMS activity to:
– The last user to send an SMS to the record
– The last user to modify the record, or
– The record owner.
These options need to be specified globally for Leads, Contacts and Person Accounts, and All Other Objects. If inbound SMS are not being assigned to the most relevant person, you should review these settings.
In addition, where an inbound SMS cannot be matched to a record in Salesforce.com, Mercury SMS will assign the record and send a notification email to the user specified as the “Orphan Message Owner”. The orphan message owner can also be updated on the Mercury SMS Setup page.
Mercury SMS relates inbound SMS to the appropriate record based on a Thread ID, captured in the messaging data, or by locating a matching mobile phone number in a “Phone Mapping Field”.
In some cases a match cannot be found, either because;
– The inbound SMS came from an unrecorded number,
– An inbound phone mapping field had not been created, or
– Mercury SMS has not been given access to view the relevant records or fields due to profile and sharing settings.
Where Mercury SMS cannot locate the correct record to match the SMS activity to, the activity will be created and assigned to the orphan message owner to review and update as needed.
If all inbound SMS are being assigned to the orphan message owner, you should review the user guide and ensure that the Mercury SMS Site Guest user has the correct access to the records and fields, and that the inbound phone mapping fields have been created as required.
Mercury SMS requires read access to Contacts in order to relate inbound SMS messages to Contact records.
In the case that your sharing settings for Contacts are “Controlled by Parent” and the correct access is given to the Accounst object, then Mercury SMS will be able to access the Contact records only if they are related to an Account.
If you have a Contact record that is not related to an Account it will be treated as a private Contact unless the Contact sharing rules are explicit for Contacts and not inherited from the parent Account.
If you require that Contacts are not linked to Accounts and that the Contact access is controlled by the parent record, you will need to create a sharing rule to open up access to these Contacts to the Mercury SMS Site Guest User, otherwise Mercury SMS will not be able to relate inbound SMS to the Contact record.
Mercury SMS comes with a permission set called “Mercury SMS Full” which provides full access to all of the Mercury SMS components. This permission set allows you to quickly and easily give your users access to use Mercury SMS.
Note: When installing Mercury SMS you have the option to grant access to all users, if you choose this option you will not need to assign the permission set.
In the case that you want to give users restricted access to Mercury SMS, such as to not allow them to create SMS Templates, you should not apply the Mercury SMS Full permission set, but instead make a refined version of the permission and apply to the users as required.
Mercury SMS offers the ability to create templates using merge fields on the master object (the object that the SMS will be sent to) as well as fields on objects that are related as parent objects via lookup or master-detail relationships.
For example if you are building an SMS template for Contacts, you can also merge in details from the related Account object, including the Account name and address, by selecting to merge fields from the related object in the picklist before the merge field picklist.
If you are finding that your merge filed is returning the ID, instead of the Name, this means that you have not selected the correct merge field.
When merging in fields from related objects, you need to ensure that you first select the correct object before you select the field. If you select the Account field from the Contact object merge fields, this will be the Account ID.
Instead, you should first select to merge from the related object in the picklist in front of the merge fields, and then you will have access to select the correct Account Name merge field.
In order for inbound SMS to get created in Salesforce.com, your Web Push URL must be correctly applied on your MessageMedia account.
If your inbound SMS are not being created in Salesforce, you should check that you have correctly set up Mercury SMS as per the user guide, and that your Web Push URL has been applied to your MessageMedia account. Note that if you are using a MessageMedia trial account, you will need to notify MessageMedia so they can update the Web Push URL once you have submitted it. If you are using a live MessageMedia account then you can directly update the Web Push URL.
Please also note that if you tested Mercury SMS in your sandbox environment and then installed into production, the Web Push URL will be different and will need to be updated in your MessageMedia account.
Often, the issue is not that inbound SMS is not being created in Salesforce.com, but instead that the activities are not being assigned to the correct record due to sharing settings. In this case you should review the setup instructions in the user guide, with regards to giving access to the Mercury SMS Site Guest User and Sharing Settings.
Mercury SMS will relate the inbound SMS activity to a record based on locating a matching “Thread ID” or “Phone Mapping Field”. If this occurs the inbound SMS will be available in the activity related lists of the record.
Whether the inbound SMS activity is recorded in the “Open Activities” or “Activity History” related list will depend on the status you have chosen to apply to inbound SMS on the Mercury SMS Setup page. If you have chosen to assign the inbound SMS an open status, the activity will be shown in the “Open Activities” related list. If you have chosen to assign the inbound SMS a closed status, the inbound SMS will appear in the “Activity History” related list.
The Message Feed feature for Leads and Contacts will also allow you to view inbound and outbound SMS in a conversation style view.
If the inbound SMS could not be assigned to a related record it will be assigned as a task to the orphan message owner, who will also receive an email notification linking to the activity.
Inbox Apps is a feature of Cirrus Insight which allows other Salesforce.com apps to be integrated into your email inbox. We have partnered with Cirrus Insight to allow customers of both apps the ability to use the Mercury SMS Message Feed feature to send and receive SMS messages to Salesforce records from within your email inbox!
Find out more about this feature in our user guide.
No helpful answer? Here are some options