Bring in your leads

Four ways to get people into LeadBind.

Your lead form

The main one. A form on your site posts to LeadBind, the lead appears, and speed to lead calls them within seconds.

You need two things on that form:

• Name and phone, at minimum
• Consent language saying they agree to be contacted about their request, including by automated calls and texts

That second one is not decoration. It is your evidence if you are ever challenged, and carriers ask to see it when you register for texting. Screenshot your form today. See Consent and opt-outs.

CSV import

For a list you already have, or a whole book you are moving off another CRM. Upload the file, check the column mapping, import. Everything in one upload lands in a single named list, so you can work it, dial it, or hand it to your reps as a batch.

Before you import anything:

• Do you have permission to contact these people? Where did the list come from? If the honest answer is "I bought it" or "we scraped it," do not import it into a system that will start dialing. See Consent.
• Set the source. "March home show" is worth knowing later. A blank source is a lead you can never evaluate.
• Do not re-import an old list to get around an opt-out. The suppression list will block the send, which is correct, but do not build a workflow on it.

Up to 20,000 rows per upload.

The columns it recognizes

Headers are matched without regard to case or spacing. A header LeadBind does not recognize is still kept, under your own spelling, so nothing in the file is thrown away.

What it becomes	Headers accepted
Name	name, full name, fullname, lead name, contact, contact name, or first name plus last name
Phone	phone, phone number, mobile, cell, cell phone, number, primary phone, phone1
Email	email, email address, e-mail
State	state, st, state code
Address	address, street address, address 1, address line 1, street
City	city, town
Zip	zip, zip code, postal, postal code, postcode
Vendor	vendor, lead vendor, source vendor, list vendor
Source	source, lead source, campaign
Lead date	lead date, date of lead, date received, received, received on, date
Age	age, or worked out from dob, date of birth, birthdate, birthday
Beneficiary	beneficiary, bene, beneficiary name
Do not call	dnc, do not call, donotcall, dnc flag
Notes	notes, note, comments, comment, remarks

Address, city, state, and zip are also composed into one address on the lead, which is what puts an imported lead on the door-knocking map.

Bringing a book over from another CRM

An export from a CRM you are leaving carries more than contact details. It carries the work: what stage each lead reached, how many times it was dialed, when it was last dialed, and which rep owns it. Those columns are read too, so a migrated book arrives with its history instead of arriving as a wall of brand-new leads.

What it becomes	Headers accepted
Stage	status, lead status, ringy status
Times called	num times called, number of times called, times called, call count, calls made
Last called	last called, last call, last called at, last contacted, last call date
Assigned rep	assigned to, belongs to, assigned agent, assigned rep
Carrier	carrier, insurance carrier, carrier name
Policy number	policy number, policy no, policy #, policy id
Premium	premium, monthly premium, premium amount
Sale amount	sale amount, sales amount, sale
Military	military, military status, veteran, veteran status

Status becomes a stage through a fixed table, not a guess:

Stage	Statuses that land there
New	new, new lead, fresh, unworked, not contacted
Contacted	contacted, attempted, attempted contact, working, in progress, no answer, left message, left voicemail, voicemail, follow up, nurture
Callback	call back, callback, call back scheduled, scheduled callback, recall
Hot	hot, hot lead, interested, quoted, quote sent, application started, pending application
Booked	appointment, appointment set, appt set, booked, scheduled
Sold	sold, closed, closed won, won, client, customer, issued, policy issued
Lost	lost, closed lost, not interested, dead, dead lead, disqualified, unqualified, bad lead, bad number, wrong number, do not call, dnc, declined, not qualified

Punctuation and capitalization do not matter, so Call Back, call-back, and CALLBACK all land in the same place.

Most CRMs let you invent your own statuses, so this table can never be complete. A status LeadBind does not recognize lands in New, keeps its original value on the lead, and is reported as unmapped in the import result. It is not silently guessed at.

Times called fills the attempt counter the dialer and the automations read, so a migrated lead is not dialed from zero again and still respects your attempt cap. A cell with no digits in it, like n/a or a dash, leaves the counter empty rather than setting it to zero.

Last called reads month-first US dates: 9/4/2026, 09-04-26, 2026-09-04, with an optional time and an optional AM or PM. A date it cannot read with certainty is left blank rather than guessed, because 04/09 is April 9th to one exporter and September 4th to another.

Assigned to and Belongs to are matched against the people in your own organization, by email or by full name. A cell that matches nobody, matches more than one person, or names somebody outside your org leaves that lead unassigned and is counted in the import result. A solo account has no roster to match against, so every assignee cell counts as unmatched.

Carrier, policy number, premium, sale amount, and military are stored under fixed names so the same field is findable on every import, no matter how that export spelled the header.

What the import result tells you

The panel after an import reads "mapped on 812 of 900 rows" per field, and only for the columns your file actually carried. That is deliberate. A field reported as mapped on 812 of 900 rows tells you 88 rows carried something LeadBind could not place, which is a real thing to go and look at. A single percentage would hide it, and a field your file never had says nothing at all rather than showing a zero that reads like a failure.

If you own or manage an organization, Distribute to reps is on that same panel. See Lead routing.

Duplicates

Leads are deduplicated against your existing book by phone, on the last ten digits. A row that matches a lead you already have does not create a second one: the existing lead has its details refreshed from the file and joins the new list. Repeat rows inside the same file are caught too, and the first one wins.

Rows with no phone are matched by email, then by name.

Webhook

For any system that can post JSON. Point it at your LeadBind lead webhook and leads arrive in real time, exactly like a form.

This is how you connect a landing page builder, an ad platform's lead form, or a tool nobody has heard of.

CRM sync

If you run another CRM, keep it and push leads over. LeadBind runs the phone, the calendar, and the follow-up; it does not need to be your system of record.

After they arrive

Whichever route, the lead behaves the same:

1. It lands in Leads with its source
2. Speed to lead calls, if it is on and inside your calling hours
3. The assistant qualifies and books
4. Follow-up works the ones who did not answer

Common problems

Leads not arriving. Test your form yourself. If nothing lands in Leads, the form is not connected.

No source on any lead. Whatever feeds them is not sending it. Fix it now; you cannot backfill.

Duplicates. Someone filled out two forms, or a list was imported twice. Merge them, or two sequences reach the same person.

Imported leads not being called. Speed to lead may be scoped to specific sources, or it is off, or you are outside the calling window.

Everything imported as New. Your status column is not one of the headers above, or your statuses are ones LeadBind does not recognize. The import result says which. The original values are still on the leads.

Nobody owns the imported leads. The names in your assignee column did not match anyone in your organization. Match them by email instead of name, or distribute the list once it is in.

More in Troubleshooting.