Identify and manage contacts that opted in and opted out of SMS programs by creating a query for SMS consent. You can import a list of contacts into your Acoustic Campaign database. Consent works when the SMS user enables the database for SMS.

If the end user is opted-in or opted-out of the program using the SMS Campaign manager, the SMS campaign source field does not contain any values.

Manage SMS consent

1. In Campaign, go to Data > Database > View data.
2. Select your SMS-enabled database.
3. Click the Search tab.
4. Search and select the contact that you would like to see on the SMS consent summary page. The Edit contact page opens.
5. Click the SMS consent summary button and find the SMS consent where the contact is currently enrolled.

On the SMS consent summary page, if the contact's status is OPTED-IN, then the contact has given consent to receive SMS messages.

SMS consent status after a contact merge

When you perform a merge contact action in the SMS-enabled database, the system retains the SMS consent status of a contact.

You can currently merge up to three contact records into one, and if the master record has the same SMS-enabled phone number as a losing record, the consent state from the losing record to be merged into the winning record. In all variations of merging up to three recipients, if the SMS phone number is in the winning record, we will retain its consent status on the text to join programs that the SMS phone number is opted-in or opted-out.

1. In Campaign, go to Data > Database > View data.
2. Select your SMS-enabled database.
3. Click the Search tab.
4. Click the Find duplicate contacts button.
5. Choose how you want to find your duplicate records. For example, if you use the SMS phone field, the SMS-enabled field is selected.
6. Click Find.
7. Check the boxes to select the contact records you would like to merge together. Then click the Merge link to review how these records merge together.
8. After the data job completes, all consent data that was with the losing records is deleted.

The following scenarios may occur when merging contacts together.

Scenario 1

The master record has to include the SMS phone number with an OPTED-IN or OPTED-OUT status to a text to join Program X for consent to follow it.

Using the example below, if Contact 2 or Contact 3 have the same SMS phone number, but are opted in or opted out of different text to join programs, then the consent for the text to join programs is added or merged into the master record and vice versa for opted out status. Note that the phone numbers in the SMS phone fields are the same. The Email fields may contain different email addresses.

Scenario 2

If the master record does not contain the SMS phone number with consent, then the consent data is not merged into the master record.

Using the example below, when the records that are being merged together have different phone numbers and the winning phone number is selected, if it is the SMS phone field then consent follows. Notice that the phone numbers in the SMS Phone fields are different. The Email fields contain the same email addresses.

SMS consent status after a list (database) merge/purge

When merging or purging two databases and one is an SMS-enabled database, SMS consent will not be carried into the newly created merged database. The original SMS-enabled database will stay intact and SMS consent will remain the same.

The Purge button is located in Data > View data.

Select the SMS-enabled database to purge against another database.

Create a query for SMS consent

Create a query to capture contacts who have consented to receive SMS messages and run your SMS campaigns quicker and easier.

1. In Campaign menu, go to Data > Queries and click Create.
2. Complete the fields in the Save query as dialog box:
   1. Choose database to query: Click Browse and select your SMS-enabled database.
   2. Save query as: Name the query.
   3. Location: Save the query in a shared folder so all users in your organization can access the query.
   4. Type: Select Query.
   5. Click OK to open the Query builder.
3. Build the query:
   1. Click Profile and select Channel.
   2. Contact: In the Choose channel behavior list, select Is opted-in to channel.
   3. Channel: Select SMS.
   4. Text to join program(s): Click Choose and select one or more text to join programs.
   5. Click Done.
4. Click Save and calculate.
5. Review the query details on the Calculate query size data job page and then click Submit.

When the data job is complete, you can click the query name to view the Query summary page. Click the Search tab to see the consent status for individual contacts.

Import contacts with consent

Use the list import wizard to import multiple contacts with SMS consent data into your SMS database. When using SMS consent contact source update type, the SMS consent field must be present in the imported file. If a contact record's SMS consent field is blank, we do not import the contact. If you want to add new contacts into your SMS enabled database without consent, use the normal list import contact source update type.

