When you upload a lead list to a CSV Lead Source in Entrovox, your AI voice agent immediately validates the records, applies TCPA calling-window rules and DNC screening, and queues the leads for outbound calling. When the AI reaches an interested lead, it warm-transfers the live call directly to a licensed agent at your agency.
This guide details the required column headers, accepted field synonyms, data formatting standards, and custom metadata handling so your uploads process smoothly without manual data cleaning.
- Phone number (valid 10-digit US)
- First & last name (or full name)
- State (strongly recommended for TCPA)
1. Required columns
Every imported CSV must contain contact information for each lead. Header matching in Entrovox is case-insensitive, forgiving of spaces and separators, and independent of column order.
| Canonical field | Accepted column headers | Description & validation |
|---|---|---|
| Phone number | Phone, Phone Number, Phone No, Mobile, Mobile Number, Cell, Cell Phone, Primary Phone, Phone - Main | 10-digit US number or standard E.164. Punctuation, dashes, spaces, and leading country code (+1) are stripped automatically. Rows missing a dialable phone are skipped. |
| First name | First Name, FirstName, First, FName, Given Name, Contact First Name, Lead First Name | The lead’s given name. Used by the AI to address the caller naturally. Names formatted in ALL CAPS are automatically title-cased. |
| Last name | Last Name, LastName, Last, LName, Surname, Family Name, Contact Last Name | The lead’s surname. |
If your CRM exports a single combined name column (e.g. Full Name or FullName), Entrovox automatically splits it into First and Last names. Both “Jane Smith” and “Smith, Jane” conventions are parsed. For names with suffixes (Jr., Sr., III), using separate First Name and Last Name columns is recommended: in comma-form names like “Smith, Jane Jr.”, trailing suffixes are retained with the given name rather than isolated into the surname.
2. Optional & recommended columns
Adding these columns provides rich conversational context to the AI and enables accurate timezone mapping for federal TCPA calling windows:
| Field | Accepted headers | Function & values |
|---|---|---|
| State(Highly recommended) | State, ST, State Code | 2-letter state abbreviation (e.g., TX, CA, FL) or full name. Entrovox maps the state to the lead’s local timezone to evaluate the federal TCPA calling window (8:00 AM – 9:00 PM local time). |
| Timezone(Split-zone states) | Timezone, Time Zone, TZ | Standard IANA timezone identifier (e.g., America/Denver, America/Chicago, America/New_York, America/Los_Angeles, America/Phoenix). Recommended for leads in minority-zone portions of split states (such as El Paso, TX in Mountain Time) to ensure exact local calling windows. Values must follow standard IANA naming; abbreviations (such as Mountain or CST) cannot be parsed by the dialer and cause the lead to be held. |
| Type of insurance | Line of Business, LOB, Type of Insurance, Insurance Type, Product, Coverage | Stored on the lead record (e.g. auto, home, home_auto, life, health, medicare, or final_expense). Note that the conversational line quoted during calls is determined by your lead source and the AI’s configuration, not by this per-row CSV value. |
| Email, Email Address, E-Mail, Contact Email | Stored with the contact record for follow-ups and CRM sync. | |
| Zip code | Zip, Zip Code, Zipcode, Postal Code | 5-digit US postal code (e.g., 75001). |
| Preferred language | Language, Preferred Language, Lang | If set to Spanish, es, or español, the AI opens in Spanish provided your agency has Spanish enabled, a multilingual voice model, and a Spanish opening line configured. If any prerequisite is missing, the AI defaults to English. |
| Lead created date | Created At, Date Created, Lead Date, Date Added, Submitted Date | When the vendor generated the lead. Supports ISO 8601 (2026-10-09 14:30:00) and standard US formats (10/09/2026 2:30 PM). Dates older than 5 years or more than 2 days in the future are preserved as raw metadata and fall back to import-time ordering. |
| Alternate phone | Phone Alt, Alt Phone, Secondary Phone, Phone 2, Mobile 2 | Secondary phone number attached to the lead record. |
3. Compliance & TCPA calling windows
Federal regulations prohibit outbound calls outside legally permitted hours. Because your agency certifies express consent prior to activating any lead source, Entrovox evaluates outbound dials against the federal TCPA calling window of 8:00 AM to 9:00 PM in the lead’s local timezone (all days, honoring the 10 configured federal holidays). State-level telemarketing statutes governing unsolicited cold outreach do not apply to consented leads.
Entrovox maps the lead’s State column to its predominant timezone by population (e.g. Central for Texas, Eastern for Florida). For leads in split-zone states with minority timezones (such as El Paso, TX in Mountain time or the Florida Panhandle in Central time), provide an explicit Timezone column using valid IANA identifiers (e.g., America/Denver) to prevent a one-hour scheduling offset. Non-standard values or abbreviations (such as Mountain or CST) cannot be parsed and will suppress dialing. If neither state nor timezone is provided, the platform falls back to your agency’s organization timezone — which risks dialing after hours if a lead lives in a timezone east of your agency.
4. Custom columns & metadata
Does your lead provider include extra fields like Current Carrier, Vehicle Make/Model, or Year Built?
You do not need to delete or reformat them. Any column not mapped to a canonical field is automatically preserved as raw custom metadata on the lead record in the database without failing validation or import.
5. Example CSV template
Below is a sample CSV layout. The first row must contain column headers, followed by lead data rows:
First Name,Last Name,Phone,State,Type of Insurance,Preferred Language,Email,Zip Code,Notes Jane,Smith,(555) 234-5678,TX,Auto,English,[email protected],75001,Clean driving record John,Doe,555-876-5432,FL,Home,English,[email protected],33101,Single family home Carlos,Rodriguez,+15553456789,CA,Auto,Spanish,[email protected],90210,Prefers Spanish
6. Encoding & file format rules
- File extension: Standard
.csvformat. - Encoding: UTF-8, UTF-8 with BOM, Latin-1, or Windows-1252 (CP1252). Standard spreadsheet exports from Microsoft Excel, Apple Numbers, and Google Sheets work without modification.
- Capitalization: Names formatted in ALL CAPS (
JOHN SMITH) are automatically converted to title case so text-to-speech models do not spell names letter-by-letter. - Duplicate detection: Leads are evaluated against your agency’s deduplication rules and internal Do-Not-Call (DNC) list prior to dialing.
When uploading to a dedicated Cross-Sell Lead Source (account rounding), campaigns strictly support the home and auto lines. You must provide an Owned Line of Business (e.g. Auto). An optional Target Line of Business (e.g. Home) may also be supplied; if omitted, the reciprocal line is automatically inferred.
Important: Other lines of business (such as life, health, Medicare, or final expense) are not supported for cross-sell campaigns. Any row where the owned line is outside home/auto is automatically skipped during import. To ensure the AI pitches the intended coverage, target lines must specify only home or auto; unmapped target lines fall back to the reciprocal line rather than skipping the record.