PhoneBurner batch enrichment — overnight files, ranked phones, one import

PhoneBurner operators often work in batches: hundreds or thousands of accounts queued for a calling block, with a CSV that must match PhoneBurner's import expectations before reps open the dialer. The bottleneck is rarely "find more leads." It is fill thin phone columns with lines that reach a decision maker, not another main number that dies in voicemail.

411data fits that batch mental model. You upload a file you already have rights to work, enrich overnight, reshape the output to your PhoneBurner template, and import once. We do not sell new leads, and we do not scrub DNC or litigator lists — handle compliance in your existing PhoneBurner or agency workflow.

Why batch + export beats one-off lookups

Append vendors optimized for per-lookup price usually return one phone field — often the switchboard. PhoneBurner wants a row-shaped record: identifiers, company, contact name, one or more dial positions, sometimes email for parallel nurture.

411data's unit is a fully enriched row with ranked phones, contacts, and summary fields. Custom Export Builder then projects that graph into your PhoneBurner column names — Phone, Phone2, custom headers — without a manual Excel reformat. Ranking puts owner and officer cells ahead of reception; legal lines stay out of dial slots (decision-maker phones).

Workflow

1. Upload the source file

Use /batch for the UI path or POST /api/v1/batch/enrich/upload for automation (batch CSV enrich). PhoneBurner users often start from:

• A purchased or client-owned marketing list
• A CRM export with stale or single-line phone data
• A prior PhoneBurner export you are re-hydrating before a recycle pass

Any reasonable delimiter and header shape is accepted. Link anonymous uploads to your agent bearer before starting paid processing.

2. Start enrichment (bill-on-match)

Connect for a bearer if you need one (quickstart). Batch start requires sufficient virtual balance; unmatched rows auto-credit when enrichment cannot fill the row — you are not charged for misses.

Large files can pause when balance runs low; resume after topping up via the batch UI or API without re-uploading the source CSV.

3. Define the PhoneBurner import profile

PhoneBurner import specs vary by account and integration. Do not guess column names:

1. Paste a known-good PhoneBurner import row into Export Builder derive.
2. Create a profile with column hints: e.g. primary dial position = "phone most likely to reach the owner", secondary = "next ranked line, never legal counsel."
3. Turn on dm_phone_rank in profile settings.
4. Run estimate with the same file_instructions you will use on the full run.
5. Preview 3–5 rows, fix hints if a column maps wrong, then POST the full export run.
6. Download CSV from GET …/download.csv and import into PhoneBurner.

Rebuild exports against the same mapping hash are free — useful when you tweak passthrough columns but keep dial mapping stable.

4. Scale with API keys

High-volume shops should read /developers and mint scoped keys for upload → start → export → download. Connect wizards documents the /connect?action=usage-keys path for operators who delegate batch runs without sharing the admin bearer.

What we do not promise

• No "TCPA-compliant leads." You bring the list; we enrich contact fields.
• No National DNC guarantee. Scrub in PhoneBurner or your compliance vendor if required.
• No invented performance stats. Match yield depends on your file; we do not publish universal match-rate headlines.

PhoneBurner batch calling works best when the first number on each row is worth dialing. Upload what you own, enrich with ranking, export in your import shape — reach the decision maker, not the switchboard.