Kixie CSV enrichment — map ranked phones into your dialer import

Kixie sits on top of the list you already feed it — CRM exports, purchased files, or agency client deliverables. Most teams do not need another database search. They need better numbers in the columns Kixie's import and power-list workflows expect, with the best decision-maker line first so reps skip the 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 Kixie, your CRM, or a dedicated hygiene vendor before or after enrichment.

The shape of a Kixie-ready file

Kixie deployments differ: some teams import a minimal two-column phone + name sheet; others carry CRM ids, company, email, and custom dispositions. There is no single canonical "Kixie 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 Phone Number", "company passthrough from source file"). Enable dm_phone_rank so ranked candidates arrive before the mapper fills dial positions (ranking details).

End-to-end workflow

1. Start from your source export

Pull the CSV your team already uses before Kixie — Salesforce, HubSpot, a purchased append, or a GoHighLevel dump. 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.

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 Kixie import with Export Builder

1. Derive destination columns from a real Kixie 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 Kixie (or push through your existing CRM → Kixie sync if you only replace the 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 Kixie needs both ranked phones and enriched DM title fields.

4. Automate repeat files

Agencies running the same client 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

• No TCPA-compliant lead marketing. We surface contact data on accounts you bring; calling compliance is yours.
• No fabricated match-rate headlines. Yield varies by file and industry.
• No fixed Kixie template in the product. If your import fails, compare headers character-for-character with a known-good row — Export Builder is built for that iteration loop (derive → preview → adjust hints).

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