Aircall lead enrichment — ranked phones for contact import

Aircall power-dials the contacts you load — CRM exports, agency client files, or a spreadsheet your team already curates. The gap is rarely "we need more accounts." It is thin phone columns: one main line, blank mobile fields, numbers that route to reception instead of the person who signs.

411data enriches lists you already own. We are not a list broker, and we do not sell opt-in lead packages. We also do not scrub National DNC or litigator lists — if your compliance program requires those checks, run them in Aircall, your CRM, or a dedicated hygiene vendor before or after enrichment.

Minimum inputs: name and address

Batch enrichment needs enough signal to match an account. For most files that means company name plus a postal address (street, city, state, ZIP). Optional columns — CRM contact id, email, existing phone, industry tags — ride through as passthrough fields so your Aircall import can round-trip the same record.

Thin exports still work when the address cell is stacked or headers are non-standard; /batch normalizes ingress quirks (batch CSV enrich). Without at least name-and-location anchors, match yield drops — we bill on what we actually fill, not on misses.

Ranked decision-maker phones

After a match, 411data returns a lead graph: officers, owners, titles, and multiple phone candidates. Ranking promotes mobile and officer lines ahead of switchboards and demotes legal and registered-agent numbers from dial positions (decision-maker phones).

Enable dm_phone_rank in your export profile so the mapper sees candidates in dial order — best line first, sensible fallbacks second — instead of a random pile of numbers.

Map to Aircall import columns with Export Builder

Aircall contact imports accept CSV with headers your workspace defines — first name, last name, company, primary phone, email, custom attributes. There is no single canonical "Aircall template" baked into 411data; that is intentional.

Custom Export Builder learns your schema from a sample row:

1. Paste a known-good Aircall import line (or header list) into derive columns.
2. Save profile hints: e.g. "best decision-maker phone in Phone", "company name passthrough from source", "officer mobile in a secondary phone custom field if present."
3. Turn on dm_phone_rank in profile settings.
4. Estimate with the same instructions you will run in production, then preview a handful of rows.
5. Run the full export, download CSV, and import through Aircall's contact upload (or push enriched phone fields upstream if your CRM syncs into Aircall).

Stock passthrough paths from the enriched graph are listed via GET /api/v1/export/columns/stock or the /batch/{id}/export UI — useful when Aircall needs both ranked phones and enriched DM title fields on the same row.

Bill-on-match pricing

Mint a bearer if needed (quickstart), upload your file, and start the batch job. Bill-on-match means unmatched rows auto-credit — you are not charged for blanks. Large files can pause when virtual balance runs low; resume after topping up without re-uploading the source CSV.

Agencies running the same client schema weekly should save the export profile once and re-run against new batch ids. For automation, read /developers and mint scoped usage keys so operators can upload → enrich → export without sharing the admin bearer (Connect wizards).

Honest limits

• No "TCPA-compliant leads." You bring the list; calling compliance is your process and counsel.
• No DNC or litigator guarantee. Scrub elsewhere if your workflow requires it.
• No invented match-rate headlines. Yield varies by file quality and industry.
• No fixed Aircall template in the product. If import fails, compare headers character-for-character with a row you know works — derive → preview → adjust hints is the intended loop.

Better Aircall sessions start with the right phone first. Export what you own, enrich with ranking, import a CSV shaped for how your team already dials — reach the decision maker, not the switchboard.