1. Campaign – Lookup of Campaign object
2. Case – Lookup of Case object
3. Contact – Lookup of Contact object
4. Conversation – Lookup to conversation
5. Converse App – Lookup to Converse app if message is triggered from converse app
6. Converse App Action
7. Converse App Task
8. Country – If the country settings is selected as ‘All’ and country code is added to mobile number, shows the country name
9. CreatedOn – Created date
10. Delivery Error Message
11. Delivery Status – Delivery report of outgoing message
12. Direction – Shows direction of the messages IN for incoming and OUT for outgoing
13. Disable SMS On Trigger
14. External Field – Unique ID of the record
15. Lead – Lookup of Lead object
16. Message Credits – Shows how many SMS credits were consumed for that SMS
17. Message Type – Shows if it is SMS /MMS
18. MMS Subject – If it is MMS, show the subject of MMS.
19. Mobile Number – Shows the mobile number used for sending the outgoing message
20. ObjectType – Shows the object name from where the outgoing text was triggered
21. Opportunity – Lookup of Opportunity object
22. Previous Message – This field populated the lookup of last outgoing message in case of an incoming message
23. SenderId – Shows the senderID used for sending/receiving message
24. Sent Status
25. SMS Template – Lookup of the SMS template used
26. SMSText – Shows the message body of SMS
27. Source – From where the message was triggered
28. Status – Shows the overall status of message
29. Status Message
30. Text Unicode – Shows if the text was considered unicode
31. Unformatted Phone Number – Unformats the mobile number
32. User

The following Conversation Fields are available in the managed package:

1. Account
2. Campaign
3. Case
4. Contact
5. Converse App
6. Converse App Action
7. Inbound Number
8. isUnread
9. Last Incoming Time
10. Last Message Direction
11. Last Message Time
12. Last Outgoing Time
13. Lead
14. Mobile Number
15. Mode
16. New Count
17. Object
18. Opportunity
19. Purpose
20. Sender
21. State

Sent Status
The SentStatus of an SMS gives you the health of the SMS creation process from the salesforce org to the SMS-Magic portal. If it displays “Submitted” in the initial stage, it means that the SMS request has been created successfully.

Delivery Status
The deliveryStatus of an SMS is the real-time delivery report that we receive from the SMS providers. The moment we receive them, we push them back to your SF org.

In short, when we send an SMS from the SF org, a record is created in SMS History tab with the Sent Status as “Submitted”. This means that the SMS has been sent from Salesforce to the SMS Magic portal for further processing. When we receive the delivery report from the provider, we push it back to your org and the Sent Status is updated to “Success” and the Delivery Status is updated with the one shared by the SMS provider.

Additionally, the Status field shows the overall status of the outgoing messages.

Please note that for automated messages, the user who would be fulfilling the criteria (mentioned in the automation flow) needs to have the SMS-Magic license. In short, when the conditions are satisfied by the respective user, as per Salesforce functionality, that user will become the owner of History record and our logic checks if that user has SMS- Magic license.

If someone revokes OAuth access from Salesforce or if your access rights get expired, you may face the following issues:

1. Your Salesforce Org will no longer receive inbound SMS
2. You will no longer receive delivery reports for outbound SMS

In order to continue receiving benefits from SMS-Magic, you need to reset OAuth. Resetting OAuth can be done by following a few simple steps, as follows:

1. Login to SMS-Magic Portal through Salesforce
2. Switch to SMS Magic Converse, go to the Converse Settings page, and click Reset.

3. Ensure that the green checkmark appears on the following page indicating that the access is granted.

1. Under Converse Settings, click Message object configuration.
2. Select the Object.
3. Select the Name field.
4. Add or Edit the Mobile Phone.
5. Refer to the SMS-Magic Converse Salesforce Admin Guide for more details.

Refer to the section on SMS-Magic Converse Permission Details in the SMS-Magic Converse Guide for Salesforce Admin for more details on assigning permissions in SMS-Magic Converse.

