AI-generated summary
Genesys Cloud enables users to create contact lists by uploading records from input files in multiple formats, including comma-separated values (.csv) files, Excel files, and File Specification templates that support comma-separated, delimiter-separated, or fixed-length formats encoded in UTF-8. Contact list creation requires specific permissions across Outbound categories including Contact List, Import Template, File Specification Template, and Attempt Limits functions.
The system enforces operational limits on contact list structure and scale: header columns are limited to individual column entries to and contact lists to a maximum of 50 columns. Organizations can maintain up to 1,000 contact lists with a maximum of 5 million total contacts and 1 million contacts per individual list. Contact lists are created through the Digital and Telephony > Outbound > List Management menu, where users assign unique names, select divisions, and choose their preferred upload method. Genesys recommends excluding internal phone numbers belonging to organizational users or IVR lines from contact lists to prevent operational issues, call routing loops, and failed call attempts during outbound dialing campaigns.
When using import templates, users can configure data mapping and contact field options. A unique identifier column can be optionally selected to enable future data appending by matching incoming records to existing contacts using customer IDs or account numbers; without a unique identifier, the entire row serves as the primary key. Unique identifier columns are limited to and may only contain uppercase and lowercase letters, numbers, dashes, underscores, and asterisks—no spaces or special characters are permitted.
Contact lists support multiple communication channels: up to 10 phone number columns with configurable types (home, work, cell), up to 10 email address columns with types (personal, work), and WhatsApp Phone ID columns with corresponding type designations. Time zone configuration can be manually specified through a Time Zone Column selection or automatically determined via Automatic Time Zone Mapping, which is supported for North American area codes and postal codes when the organization is located in a North American AWS region. Attempt controls restrict calling attempts to specific contact records or phone numbers on a daily or total basis, applicable only to phone numbers rather than email addresses.
Preview mode columns allow selective preview dialing of specific contacts based on designated values, useful for flagging high-value contacts to prevent abandonment; this feature must be configured during initial contact list creation. For campaigns using Dynamic Queueing sorting, column data types must be specified, supporting Numeric (with Min/Max values), Text (with maximum character length up to combined), Timestamp (ISO format YYYY-MM-ddTHH:mmZ, dates between 1970-01-01 and 2038-01-19), and DateTime (ISO 8601 format accepting any valid date). Column data type specifications cannot be edited after saving; modifications require creating a new contact list.
Retention configuration is available at both contact list and contact levels when using templates. At the contact list level, administrators can configure the time zone for retention determination and select from three retention types: Never (no automatic deletion), Default Retention Days (deletion after 1-360 days from creation), or Today (deletion at midnight in the configured time zone). At the contact level, administrators specify retention type, retention days, and expiration date columns from imported files. The expiration date displays in UTC time zone and cannot be modified after saving. Time zone settings cannot be changed after the contact list is saved. CSV files must not contain blank rows to prevent import failures, and white space trimming from contact fields can be toggled during configuration. The system provides progress indicators during file uploads and displays completion messages upon successful import