Close CRM lead enrichment — ranked phones before import or on existing leads

Close combines CRM and dialer in one workspace — Smart Views, sequences, and power dialing on the same lead record. Most teams already own the account list: a client file, a territory export, or leads in Close with a thin phone field and nothing worth dialing in mobile. The friction is getting owner and officer cell lines into the phone columns Close's dialer uses, instead of a main line that rings reception.

411data enriches lists you already have permission to work. We are not a list broker, and we do not scrub National DNC or litigator lists — run those in Close, your agency stack, or a dedicated hygiene vendor if your process requires them.

Two workflows that fit Close

Import-first. You have a customer or purchased file that has not landed in Close yet. Enrich it on 411data, shape the CSV to Close's import headers, then bulk-import leads with ranked phones already in place.

Refresh-in-place. Leads already live in Close but phone data is stale. Export a Smart View to CSV, enrich on 411data, and reimport with lead id passthrough so Close updates the same records instead of creating duplicates.

Both paths use the same batch engine and Export Builder profile; only the source export and passthrough columns differ.

Minimum inputs: business name and address

411data matches on company identity, not a Close lead id. Each row needs a business name and a mailing or street address (city and state help when the file is sparse). Optional columns — Close lead_id, custom fields — ride through as passthrough bindings for round-trip import.

Upload via /batch or the API (batch CSV enrich). Ingress normalizes mixed delimiters and vendor header quirks; you link the upload to your agent bearer before starting paid processing.

Batch enrich with decision-maker ranking

Mint a bearer if you need one (quickstart), then start the batch job. Billing is bill-on-match: rows we cannot fill auto-credit. You are not charged for empty matches.

After enrichment, phones are scored before they reach your export — owner and officer mobiles promoted, switchboards and reception demoted, attorney and registered-agent lines excluded from ranked dial slots (how ranking works). Enable dm_phone_rank in your export profile so the mapper receives a deterministically ordered candidate list per lead.

Map to Close import columns with Export Builder

Close import layouts vary by workspace. There is no fixed Close template in 411data. Custom Export Builder learns your columns from a pasted sample row:

Export one known-good Close lead (or paste headers from Close's import guide) into derive columns.
Save profile hints: e.g. "best decision-maker line in phone", "second-ranked mobile in mobile_phone if present."
Bind Close lead_id (or equivalent) from source for refresh workflows; bind enriched DM name and title from the lead graph.
Estimate → preview 3–5 rows → run the full export.

Download the CSV and import through Close's lead import. Reps opening the dialer from Smart Views see ranked lines in the fields they already use.

Automate repeat files

Agencies running the same Close schema weekly should store the export profile once and re-run against new batch ids. The developer guide documents HTTP routes; scoped usage keys let automation run enrich + export without the admin bearer (Connect hub recipe).

What we do not claim

No TCPA-compliant lead labels. Compliance with calling rules is your process and counsel.
No guaranteed match rate. Yield depends on your file; unmatched rows credit back under bill-on-match rules.
No invented stats. We do not publish flat match-rate headlines.

Reach the decision maker, not the switchboard — enrich what you own, import a file shaped for how your team actually dials in Close.