1

Unable to receive Text/Email notification for Incoming Messages

Issue Scenario

A user does not receive any Email/Text notification for incoming messages.


Possible Causes

The following are the possible causes for the issue:

•“Notification on incoming” flag is set to False on the Salesforce org.

•The user is not assigned to the sender ID and thus does not meet the criteria of “user assigned to sender ID” that has been defined as a notification parameter.

•Multiple users are assigned to a single Sender ID and therefore is not eligible to receive notifications based on the “user assigned to sender ID” notification parameter.

•The user is not the last sender and therefore does not meet the criteria for the “Last sender” that has been defined as a  notification parameter.

•There are more than 200,000 SMS History records (for “Last sender” notification).

•The user does not have permission to the object and its field where the incoming SMS record is stored (SMS History or Incoming SMS). Also, they do not have access to the Conversations object.

•If the “Notification on incoming” is set to False, the customer might have set up workflows/process builder for custom email alerts and the logic for that might be incorrect.

•Emails are going to the SPAM folder of customer’s email Inbox

•Customer’s IT team might have filters on employees Inbox which might be causing the issue.


Solution

Follow the given procedure to solve the issue:

1.Under Converse Settings click Sender ID & Assignment.

2.Slide the “Notification on incoming” toggle button and set it to True to enable the customer to receive emails alerts using our logic

3.Make sure that  the user is assigned to a sender ID to ensure that it receives notifications when the “user assigned to sender ID” notification value is defined.

4.Also ensure that only one user is assigned to a sender ID (for “user assigned to sender ID” notification)

5.Verify the last sender who needs to be notified.

6.If there are more than 200,000 SMS History records, then, you will need to index the mobile field.
Refer the solution document available in the URL below follow a recommended practice: https://docs.google.com/document/d/1PsBNr8PQuKD_abbRwggCZTtfGQqedAdAU74tzqlZ10k/edit?usp=sharing

7.Grant the user appropriate access to the SMS History/Incoming SMS object and Conversations object.

8.Review the custom automation rule for email alerts configured on the customers org and modify the logic accordingly.

9.Reach out to the CS team for further assistance  or contact the Dev team if you are still unable to resolve the logic.

10.Request the customer to mark these emails as Not spam.

11.Ask the customer to check with his IT team.

For the last two steps in the procedure mentioned above, check if the emails are actually triggered from Salesforce by setting up email logs. This helps to ensure whether emails were triggered at a specific time.

For more details, refer the following Salesforce Help document at –
Request an Email Log



Browser Notification not working for Incoming Messages

Issue Scenario

A user does not receive browser notifications for incoming messages.


Possible Causes

The following are the possible causes for the issue:

•The push topics are not configured correctly.

•Popup notifications are disabled for your browser.


Solution

Contact the  Dev team, if you fail to receive browser notification even after all configurations are defined appropriately.




ECD Shows no Indication of Incoming Messages

Issue Scenario

The ECD does not show any indication when the user receives incoming messages in the ECD.


Possible Causes

The following are the possible causes for the issue:

•The push topics are not configured correctly.


Solution

•Configure Push topics accurately.

•Contact the  Dev team, if you fail to receive notification in ECD even after push topics are configured appropriately.




Incoming Messages Are Not Visible in Converse Desk/ECD/Conversation View

Issue Scenario

A user is unable to view Incoming Messages in Converse Desk, ECD or Conversation View.


Possible Causes

The following are the possible causes for the issue:

•The lookup field is not populated on the incoming SMS record.

•The object field is not populated on the conversation record.

•Previous message field on SMS History was not populated.

•The SMS was received from an unknown number.

•Sharing settings has not been configured properly.


Solution

Check and implement the following changes to solve the issue:

•Verify if the user has permissions for the lookup field and assign appropriate solutions if required.

•Index the Mobile field on the SMS History record, if required.  

•Populate the object type field on the conversation record if required.

•Review all sharing settings/sharing rules on Conversations object, not allowing messages to be visible to specific people, and grant access to the affected user.




Incoming SMS Alerts are Sent to Incorrect Recipient

Issue Scenario

The incoming SMS alerts are sent to unintended recipient.


Possible Causes

The following are the possible causes for the issue:

•Data indexing issue – There are more than 200,000 records on which the query runs. Therefore the incoming SMS is assigned to the OAuth user.

•Notification settings are not configured correctly.

•The Previous message lookup did not happen.

•Incoming SMS was received from an unknown number.

•User does not have permissions for updating the Previous Lookup or the related SMS History


Solution

Do the following to resolve the issue:

•Index all mobile fields. Refer to the document in the link provided below for more details on Field Indexing.
https://docs.google.com/document/d/1PsBNr8PQuKD_abbRwggCZTtfGQqedAdAU74tzqlZ10k/edit?usp=sharing

•Configure all notifications correctly. For more details, refer the section on Configure Incoming Notifications under Sender ID and Assignment in the SMS-Magic Converse Guide for Salesforce Admin:
https://www.sms-magic.com/technical-resource-center/sms-magic-guide-for-salesforce-admin/