On the other hand, Delivery Status gives the real time delivery of the outgoing message. Once the record is created at SMS Magic servers, it pushed to provider’s end for further processing. As soon as we receive the delivery report from the provider the SentStatus is updated to ‘Success’ and Delivery Status to the one shared by the provider.

1. Sending messages to invaid number like Landline
2. Mobile switched off or out of network
3. Destination number has opted out
4. The Message subscription on the destination number has expired (e.g.- Customer having 1:1 communication and suddenly a message is not delivered).
5. Spam Detected- Too many messages sent using long code, like bulk or campaign (We suggest either Shortcode or Toll free number).
6. Number has opted out from receiving messages from you.
7. Number is overwritten
8. The end-user’s mobile plan does not support SMS
9. Number is no longer valid
10. Prepaid subscription for SMS expired
11. The sender id entered is either not in the correct format, not SMS-enabled or not assigned to your account.
12. Network error- Network issues at carrier end
13. Spam detected- SMS filtered
14. Invalid SMS Content- blank SMS or SMS exceeds the characters limit of 1600 for messages

To check if Clickjack is enabled:

1. On the Setup page, search for Security.
2. Under Platform Encryption, click Sessions Settings.
3. Under clickjack protection, check whether the following two check boxes are enabled:
4. Enable clickjack protection for customer Visualforce pages with standard headers; and
5. Enable clickjack protection for customer Visualforce pages with headers disabled is enabled.

Solution:

If Clickjack protection is enabled, follow the given process to resolve the error:

1. On the Setup page, search for Visualforce.
2. On the Visualforce page, search for the visualforce page for which you want to resolve the error.
3. Click on the Edit button.
4. Modify the following attribute in the first line applyHtmlTag =”false”
5. Refer the URL shown below for more details: https://help.salesforce.com/articleView?id=000230608&type=1

If the user is a “System Administrator” – Set “Customize Application” permission for this profile from “Administrative Permissions–> Customize Application” as true. — If the user is not a “System Administrator” – Set “View Setup and Configuration” permission for this profile from “Administrative Permissions–> View Setup and Configuration” as true . “

1. Access to Page Layout for SMS-Magic Buttons: Buttons cannot be assigned to a profile. Therefore, they are added to a layout. In order to access these buttons, Customer Portal Super user Profile and Customer Portal Manager users should be able to access that particular page layout. Page layout assignment for the Customer Portal Super user Profile and Customer Portal Manager user can be defined on their profile.
2. Provide access to SMS-Magic Objects, VF pages, Triggers and FLS permissions: Salesforce Admin should provide the Customer Portal Super user Profile and Customer Portal Manager users with access to the SMS-Magic objects. Along with this, access should also be provided to the SMS-Magic Visualforce pages and triggers. This ensures that Customer Portal Super user Profile and Customer Portal Manager user has full access to SMS-Magic application.
3. Field Level Security Permissions: The Customer Portal Super user Profile and Customer Portal Manager user should also have field level security permission on individual fields in order to send and receive SMS. In addition to granting permissions to object, all fields of the object should be granted the same level of permissions.

For example: To send SMS, Customer Portal Super user Profile and Customer Portal Manager user should have create and update permission to SMS History object and all fields of SMS history object.

The table below provides further details on objects:

1. Functionality
2. Send SMS
3. View Incoming SMS
4. Create Templates

DescribeSObjectResult result = Schema.getGlobalDescribe().get(‘‘).getDescribe();
System.debug(‘Object Accessible:’+result.isAccessible());
System.debug(‘Object Createable:’+result.isCreateable());
System.debug(‘Object Updateable:’+result.isUpdateable());
System.debug(‘Object Deleteable:’+result.isDeletable());
for (Schema.Sobjectfield obj : result.fields.getMap().values()) {
Schema.DescribeFieldResult fldResult = obj.getDescribe(); System.debug(‘Field Name:’+fldResult.getLabel()+’;\tField Accessible:’+fldResult.isAccessible()+’;\tField Createable:’+fldResult.isCreateable()+’;\tField Updateable:’+fldResult.isUpdateable()); }