See Also
The Send SMS and Double Opt-In(SMS) Properties are updated based on the type of keyword received from a Contact or Lead in an incoming SMS message. The values in these Properties are used to configure appropriate Mailing Lists to send SMS Campaigns to Targets.
Table 1 provides sample values of Contacts and Leads that are used as a reference to illustrate the scenarios in Table 2.
Table 2 describes the various scenarios that determine the values that are set for the Send SMS and Double Opt-In(SMS) Properties of the Lead and Contact Objects.
| Table 1: | Sample Values for Contacts and Leads |
|
Contact |
Leads associated with the Contact |
Mobile Number |
Send SMS |
Double Opt-In(SMS)
|
|
Contact1 |
8654320719 |
No |
No |
|
|
|
Lead1 |
8654320719 |
No |
No |
|
Lead2 |
7890654321 |
Yes |
Blank |
|
|
Contact2 |
8654320822 |
Yes |
Yes |
|
|
|
Lead3 |
8654320822 |
Yes |
Yes |
|
Lead4 |
8654320719 |
Yes |
Blank |
|
|
Contact3 |
8654320933 |
Yes |
Blank |
|
|
|
Lead5 |
8654320933 |
Yes |
Blank |
|
|
Lead6 |
8654320934 |
No |
No |
| Table 2: | Scenarios for the Values Set in the Send SMS and Double Opt-In(SMS) Properties |
|
Scenario |
Value of the Send SMS Property |
Value of the Double Opt-In(SMS) Property |
|
1. When the Mobile Property of a Lead or Contact is not specified during Lead or Contact creation in Talisma through any of the following Talisma Modules: ◦ Talisma Client ◦ Import operation ◦ Talisma iServices ◦ Talisma Customer Portal ◦ Talisma Web Forms |
No |
Blank |
|
2. When the Mobile Property of a Lead or Contact is specified during Lead or Contact creation in Talisma through any of the following Talisma Modules: ◦ Talisma Client ◦ Import operation ◦ Talisma iServices ◦ Talisma Customer Portal ◦ Talisma Web Forms |
Yes |
Blank |
|
3. When the Mobile Property of a Lead or Contact is updated through any of the following Talisma modules: ◦ Talisma Client ◦ Import operation ◦ Talisma iServices ◦ Talisma Customer Portal ◦ Talisma Web Forms |
||
|
• If the specified mobile number already exists in the Contact associated with the Lead or in any Leads that are associated with the Contact. For example,in Table 1, the mobile number of Lead1 is updated to 7890654321, which is the mobile number for Lead2. In this scenario, the values of the Send SMS and Double Opt-In(SMS) Properties of Lead2 are set for Lead1. |
Copy the value from Lead2. This will be set to Yes. |
Copy the value from Lead2. This will be set to Blank. |
|
• If the specified mobile number does not exist in the Contact associated with the Lead or in any Leads that are associated with the Contact. Example: For example,in Table 1, the mobile number of Lead1 is updated to 7890654312, which does not exist either in its associated Contact Contact1 or in the Leads associated with Contact1. In this scenario, the Send SMS and Double Opt-In(SMS) Properties of Lead1 are set to the default values of these Properties. |
Yes |
Blank |
|
4. When the Contact associated with a Lead is changed through any of the following Talisma modules: ◦ Talisma Client User manually changes the Contact of a Lead ◦ Through Import operation ◦ Through Talisma iServices |
||
|
• If the mobile number of the Lead matches with the mobile number of the new Contact or the mobile number of any Leads that are associated with the Contact. For example, in Table 1, Contact1 is removed and Contact2 is associated with Lead1. In this scenario, the mobile number of Lead1 is 8654320719, which is also the mobile number of Lead4 that is associated with Contact2. In this scenario, the Send SMS and Double Opt-In(SMS) Properties of Lead1 are updated with the values of the Send SMS and Double Opt-In(SMS) Properties of Lead4. |
Copy the value from Lead4. This will be set to Yes. |
Copy the value from Lead4. This will be set to Blank. |
|
• If the mobile number of the Lead does not match the mobile number of the new Contact or the mobile number of any Leads that are associated with the Contact. For example, in Table 1, Contact1 is removed and Contact3 is associated with Lead1. In this scenario, the mobile number of Lead1 is 8654320719, which does not match with the mobile number of Contact3 and the Leads associated with Contact3. In this scenario, the Send SMS and Double Opt-In(SMS) Properties of Lead1 will be retained. |
Retain the existing value. This will be retained as No.
|
Retain the existing value. This will be retained as No. |
|
5. When a Contact or Lead responds to an SMS with an exact match for the Opt-In Keyword. |
Yes |
Yes |
|
6. When a Contact or Lead responds to an SMS with an exact match of the Opt-Out Keyword. |
No |
No |
|
7. When a Contact or Lead does not respond to the SMS, or responds with a message that is not an exact match of the Opt-In or Opt-Out Keywords. |
Retain the existing value. |
Retain the existing value. |
|
8. When a Talisma Client User updates the Send SMS Property to Yes for a Lead or Contact. |
Yes Note: This value will be set for all the Lead items associated with the Contact if they have the same mobile number. |
Retain the existing value. |
|
9. When a Talisma Client User updates the Send SMS Property to No for a Lead or Contact. |
No Note: This value will be set for all the Lead items associated with the Contact if they have the same mobile number. |
Retain the existing value. |
|
10. When a deleted Lead or Contact is restored from the Trash Can Workspace |
||
|
• If the mobile number of the restored Lead matches with the mobile number of the Contact or any Leads that are associated with the Contact. For example, in Table 1, Lead6 is deleted from Talisma. A Talisma Client User creates Lead7 with mobile number 8654320934 and associates it with Contact3. The values of the Send SMS and Double Opt-In(SMS) Properties of Lead7 are set to Yes and blank by default. The Talisma Client User later restores Lead6 from the Trash Can Workspace. In this scenario, as the mobile number of Lead6 matches with the mobile number of Lead7, the Send SMS and Double Opt-In(SMS) Properties of Lead6 are updated with the values of the Send SMS and Double Opt-In(SMS) Properties of Lead7. |
Copy the value from Lead7 to the restored Lead. This will be set to Yes. |
Copy the value from Lead7 to the restored Lead. This will be Blank. |
|
• If the mobile number of the restored Lead does not match with the mobile number of the Contact or the mobile number of any Leads that are associated with the Contact. For example, in Table 1, a Talisma Client User deletes Lead2. When the Talisma Client User restores Lead2 from the Trash Can Workspace, the Send SMS and Double Opt-In(SMS) Properties of Lead2 are retained because the mobile number of Lead2 does not match the mobile number of Contact1 or Lead1. |
Retain the existing value. This will be set to Yes. |
Retain the existing value. This will be set to blank. |
|
11. When an archived Lead is restored |
||
|
• If the mobile number of the restored Lead matches the mobile number of the associated Contact or Leads associated with the Contact. For example, in Table 1, Lead1 is archived in Talisma. In the meantime, Contact1 sends an Opt-In keyword to Talisma. As a result, the values of the Send SMS and Double Opt-In(SMS) Properties of Contact1 are updated to Yes. A Talisma Client User restores the archived Lead1. In this scenario, as the mobile number of Lead1 matches with the mobile number of Contact1, the Send SMS and Double Opt-In(SMS) Properties of Lead1 are updated with the values of the Send SMS and Double Opt-In(SMS) Properties of Contact1. |
Copy the value from Contact1 to the restored Lead Lead1. |
Copy the value from Contact1 to the restored Lead Lead1. |
|
• If the mobile number of the restored Lead does not match with the mobile number of the associated Contact or any Leads associated with the Contact. For example, in Sample Values for Contacts and Leads, Lead2 is archived in Talisma. A Talisma Client User restores the archived Lead2. As the mobile number of Lead2 does not match with the mobile number of Contact1 or Lead1, the Send SMS and Double Opt-In(SMS) Properties of Lead2 are set to the default values of these two Properties. |
Reset to the default value, which is Yes. |
Reset to default value, which is blank. |
|
Note • When you merge two Contacts, the Double Opt-In(SMS) and Send SMS Properties in both Contacts are changed to read-only and cannot be selected. If the mobile number of the source Contact is selected, the Send SMS and Double Opt-In(SMS) Properties of the retained Contact will be updated based on the update scenario 3 that is explained in “Behavior of the Send SMS and Double Opt-In(SMS) Properties”. Additionally, when the Contacts are merged, the Leads associated with the first Contact are associated with the retained Contact. As a result, the values of the Send SMS and Double Opt-In(SMS) Properties are updated based on scenario 4 that is explained in “Behavior of the Send SMS and Double Opt-In(SMS) Properties”. • Consider a scenario where Properties Inheritance Mapping is configured for the Mobile Property between the Lead and Contact Objects in Talisma Business Administrator. In Talisma Client, when the Mobile Property of a Lead or Contact is updated and the Mobile Property of the associated Contact or Lead is updated automatically or manually, the Send SMS and Double Opt-In Property values for the Mobile number are inherited from the Lead to Contact or vice versa. • In Talisma Business Administrator, Properties Inheritance Mapping cannot be configured for the Double Opt-In(SMS) Property between the Lead and Contact Objects. • When Properties Inheritance Mapping is configured for the Send SMS Property between the Lead and Contact Objects in Talisma Business Administrator, the Auto Update and Manual Update values are not be available for configuration in the Update Type column. • The Double Opt-In(SMS) Property of the Lead and Contact Objects is not available for configuration in Talisma Rules. • Although audit can be enabled for the Double Opt-In(SMS) and Send SMS Properties for the Lead and Contact Object in Talisma Business Administrator, audit information will not be displayed in the History tab of the Lead and Contact Objects in Talisma Client. • When an SMS Message is received with the Opt-In or Opt-Out keyword from a Lead or Contact, the Send SMS and Double Opt-In(SMS) values are updated for all Leads and Contacts that have the same mobile number, including Leads and Contacts in the Trash Can Workspace. • When you add a mobile number for a Lead and set the Send SMS Property to No, on saving the Lead, the Send SMS Property is set to Yes. However, if you modify the mobile number and set the Send SMS Property to No, on saving the Lead, the Send SMS Property is set to No. This behavior is applicable for the Contact Object also. • When a format is specified for mobile numbers of Leads and the data is imported by using Talisma Data Management Utility, the format of the mobile number is retained for the imported Leads. If an existing Lead has the same mobile number as an imported Lead but is not formatted, the Send SMS and Double Opt-In(SMS) Properties of the two Leads may differ. For example, a Lead with Mobile number 8786453645 and Send SMS and Double Opt-In(SMS) values as Yes is available in Talisma. When another Lead with mobile number 878-645-3645 is imported, the Lead's mobile number is retained as 878-645-3645. Although the mobile number of the imported Lead and the existing Lead are identical, the Send SMS and Double Opt-In(SMS) Properties of the existing Lead will not be copied to the imported Lead. |
Send feedback on this topic (documentation@campusmgmt.com)
Last Updated: 9/16/2019
© 2019 Talisma Corporation Private Ltd., a subsidiary of Campus Management Corp. | www.campusmanagement.com