Custom time zone map data sets

When third-party data sets are used, Dialer's time zone mapping feature is primarily targeted at North American telephone numbers.  This is because commercial data sets support telephone numbers in the North American Numbering Plan (NPANXX), which covers the United States, and in some cases, Canada. 

Open Data Set Format

International customers are not excluded from using time zone mapping. Interaction Dialer supports an open data set format that customers can use to create custom time zone map data sets. It is easy to define zone mappings for areas other than North America. 

The open data set format is a text file with an extension of .dat or .txt.  The text file must conform to the following structure:

PHONE NUMBER + TAB + ZONE NAME

• PHONE NUMBER should be entered without hyphens or parenthesis. Wildcarding is allowed using the '*' character. Once a wildcard digit is used, all digits to the right of the wildcard must also be wildcards.
  
  Formatting should follow the "Standardized Number" formatting from the Dial plan. For example: +1317 for 317 numbers.

• ZONE NAME is a string used to associate a zone set zone with the phone number.  The zone name must match the name of a zone defined using the Zone Sets Container.

• There must be a tab character between the Phone Number and Zone Name fields.

Customers who create a custom data set must configure Dialer to use it. See Timezone Map Data for details.

Zones in the data set must be in the Zone Set too

When a custom zone map data set is used, the zone set assigned to the campaign must contain the same zones.  If the time zone field in the custom mapping file does not correspond to the zones in a Zone Set then the contacts will be dialed according to the Default Zone, making the time zone mapping useless.