Automatic time zone mapping examples
When a contact list is configured for automatic time zone mapping, the system evaluates the phone number and zip code column values to determine the compliant dialing time for each contact.
The table below shows how the system behaves when it evaluates a record containing two phone numbers and a zip code.
Zip code | Phone number 1 | Phone number 2 | Compliant dialing time |
---|---|---|---|
Could not map | Could not map | Could not map | 2:00 PM to 8:00 PM Eastern time (default) |
Could not map | Eastern time | Could not map | 2:00 PM to 8:00 PM Eastern time (default) |
Not available | Central time | Eastern time |
9:00 AM to 9:00 PM Eastern time or |
Mountain time | Central time | Eastern time | 10:00 AM to 9:00 PM Eastern time or 9:00 AM to 8:00 PM Central time or 8:00 AM to 7:00 PM Mountain time |
Not available | Could not map | Central time | 8:00 AM to 9:00 PM Central time |
Central time | Could not map | Central time | 8:00 AM to 9:00 PM Central time |
Central time | Central time | Central time | 8:00 AM to 9:00 PM Central time |
Central time | Could not map | Could not map | 2:00 PM to 8:00 PM Eastern time (default) or 1:00 PM to 7:00 PM Central time |
Not available | Central time | Central time | 8:00 AM to 9:00 PM Central time |
- Could not map (zip code) = The system could not map the zip code number column value because it is not a valid US zip code.
- Could not map (phone number) = The system could not map the phone number column value because it is not a valid NANP number.
- Not available = The contact list does not include a zip code column or the zip code column value for the contact is blank.
- The system stops dialing one minute before the end of the compliant dialing time to provide a buffer to complete record processing.
- Canadian area codes are fully supported. This includes Newfoundland and its 30 minute offset from UTC. For more information, see Outbound settings.