Five9 CSV enrichment — ranked phones into your list import

Five9 runs on the lists your team already loads — CRM exports, agency client files, purchased marketing data. The dialer does not fix thin phone columns. Reps still hit reception, voicemail trees, and wrong desks when the first number on each row is a switchboard.

411data enriches accounts you already own. We are not a list broker, and we do not provide DNC or litigator scrubbing — if your compliance program requires those checks, run them in Five9, your CRM, or a dedicated hygiene vendor before or after enrichment.

The shape of a Five9-ready file

Five9 deployments vary: some teams import a minimal phone + name sheet; others carry CRM ids, company, address, email, and custom fields for campaign routing. There is no single canonical "Five9 CSV" baked into 411data.

That is intentional. Custom Export Builder maps enriched rows into your schema — you paste a sample import row, derive column names, and write per-column hints ("best DM phone in number1", "company passthrough from source file"). Enable dm_phone_rank so ranked candidates arrive before the mapper fills dial positions (ranking details).

At minimum, enrichment needs enough to match the account: business name and address (street, city, state, ZIP). More identifiers help — website, phone on file, CRM keys as passthrough — but name plus location is the floor most files already carry.

End-to-end workflow

1. Start from your source export

Pull the CSV your team already uses before Five9 — Salesforce, HubSpot, a purchased append, or an agency deliverable. Upload via /batch (batch CSV enrich).

Header mapping tolerates vendor quirks: utility exports, mixed delimiters, and stacked company/address cells are normalized at ingress. Optional contact_id or CRM keys should ride as passthrough columns for round-trip matching after you re-import into Five9.

2. Enrich with bill-on-match pricing

Mint a bearer if needed (quickstart), then start the batch job. Bill-on-match means unmatched rows auto-credit — you are not paying for blanks.

After enrichment, phones are scored: owner and officer mobiles promoted, switchboards and reception demoted, legal and counsel lines excluded from ranked dial lists.

3. Build the Five9 import with Export Builder

  1. Derive destination columns from a real Five9 list import template or a row you know works.
  2. Save profile instructions: e.g. "Never place an attorney line in a dial column; leave empty rather than guess."
  3. Estimate cost with the same instructions you will submit (Export Builder recipe).
  4. Preview a handful of rows, then run the full export and download CSV.
  5. Import into Five9 as a new or updated calling list (or push through your existing CRM → Five9 sync if you only replace phone fields upstream).

Stock passthrough paths from the enriched graph are discoverable via GET /api/v1/export/columns/stock or the /batch/{id}/export UI dropdown — useful when Five9 needs both ranked phones and enriched DM title fields alongside your original CRM columns.

4. Automate repeat files

Teams running the same Five9 schema weekly should store the export profile once and re-run against new batch ids. The developer guide documents HTTP routes; usage keys scope automation without sharing the admin token (Connect wizards).

Honest limits

Better Five9 sessions start with the right phone first. Export what you own, enrich with ranking, import a file that matches how your team already works.