You can select the primary country of operation for the business. Messages will follow the compliance guidelines and Sender ID restrictions based on the country of coverage.
Under Converse Settings, you can select only a single country. If you need to send messages to multiple countries, send an email to care@screen-magic.com.
You can change the country of operation later if required.
Under Coverage , select the country from the Primary Country drop-down list.
Click Yes in the Confirm Selection pop-up window.
Click Go to Next Step.
Procure Long/Short Code
|
You need to procure incoming numbers to receive messages in your Salesforce organization.
Incoming numbers can be procured from our Portal where you can view the rates for individual countries and the available SMS packs.
Click Buy Inbound Number. The Get A Quote page appears.
Enter the details as required.
Click Get A Quote. The SMS-Magic Sales team will receive an email requesting a quote for the required quantities of Incoming number.
The Sales team reverts with a response and helps you procure the required numbers.
Contact the sales team atsales@screen-magic.com for more details on purchasing incoming numbers.
Add SMS Button to Layouts
|
After creating the SMS button, you need to add the buttons to the record layout such as Contacts, Leads, Opportunities, and so on.
To add the button to the page layout in Salesforce Lightning, you need to use the Object Manager.
To add the button to the page layout in Salesforce Classic, you need to use the Quick Find/ Search field to search for the object page and add the button.
You can add the single SMS button to the record page layout for an object such as Contacts, Leads, Opportunities, and so on. The adding of the button is done through the Page Layout option of the object.
Add the Single SMS Button to a Layout Page in Salesforce Lightning
1. From the Salesforce navigation on the top right, click Setup.
2. Select Object Manager by:
Using the Quick Find / Search field, or
Selecting Objects and Fields > Object Manager.
3. Click a record page. Record page can be Contacts, Opportunities, Leads, and so on.
4. Click Page Layouts.
5. Click Edit for the record layout.
6. Select Mobile & Lightning Actions.
7. Select the SMS button from the Mobile & Lightning Actions section.
8. Drag and drop the SMS button in the Salesforce Mobile and Lightning Experience Actions section.
Add the Bulk SMS Button to a Layout in Salesforce Lightning
1. From the Salesforce navigation on the top right, click Setup.
2. Select Object Manager by:
Using the Quick Find / Search field, or
Selecting Objects and Fields > Object Manager.
3. Click a record page. Record page can be Contacts, Opportunities, Leads, and so on.
4. Click Search Layouts.
5. Click Edit for the record List View.
6. Select the SMS button in the Available Buttons list under the Custom Buttons section.
7. Click Add to move the SMS button from the Available Buttons list to the Selected Buttons list.
8. Click Save.
Add the Single SMS Button to a Layout Page in Salesforce Classic
1. From the Salesforce navigation on the top right, click Setup.
2. Select an object by using the Quick Find/ Search field. The object can be Contacts, Opportunities, Leads, and so on.
3. Click Page Layouts.
4. Click Edit for the record layout.
5. Click Buttons.
6. Select the SMS button from the Buttons section.
7. Drag and drop the SMS button in the Salesforce Mobile and Lightning Experience Actions section.
8. Click Save.
Add the Bulk SMS Button to a Layout in Salesforce Classic
1. From the Salesforce navigation on the top right, click Setup.
2. Select an object by using the Quick Find/ Search field. The object can be Contacts, Opportunities, Leads, and so on.
3. Click Search Layouts.
4. Click Edit for the record List View.
5. Select the SMS button in the Available Buttons list under the Custom Buttons section.
6. Click Add to move the SMS button from the Available Buttons list to the Selected Buttons list.
7. Click Save.
View SMS Button on a Record Page or List
|
When you add the SMS button to the record page, the button is then available as a menu item on any record object page. The single SMS button is available on the record page of the object while the bulk SMS button is available on the record list view page.
To View the Single SMS Button in Salesforce Lightning
1. Log in to SMS-Magic Converse.
2. Select the detail page of a record object.
3. Click Submit for Approval.
4. Select the SMS button to send a message.
To View the Bulk SMS Button in Salesforce Lightning
1. Log in to SMS-Magic Converse.
2. Select the list view of a record object.
3. Click Add to Campaign.
4. Select the SMS button to send a bulk message.
To View the Single SMS Button in Salesforce Classic
1. Log in to SMS-Magic Converse.
2. Select the detail page of a record object.
3. Select the SMS button to send a message.
To View the Bulk SMS Button in Salesforce Classic
1. Log in to SMS-Magic Converse.
2. Select the list view of a record object.
3. Select the SMS button to send a bulk message.
Assign Permission To Multiple Users
|
Log in to Salesforce.
Click and then click Setup. The Setup Home page appears.
Type Permission Sets in the Quick Find search box and then click Permission Sets in the search results. The Permission Set page appears.
Click to open a SMS-Magic Converse Permission Set. The Permission page appears.
Click Manage Assignments.The Permission Set page displaying existing users appears.
Click Add Assignments.The All Users page appears.
Select the users to whom you want to assign the permission set.
Click Assign. The permissions are assigned successfully.
Create Content Type
|
Under Consent for Specific Content , click Create New. The Create New Content-Type pop-up window appears.
Enter the customer details to create a new content type.
Refer to the table below for more details on individual fields.
Click Next. The Configure section appears to help you add the Sender ID and Keyword configurations for the new content type.
Refer to the table below for more details on individual fields.
Click Validate and Next. The Opt-out Instructions section appears.
Avoid using the same keywords as those in the default Keyword configuration section.
Enter details, as required, to add an opt-out instruction to your message.
Refer to the table for more details on individual fields.
Click Save. The new message type appears on the Content-Type table.
Field
Description
Define Customer Details
Content Type Name
Type the content type name. It must follow the given guidelines:
It must be a maximum of 40 alphanumeric characters including underscores (_)
It must start with a letter.
It should not include spaces
It must not end with an underscore or contain two consecutive underscore characters.
Consent Mode
In the drop-down list select the relevant consent mode for the new content type.
Applicable Sources
Select the message source. The available options are:
Automated Conversation
Bulk Conversation
Interactive Conversation
Configure
Sender ID
In the drop-down list, select the Sender ID that will be associated with this Content-Type. Consent is created only if you receive an incoming request for this content-type using this Sender ID.
This field is available only if you select Sender ID as your consent parameter in Step 1 of the Compliance configuration. If Sender ID is not a consent parameter then consent records for content-type is created using the same Sender ID through which the incoming request is sent.
Opt-In keyword
Type the specific Opt-in Keywords that you want to associate with this content type.
Once configured this rule will be given priority over the basic settings.
Opt-In Confirmation Message
Type the message that will be sent to customers in response to the Opt-in request.
Opt-out Keyword
Type the specific Opt-out Keywords that you want to associate with this content type.
Opt-Out Confirmation Message
Type the message that will be sent to customers on receiving the Opt-out request.
Opt-Out Instructions (Optional)
Auto append opt-out Instruction in every message
Select the option if you want to add an opt-out instruction to every message that is sent out.
In an Interval
Select the number of days after which the opt-out instruction will be appended to the content-type message being sent out.
Select an Interval
In the drop-down list select the number of days after which you want to append the opt-out instruction with the content-type message.
Do not Auto-append opt-out instructions in every message
Select this option if you do not want to want to append an opt-out instruction to every content-type message that is sent out.
Opt-out Message
Type the message you want to append as an opt-out instruction.
This field appears only if you select the Auto append opt-out Instruction in every message option.
Create Double Opt-In Configuration
|
Consent can be collected from multiple non-mobile sources like web forms, emails, marketing automation platforms, and even physical forms. Depending on the country of operation you will have to complete additional processes to ensure complete compliance adherence. For example, In the US, when a prospect sends an email, fills out a form or calls agents, they must apply a double opt-in before text messages are sent.
For a double opt-in, agents, on receiving the online consent request, sends a text message to recipients requesting them to confirm their consent with a keyword . The consent status of the recipients are set to pending till they use this keyword to confirm the request. On receiving the keyword from the prospect(recipient of the earlier request) , agents send a response confirming the consent. This completes the compliance process. The consent collection process can be automated. You can set up a process builder so that whenever a new lead is created you will be able to create a new record in the consent database. This section helps you create the configuration for double opt-in or confirmation messages for opt-ins via manual or online forms. All consent will be captured based on these configurations.
To Create a Double Opt-in Configuration
Under Double Opt-in & Others, click Create Configuration. The Create New Configuration screen appears.
Enter the details as required. Refer to the table below for more details:
Click Validate and Save. The Double-Optin & Others screen appears.
Click next to the double opt-in record you want to view and click View Details from the drop-down list.
Click next to the double opt-in record you want to remove and click Delete.
FIELD
DESCRIPTION
Source
Select the non-handset source from which you want to create consent records. The current version provides Manual as the only available source.
Confirmation Message Sender ID
Select the Sender ID from which the confirmation message will be sent.
OPT-IN
Send Confirmation Message
Select the option to send a confirmation message.
Double Opt-in
Select the option to enable the customer to send a double opt-in.
Opt-in Confirmation Message
Type the confirmation message that will be sent out for an Opt-in request.
Double Opt-In Message
Type the message that will be sent out to request for a Double Opt-in.This field appears only if you select the Double Opt-in option.
Double Opt-in Keyword
Type the keyword that will be used for sending double Opt-in requests.This field appears only if you select the Double Opt-in option.
Double Opt-in Confirm Message
Type the message that will be sent out to confirm a Double Opt-in request.This field appears only if you select the Double Opt-in option.
OPT-OUT
Opt-out Confirmation Message
Type the message that will be sent out to confirm an Opt-out request. This field will appear if you do not select the Double Opt-in option.
Manage Keywords
|
To comply with industry standards, you must respond to keywords for HELP & STOP. Any user who opts-out using the STOP keyword must be added to an opt-out list (blacklist) and must not be sent any further messages until or unless they opt back in. You can configure mandatory keywords for the three keyword types provided. These are:
Opt-out
Opt-in
Help
For each keyword type, some default keywords have already been pre-defined. You can also create new ones following industry specific norms.
Create keywords using the following guidelines:
Use Alphabets
Do not add spaces
Do not include special characters
When a customer uses the keywords defined under Opt-out keyword type, they will be opted out or blocked from receiving messages for all campaigns and other activities. You cannot send anymore messages to all such customers.
Similarly, when a customer uses the keywords defined under Opt-in keyword type, they choose to opt-in for receiving messages from any team within the organization.
You can define separate keywords to help customers opt-in for specific content type messages, for example, notification or promotions. These keywords will be considered for receiving consent for that specific content-type. Refer to Create Content type for more details on creating Content type keywords.
Content-type opt-ins are useful in ensuring that you can continue sending messages to customers for a specific content-type. Therefore, in case the customer is applying for a blanket opt-out instruction, in the opt-out confirmation message they receive, you specify the content-type opt-in they can send if they wish to continue receiving messages for that specific content-type.
Under Keyword Management, click Edit next to the Keyword type you want to modify. The Edit Keyword Configuration pop-up window appears.
Refer to the table below for more details on the Keyword options.
You cannot edit the default keywords.
FIELD
DESCRIPTION
Opt-In Keywords
Displays the opt-in keywords that will be used at the organization-wide level. You can define Opt-in keywords that are specific to a content type. Refer to the section on Create Content Type for more details.
Opt-Out Keywords
Displays the opt-out keywords that will be used at the organization-wide level. This will opt-out users from all the campaigns/content types. No further messages can be sent to customers from any teams in the organization.
Help Keywords
Displays the help keywords that will be used at the organization-wide level. This will redirect customers to request for support based on the keyword you provide.
Enter the following details to add keyword configuration.
FIELD
DESCRIPTION
Type
Displays the keyword type that you have selected to edit. For example, Opt-out, Opt-in, Help.
Keywords
Type the new keywords that you want to configure for the keyword type. You can type multiple keywords for a single keyword type. The new keywords should not be the same as the default keywords.
Message
Type the message that will be sent to customers who have sent the consent details.
Do you wish to enable this setting?
In the drop-down, select to indicate whether you want to enable the keyword type. If you disable the keyword type configuration, then customer consent sent for the keyword type will be ignored. For example, Customers who wish to Opt-out using the defined keywords will continue to receive messages if opt-out Keyword type configuration is disabled. Similarly, customers who wish to opt-in with the defined keywords will not be included in the subscription list if Opt-in keyword type configuration is disabled.
Click Save Changes. The Keyword Management section appears.
UnderOpt-out instructions click Change next to the pre-configured instruction. The Opt-out Instructions pop-up window appears.
Refer to the table below for more details on the Keyword options.
FIELD
DESCRIPTION
Auto append opt out Instruction in every message
Select the option if you want to add an opt-out instruction to every message that is sent out.
In an Interval
Select this option to send messages only after the defined number of weeks. The recommended practice is to send 1 message in every 4 weeks. You can select the interval period in the drop-down list that appears.
Do not Auto-append opt out instructions in every message
Select this option if you do not want to add an opt-out instruction to every message that is sent out.
Opt-out Message
Type the message you want to append as an opt-out instruction.This field appears only if you select the Auto append opt out Instruction in every message
Click Save.The opt-out instructions, if added, appears as shown.
Template Authors
|
Object
Field
Editable
Readable
Action_Object__c
Action__c
False
False
Action_Object__c
Object__c
False
False
Action_Parameter__c
Action__c
False
False
Action_Parameter__c
Object__c
False
False
Action_Parameter__c
Action_Parameter__c
False
False
Action_Parameter__c
Parameter_Type__c
False
False
Action_Parameter__c
Parameter__c
False
False
Action__c
Action_To_Perform__c
False
False
Action__c
Action_Type__c
False
False
Action__c
Description__c
False
False
Child_Object_Config__c
Parent_Object_Id__c
False
True
Contact
SMSOptOut__c
False
False
Conversation_Related_Objects__c
Absolute_Field__c
False
False
Conversation_Related_Objects__c
Conversation_Field__c
False
False
Conversation_Related_Objects__c
Relative_Field__c
False
False
Conversation_Sender_Map__c
SMS_SenderId__c
False
False
Conversation__c
Contact__c
False
False
Conversation__c
Converse_App_Action__c
False
False
Conversation__c
Converse_App__c
False
False
Conversation__c
Inbound_Number__c
False
False
Conversation__c
Last_Incoming_Time__c
False
False
Conversation__c
Last_Message_Direction__c
True
True
Conversation__c
Last_Message_Time__c
True
True
Conversation__c
Last_Outgoing_Time__c
True
True
Conversation__c
Lead__c
True
True
Conversation__c
Mobile_Number__c
True
True
Conversation__c
Mode__c
True
True
Conversation__c
New_Count__c
True
True
Conversation__c
Object__c
True
True
Conversation__c
Purpose__c
True
True
Conversation__c
Sender__c
True
True
Conversation__c
State__c
True
True
Conversation__c
account__c
True
True
Conversation__c
case__c
True
True
Conversation__c
isUnread__c
True
True
Conversation__c
opportunity__c
True
True
Converse_App_Action__c
Automation_Key__c
False
True
Converse_App_Action__c
End_Date__c
True
True
Converse_App_Action__c
Fallback_SenderId__c
True
True
Converse_App_Action__c
List_View_ID__c
True
True
Converse_App_Action__c
Message_App_Trigger_Name__c
True
True
Converse_App_Action__c
Message_App_Trigger__c
True
True
Converse_App_Action__c
Message_Sequence__c
True
True
Converse_App_Action__c
Message_Text__c
True
True
Converse_App_Action__c
Purpose__c
True
True
Converse_App_Action__c
Respect_Subscription_Setting__c
True
True
Converse_App_Action__c
SMS_Schedule__c
True
True
Converse_App_Action__c
SMS_Template__c
True
True
Converse_App_Action__c
SenderIDSelectionCriteria__c
True
True
Converse_App_Action__c
SenderIDSelectionType__c
True
True
Converse_App_Action__c
Start_Date__c
True
True
Converse_App_Action__c
Status__c
True
True
Converse_App_Action__c
Task_Owner_Criteria__c
True
True
Converse_App_Action__c
Template_Selection_Criteria__c
True
True
Converse_App_Action__c
Template_Selection_Type__c
True
True
Converse_App_Action__c
Trigger_URL__c
True
True
Converse_App_Task__c
Contact__c
True
True
Converse_App_Task__c
Converse_App_Action__c
True
True
Converse_App_Task__c
ErrorMessages__c
True
True
Converse_App_Task__c
Event_Id__c
True
True
Converse_App_Task__c
Incoming_SMS__c
True
True
Converse_App_Task__c
Lead__c
True
True
Converse_App_Task__c
SMS_History__c
True
True
Converse_App_Task__c
Status__c
True
True
Converse_App_Task__c
Task_Id__c
True
True
Converse_App_Task__c
Template__c
True
True
Converse_App_Template_Map__c
Type__c
True
True
Converse_App_User_Map__c
User__c
True
True
Converse_App__c
Action_Count__c
True
True
Converse_App__c
End_Date__c
True
True
Converse_App__c
ErrorMessages__c
True
True
Converse_App__c
ErrorState__c
True
True
Converse_App__c
Object__c
True
True
Converse_App__c
Owner__c
True
True
Converse_App__c
PrimaryType__c
True
True
Converse_App__c
Purpose__c
True
True
Converse_App__c
Start_Date__c
True
True
Converse_App__c
Status__c
True
True
Converse_Desk_Recently_Used_Filters__c
Filter_ID__c
True
True
Converse_Desk_Recently_Used_Filters__c
Filter_Object__c
True
True
Converse_Desk_Recently_Used_Filters__c
User__c
True
True
Converse_Desk_User_Config__c
Listing_Field__c
True
True
Converse_Desk_User_Config__c
Template_Field__c
True
True
Converse_Desk_User_Config__c
User__c
True
True
Error_Log__c
Batch_Id__c
True
True
Error_Log__c
Class_Name__c
True
True
Error_Log__c
Error_Message__c
True
True
Error_Log__c
Error_Status_Code__c
True
True
Error_Log__c
Error_Type__c
True
True
Error_Log__c
Fields__c
True
True
Error_Log__c
Line_number__c
True
True
Error_Log__c
Object__c
True
True
Error_Log__c
User__c
True
True
Filter_Setting__c
Field_Value__c
True
True
Incoming_Alert_Configuration__c
isCustomize__c
True
True
Incoming_Alert_Configuration__c
isDisable__c
True
True
Incoming_MMS_Detail__c
MMS_Type__c
True
True
Incoming_MMS_Detail__c
MMS_URL__c
True
True
Incoming_SMS__c
Campaign__c
True
True
Incoming_SMS__c
Case__c
True
True
Incoming_SMS__c
Contact__c
True
True
Incoming_SMS__c
Conversation__c
True
True
Incoming_SMS__c
Converse_App_Action__c
True
True
Incoming_SMS__c
Converse_App_Task__c
True
True
Incoming_SMS__c
Converse_App__c
True
True
Incoming_SMS__c
Favourite__c
True
True
Incoming_SMS__c
Inbound_Number__c
True
True
Incoming_SMS__c
Lead__c
True
True
Incoming_SMS__c
MMS_Type__c
True
True
Incoming_SMS__c
MMS_Url__c
True
True
Incoming_SMS__c
Mobile_Number__c
True
True
Incoming_SMS__c
Mobile_Number_without_ISD_Code__c
True
True
Incoming_SMS__c
New__c
True
True
Incoming_SMS__c
ObjectType__c
True
True
Incoming_SMS__c
Quick_Reply_URL__c
True
True
Incoming_SMS__c
SMS_Text__c
True
True
Incoming_SMS__c
Sent_By__c
True
True
Incoming_SMS__c
User__c
True
True
Incoming_SMS__c
actionTaken__c
True
True
Incoming_SMS__c
outgoing_sms__c
True
True
Incoming_SMS__c
taskId__c
True
True
Keyword_Action_Config__c
Field_To_Update__c
True
True
Keyword_Action_Config__c
Keyword__c
True
True
Keyword_Action_Config__c
Related_To__c
True
True
Keyword_Action_Config__c
Value__c
True
True
Keyword_Action_Map__c
Action_Type__c
True
True
Keyword_Action_Map__c
Converse_App_Action__c
True
True
Keyword_Action_Map__c
Keyword__c
True
True
LV_MMS_Detail__c
MMS_Type__c
True
True
LV_MMS_Detail__c
MMS_Url__c
True
True
Lead
SMSOptOut__c
True
True
License__c
Status__c
True
True
License__c
User__c
True
True
List_View_Configuration__c
Criteria_Logical_Condition__c
True
True
List_View_Configuration__c
Custom_Logic__c
True
True
List_View_Configuration__c
Expexted_SMS__c
True
True
List_View_Configuration__c
Filter_Criteria__c
True
True
List_View_Configuration__c
Filter_Fields__c
True
True
List_View_Configuration__c
MMS_Subject__c
True
True
List_View_Configuration__c
Object_Name__c
True
True
List_View_Configuration__c
OptOut_Records__c
True
True
List_View_Configuration__c
Optout_Field__c
True
True
List_View_Configuration__c
Phone_Fields__c
True
True
List_View_Configuration__c
Sender_Id__c
True
True
List_View_Configuration__c
Template_Body__c
True
True
List_View_Configuration__c
Template_Id__c
True
True
List_View_Configuration__c
Total_Records__c
True
True
List_View_Configuration__c
optOut_Check__c
True
True
List_View_Execution__c
BatchJobId__c
False
False
List_View_Execution__c
Expexted_SMS__c
False
False
List_View_Execution__c
List_View_Configuration__c
False
False
List_View_Execution__c
Messages_Delivered__c
False
False
List_View_Execution__c
Messages_Processed__c
False
False
List_View_Execution__c
Opt_Out_Records__c
False
False
List_View_Execution__c
Optout_Field__c
False
False
List_View_Execution__c
Phone_Fields__c
False
False
List_View_Execution__c
SMS_Text__c
False
False
List_View_Execution__c
Template_Name__c
False
False
List_View_Execution__c
Time_Taken__c
False
False
List_View_Execution__c
Total_Records__c
False
False
List_View_Execution__c
status__c
False
False
MMS_Detail__c
MMS_Type__c
False
False
MMS_Detail__c
MMS_Url__c
False
False
Message_Action__c
Action__c
False
False
Message_Action__c
Case__c
False
False
Message_Action__c
Incoming_SMS__c
False
False
Message_Action__c
Lead__c
False
False
Message_Action__c
SMS_History__c
False
False
Message_Object_Config__c
Name_Field__c
False
True
Message_Object_Config__c
Object_Name__c
False
True
Message_Object_Config__c
Opt_Out_Field_Value__c
False
True
Message_Object_Config__c
Opt_Out_Field__c
False
True
Message_Object_Config__c
Opt_Out_Operator__c
False
True
Object_Field_Config__c
Field_Name__c
False
True
Object_Field_Config__c
Field_Purpose__c
False
True
Object_Field_Config__c
Field_Type__c
False
True
Object_Field_Config__c
Object_Message_Config__c
False
True
Object_Field_Config__c
Unrelated_Object_Config__c
False
True
Object_Metadata_Config__c
Metadata_Id__c
False
True
Object_Metadata_Config__c
Metadata_Label__c
False
True
Object_Metadata_Config__c
Metadata_Type__c
False
True
Object_Metadata_Config__c
Parent_Object_Id__c
False
True
Optout_Settings__c
Keyword__c
False
False
Optout_Settings__c
Object_Name__c
False
False
Optout_Settings__c
Optout_Field__c
False
False
SMS_Batch_Execution_Tracker__c
Campaign__c
False
False
SMS_Batch_Execution_Tracker__c
Execution_Status__c
False
False
SMS_Batch_Execution_Tracker__c
Job_Id__c
False
False
SMS_Schedule__c
Campaign_Statuses__c
False
False
SMS_Schedule__c
Condition__c
False
False
SMS_Schedule__c
Date__c
False
False
SMS_Schedule__c
End_Date__c
False
False
SMS_Schedule__c
Exclude_Phone_Json__c
False
False
SMS_Schedule__c
Failure_Reason__c
False
False
SMS_Schedule__c
Job_ID__c
False
False
SMS_Schedule__c
List_View_Configuration__c
False
False
SMS_Schedule__c
Name_Field__c
False
False
SMS_Schedule__c
Object__c
False
False
SMS_Schedule__c
Optout_Field__c
False
False
SMS_Schedule__c
Phone_Field__c
False
False
SMS_Schedule__c
Record_Ids__c
False
False
SMS_Schedule__c
SMS_Template__c
False
False
SMS_Schedule__c
SMS_Text__c
False
False
SMS_Schedule__c
Schedule_JobId__c
False
False
SMS_Schedule__c
Schedule_Name__c
False
False
SMS_Schedule__c
Selected_Days_RecurWeek__c
False
False
SMS_Schedule__c
Selected_Months_RecurMonthly__c
False
False
SMS_Schedule__c
Selected_Months_RecurYearly__c
False
False
SMS_Schedule__c
Selected_User__c
False
False
SMS_Schedule__c
SenderId__c
False
False
SMS_Schedule__c
Show_Other_Users__c
False
False
SMS_Schedule__c
Status__c
False
False
SMS_Schedule__c
Template_Id_Json__c
False
False
SMS_Schedule__c
Unrelated_Object_ID__c
False
False
SMS_Schedule__c
Variable_Day_RecurDay__c
False
False
SMS_Schedule__c
isOptout__c
False
False
SMS_Schedule__c
isRecurring__c
False
False
SMS_Schedule__c
recursTypeForDaily__c
False
False
SMS_Schedule__c
recursTypeMonthly__c
False
False
SMS_Schedule__c
recursTypeYearly__c
False
False
SMS_Schedule__c
recursType__c
False
False
SMS_Schedule__c
selectedDateForYear__c
False
False
SMS_Schedule__c
selectedDayForMonth1__c
False
False
SMS_Schedule__c
selectedDayForMonth2__c
False
False
SMS_Schedule__c
selectedMonthForYear__c
False
False
SMS_Schedule__c
selectedMonth__c
False
False
SMS_Schedule__c
selectedWeekDayForYear__c
False
False
SMS_Schedule__c
selectedWeekForMonth__c
False
False
SMS_Schedule__c
selectedWeekForYear__c
False
False
SMS_Schedule__c
variableMonth1__c
False
False
SMS_Schedule__c
variableMonth2__c
False
False
SMS_SenderId__c
Description__c
False
False
SMS_SenderId__c
Email_Notification_Template__c
False
False
SMS_SenderId__c
Label__c
False
False
SMS_Template_Type__c
Related_Object_Types__c
True
True
SMS_Template__c
Description__c
True
True
SMS_Template__c
Name__c
True
True
SMS_Template__c
ObjectName__c
True
True
SMS_Template__c
Text__c
True
True
Scheduled_SMS__c
MobilePhone__c
False
False
Scheduled_SMS__c
ObjectId__c
False
False
Scheduled_SMS__c
Object_Type__c
False
False
Scheduled_SMS__c
Scheduled_Date__c
False
False
Scheduled_SMS__c
smsText__c
False
False
SenderId_Profile_Map__c
Default_SenderId__c
False
True
SenderId_Profile_Map__c
Profile_Id__c
False
True
SenderId_Profile_Map__c
Profile__c
False
True
SenderId_Profile_Map__c
SenderId_Lookup__c
False
True
SenderId_Profile_Map__c
Sender_Id__c
False
True
SenderId_Profile_Map__c
User__c
False
True
Unrelated_Object_Config__c
Parent_Object_Id__c
False
True
forward_config__c
Keyword__c
False
False
forward_config__c
forwardToEmail__c
False
False
forward_config__c
forwardToMobilePhone__c
False
False
forward_config__c
forwardToUser__c
False
False
forward_config__c
methodName__c
False
False
incoming_lookup_config__c
MobilePhoneField__c
False
False
incoming_lookup_config__c
Notify_Record_Owner__c
False
False
incoming_lookup_config__c
ReferenceField__c
False
False
incoming_lookup_config__c
incoming_sms_owner__c
False
False
lookup_config__c
lookupFound__c
False
False
lookup_config__c
lookupNotFound__c
False
False
smsMagic__c
Account__c
False
False
smsMagic__c
Campaign__c
False
False
smsMagic__c
Case__c
False
False
smsMagic__c
Contact__c
False
False
smsMagic__c
Conversation__c
False
False
smsMagic__c
Converse_App_Action__c
False
False
smsMagic__c
Converse_App_Task__c
False
False
smsMagic__c
Converse_App__c
False
False
smsMagic__c
Country__c
False
False
smsMagic__c
CreatedOn__c
False
False
smsMagic__c
Delivery_Error_Message__c
False
False
smsMagic__c
Direction__c
False
False
smsMagic__c
Favourite__c
False
False
smsMagic__c
Is_Text_Unicode__c
False
False
smsMagic__c
Lead__c
False
False
smsMagic__c
MMS_Subject__c
False
False
smsMagic__c
Message_Type__c
False
False
smsMagic__c
Name__c
False
False
smsMagic__c
New__c
False
False
smsMagic__c
ObjectType__c
False
False
smsMagic__c
Opportunity__c
False
False
smsMagic__c
PhoneNumber__c
False
False
smsMagic__c
Previous_Message__c
False
False
smsMagic__c
SMSText__c
False
False
smsMagic__c
SMS_Credits__c
False
False
smsMagic__c
SMS_Template__c
False
False
smsMagic__c
SenderId__c
False
False
smsMagic__c
Sent_By__c
False
False
smsMagic__c
Sent_On__c
False
False
smsMagic__c
Source__c
False
False
smsMagic__c
Status__c
False
False
smsMagic__c
Type__c
False
False
smsMagic__c
Unformatted_Phone_Number__c
False
False
smsMagic__c
Use_Default_Sender__c
False
False
smsMagic__c
User__c
False
False
smsMagic__c
deliveryStatus__c
False
False
smsMagic__c
disableSMSOnTrigger__c
False
False
smsMagic__c
response__c
False
False
smsMagic__c
sentStatus__c
False
False
smsMagic__c
statusMessage__c
False
False
Deprecated Fields
|
Object Name
Field Name
Field Label
Field Description
SenderId_Profile_Map__c
Default_SenderId__c
Default SenderId
This field contains the sender ID of the user.
SenderId_Profile_Map__c
Profile__c
Profile
This field contains the profile name related to the sender ID of the user.
SenderId_Profile_Map__c
Sender_Id__c
Sender Id (Deprecated)
Deprecated from version 1.31. Use smagicinteract__Default_SenderId__c field instead.
Message_Action__c
Action__c
Action
This field contains the ID of the related Action.
Message_Action__c
Case__c
Case
This field contains the ID of the related Action.
Message_Action__c
Incoming_SMS__c
Incoming SMS
This is a message sent by the end user.
Message_Action__c
Lead__c
Lead
This is a prospect that needs to be qualified as a real sales opportunity.
Message_Action__c
SMS_History__c
SMS History
This field keeps the record of all outgoing and incoming SMS.
Conversation_View_Setting__c
All__c
All
Conversation_View_Setting__c
Default_Sender__c
Default Sender
Conversation_View_Setting__c
Owner__c
Owner
List_View_Execution__c
BatchJobId__c
BatchJobId
List_View_Execution__c
Expexted_SMS__c
Expexted SMS
List_View_Execution__c
List_View_Configuration__c
List View Configuration
List_View_Execution__c
Messages_Delivered__c
Messages Delivered
List_View_Execution__c
Messages_Processed__c
Messages Processed
List_View_Execution__c
Opt_Out_Records__c
Opt Out Records
List_View_Execution__c
Optout_Field__c
Optout Field
List_View_Execution__c
Phone_Fields__c
Phone Fields
List_View_Execution__c
SMS_Text__c
SMS Text
List_View_Execution__c
Template_Name__c
Template Name
List_View_Execution__c
Time_Taken__c
Time Taken
List_View_Execution__c
Total_Records__c
Total Records
List_View_Execution__c
status__c
status
LV_MMS_Detail__c
List_View_Configuration__c
List View Configuration
LV_MMS_Detail__c
MMS_Type__c
MMS Type
LV_MMS_Detail__c
MMS_Url__c
MMS Url
Incoming_Alert_Configuration__c
isCustomize__c
Customize For Each User
Incoming_Alert_Configuration__c
isDisable__c
Disable For All
SMS_Magic_SetUp_Tracker__c
step_1__c
Step 1
SMS_Magic_SetUp_Tracker__c
step_2__c
Step 2
SMS_Magic_SetUp_Tracker__c
step_3__c
Step 3
SMS_Magic_SetUp_Tracker__c
step_4__c
Step 4
SMS_Magic_SetUp_Tracker__c
step_5__c
Step 5
SMS_Magic_SetUp_Tracker__c
step_6__c
Step 6
global_settings__c
Allow_Popup_Msg__c
Acknowledgement Popup Setting
Select this field to enable popup to confirm an outgoing message.
Incoming_SMS__c
MMS_Url__c
MMS Url
Incoming_SMS__c
Quick_Reply_URL__c
Quick Reply URL
Incoming_SMS__c
Sent_By__c
Sent By
incoming_lookup_config__c
MobilePhoneField__c
Search MobileField Name
incoming_lookup_config__c
Notify_Record_Owner__c
Notify Record Owner
incoming_lookup_config__c
ReferenceField__c
Reference Name on Incoming Object
incoming_lookup_config__c
incoming_sms_owner__c
Incoming SMS Owner
incoming_lookup_config__c
objectName__c
Lookup Object Name
SMS_Template_Type__c
Related_Object_Types__c
Related Object API Name
SMS_Template_Type__c
Template_Object_Type__c
Object API Name
Optout_Settings__c
Keyword__c
Keyword
Optout_Settings__c
Object_Name__c
Object Name
Optout_Settings__c
Optout_Field__c
Optout Field
Scheduled_SMS__c
MobilePhone__c
MobilePhone
Scheduled_SMS__c
ObjectId__c
ObjectId
Scheduled_SMS__c
Object_Type__c
Object Type
Scheduled_SMS__c
Scheduled_Date__c
Scheduled Date
Scheduled_SMS__c
jobId__c
jobId
Scheduled_SMS__c
smsText__c
smsText
Scheduled_SMS__c
status__c
status
Filter_Setting__c
Field_Name__c
Field Name
Filter_Setting__c
Field_Value__c
Field Value
Filter_Setting__c
List_View_Configuration__c
List View Configuration
Filter_Setting__c
Operator__c
Operator
List_View_Configuration__c
Criteria_Logical_Condition__c
Criteria_Logical_Condition
List_View_Configuration__c
Custom_Logic__c
Custom Logic
List_View_Configuration__c
Expexted_SMS__c
Expexted SMS
List_View_Configuration__c
Filter_Criteria__c
Filter Criteria
List_View_Configuration__c
Filter_Fields__c
Filter Fields
List_View_Configuration__c
MMS_Subject__c
MMS Subject
List_View_Configuration__c
Object_Name__c
Object Name
List_View_Configuration__c
OptOut_Records__c
OptOut Records
List_View_Configuration__c
Optout_Field__c
Optout Field
List_View_Configuration__c
Phone_Fields__c
Phone Fields
List_View_Configuration__c
Sender_Id__c
Sender Id
List_View_Configuration__c
Template_Body__c
Template Body
List_View_Configuration__c
Template_Id__c
Template Id
List_View_Configuration__c
Total_Records__c
Total Records
List_View_Configuration__c
optOut_Check__c
optOut Check
Converse_App_Action__c
Trigger_URL__c
Trigger URL
Acknowledgement_Popup_Setting__c
Allow_Popup_Msg__c
Allow Popup Msg
smsMagic__c
Delivery_Error_Message__c
Delivery Error Message
smsMagic__c
Favourite__c
Favourite
smsMagic__c
deliveryStatus__c
Delivery Status
This field is deprecated from version 1.52.We suggest not to refer to this field anymore. It is present because few of our customers on older versions refer to this field for reporting purposes. You should refer to the Status’ field only to know the correct status of sent messages.
smsMagic__c
response__c
Response
smsMagic__c
sentStatus__c
Sent Status
This field is deprecated from version 1.52.We suggest not to refer to this field anymore.It is present because few of our customers on older versions referring to this field for reporting purposes.You should refer to the ‘Status’ field only to know the correct status of sent messages.