Field mappings

Field mappings refer to the process of uploading a template or sample data and mapping the headers with the headers of dialer system. You can also define the data type for each header or define if a header needs to be encrypted. The headers of the dialer system will be mapped to the sample data type.

When you create a campaign, you have to assign the field mappings to a campaign and an appropriate contact list has to be uploaded. When you upload a contact list to a campaign, and if the headers of the field mappings do not match, then you will get an error.

📘

When a file header is marked as PII-enabled and locked in one field mapping, the same header will be treated as PII-enabled in all other field mappings—both existing and future.

For example, if the header CREDIT_CARD_NUMBER is marked as PII-enabled and locked in one field mapping, it will be considered PII-enabled in any other field mapping where the same header appears.

When a file header is marked as PII-enabled and locked in one field mapping, the same header will be treated as PII-enabled in all other field mappings—both existing and future.

For example, if the header CREDIT_CARD_NUMBER is marked as PII-enabled and locked in one field mapping, it will be considered PII-enabled in any other field mapping where the same header appears.

Hence make sure you upload the correct contact list to a campaign to avoid datatype mismatch errors.

📘

The PII enabled/encrypted field mapping file headers of a contact list are not available for applying conditions in Contact selection filters and in Search contacts screen.


Create field mapping

  1. Navigate to Voice campaign administration > Field mappings. The Field mappings list screen will be displayed.
  2. Click Create field mappings. Enter a name for the field mapping and complete the steps mentioned below:

  1. Step 1: Upload sample file: Click Choose file and select the .txt (pipe delimited) or .csv (comma separated) file.
  2. Once the file upload is successful, the screen will display the List of headers of the file, Field separator in read-only mode and File char set. You can change the File char set as needed.

  1. Step 2: Map contact modes: Select the drop-down of each header and map with the corresponding contact modes. This will ensure that appropriate number is dialed based on schedule.

  1. Step 3: Specify country of all the phone numbers: Select the country for which the field mapping is created. Select the format of the phone number. We support 4 phone number formats.

  1. Step 4: Map source of telephone area codes: This step is applicable for North America only.
  2. Step 5: Map source of timezones: Select one of the below options:
    1. Not derived from the contact list: Select this option if you want to configure the timezone at the time of campaign creation.
    2. Derived from the contact list (US / Canada telephone area code): Select this option if the telephone area codes are derived from contact list.
    3. Derived from the contact list : US ZIP codes: Select this option if the ZIP codes are derived from contact list.
  3. Step 6: Map source of US ZIP codes: Select one of the below options:
    1. ZIP code info not available in the file: Select this option if the zip code is not available in the uploaded file.
    2. Specified in the contact list: US ZIP Code: Select this option if the zip code is available in the uploaded file. When this option is selected, another drop-down is displayed to select the zip code header. The value in this ZIP code header will be used for timezone inference.

  1. Step 7: Map source of US/Canada state/province code: This step is applicable for the US and Canada only.
  • State/Province info not available in the contact list: Select this option if the state/province code is not available.
  1. Step 8: Map global variables: Select appropriate header from the drop-down to map with the respective global variables.

  1. Step 9: Specify file header data types: Select appropriate data type from the drop-down.

📘

PII encryption is allowed only if the data type is String.

📘

The data type of the 'ZIP code' file header should be set to String. Otherwise, ZIP codes that begin with a zero (e.g., 00501) may appear as 501, which would make the U.S. ZIP code invalid since it must contain six digits.

  1. Click Save field mapping.

Edit field mapping

You can edit a field mapping if it is not associated with any campaign. Any field mapping associated to a campaign will not be allowed for editing irrespective of the campaign status.

Follow these steps to edit field mappings:

  1. Navigate to Voice campaign administration > Field mappings. The Field mappings list screen will be displayed.
  2. Click the ellipses icon of the respective field mapping and click Edit.

  1. Make necessary changes to the field mapping and click Update field mapping.

View list of associated Campaigns

You can view all the campaigns that are associated with respective mapping.

Follow these steps to view the campaigns associated with the campaigns:

  1. Navigate to Voice campaign administration > Field mappings. The Field mappings list screen will be displayed.
  2. Click the ellipses icon of the respective field mapping and click List of associated Campaigns.

  1. The screen will display the campaigns and their status that are associated with the selected field mappings.

  1. (Optional) To find a campaign, type the campaign name in the search box.
  2. Click OK to close the screen.

Important Notes:

a) All phone numbers (contact mode values) for a single contact must follow the same format and belong to the same country.
b) All contact records within a file must use the same phone number format for a country.
c) Phone numbers must not contain spaces, hyphens, or any other non-numeric characters.