1. In Acoustic Campaign, go to Data > Database > Import update to open the Import update existing page.
2. Complete the template and then click Next.
   1. Add new contacts: In SMS context, this option in list import looks only for new contacts in the imported file with SMS opted-in or opted-out consent data, for a specified text to join program. If one of the contact records exists in the SMS-enabled database and also in the data file, even with consent data, they are ignored as this list import action is only for new contacts.
   2. Update field values in the contact source: This option looks for updated contacts data in the data file that matches to existing contacts.
      1. We update only the contacts' consent state if it is opposite their current state in the database. For example, if someone performs an update and in the imported file they are opted-in and in the database they are opted-in, we do not update their record (specific to text to join programs). New contacts are ignored.
      2. If they do not have any consent data, the list import update also adds new consent data for existing contacts.
   3. Add new contacts and update existing field values in the contact source: This option imports new and looks for updating contacts data in the data file and the database. List import Add and Update adds in new contacts with consent, updates the contacts consent state if it is opposite to the current state of the contact in the database, and adds new consent data for the existing contacts if they don’t have any consent data.
   4. Choose import update type: Select SMS consent contact source.
   5. Select the contact source you wish to update. Choose an option:
      1. Consent manager: Imports contacts and consent data to a specific text to join program. Select a text to join program.
      2. Contact lists: Imports contacts into a certain contact list and adds consent. Select to import either a .csv, .tsv, or.psv file through the user interface.

Map fields

There are specific SMS consent fields that you must map so SMS consent can be imported and updated to your contacts mobile phone number records. Before you begin, make sure that the SMS phone number field is listed and displays as the SMS phone number field type.

Map the import fields to the following consent fields and then click Next:

• SMS consent status (required, OPTED-IN or OPTED-OUT)
• SMS consent date
• SMS consent source

SMS consent date is when you collected the consent. SMS consent source is where you collected the consent, like a physical store or call center. If SMS consent date or SMS consent source is left blank in the imported file and is not mapped, the system defaults will go into place, as this information must also be recorded for historical purposes when the information hits the system.

• SMS consent date (uses system default: SysDate)
• SMS consent source (uses system default: List import)

Edit field settings

The SMS consent fields are listed in a separate table. Note the default values that will be used if the SMS consent date and SMS consent source are left blank in your imported file.

Review the information and click Next.

Select sync fields

The system automatically selects the option that you will sync the SMS Consent records by the required SMS Phone Number field. Consent records will follow the SMS Phone Number field.

Click Next.

Submit the data job

1. Confirm the information is correct.
2. To receive an email notification when the job's status is complete, enter your email address. You may check the status at any time on the Data jobs page.
3. Click Submit.

SMS consent date/time update rules

Scenario 1

A contact has an unknown SMS consent status or is opted out of the SMS program before the API call.

The contact's consent date/time is updated after the API call if:

• You use the importlist API to update the database and include the SMS consent field in the API request.
• The API request is to opt in the contact to the SMS program.

Scenario 2

A contact was opted in to an SMS program before the API call was received

If the SMS consent date is not provided during the import process, the system uses the import date/time as the consent date. The system updates the existing consent date if:

• You use the importlist API to update the database and include the SMS consent field in the API request.
• The API request is to opt-in the contact to the SMS program.

Update campaign with SMS opt-out consent status

SMS consent is handled by Acoustic Campaign's Consent table and is considered the database of record. You must keep SMS opt-in and opt-out statuses up to date.

Complete the following steps:

1. In Campaign, go to Data and create a query to find contacts who have opted-in or opted-out of a text to join program. Use one query per program to ensure accuracy. When you create your query, use these query parameters:
   1. Click Profile and select Channel.
   2. Contact: In the Choose channel behavior list, select Is opted out of channel.
   3. Channel: Select SMS.
   4. Text to join program(s): Click Choose and select one or more text to join programs.
2. In Unica Campaign, schedule the Campaign flowcharts that trigger the contactUpload and contactDownload scripts to run automatically. The contactDownload script exports the query data when you specify the Query ID. You can also automate this within Campaign. To update SMS consent status, you must use the custom SMS mapping file that is provided as part of the Campaign integration with Acoustic Campaign download package. For details, refer to Chapter 6. Contact data download – Acoustic Campaign to Campaign in the Integration Guide or SMS text messaging: using HCL Unica Campaign and Acoustic Campaign.