Drop in a spreadsheet. It figures out the columns itself.
There's no template to download, no exact header names to match, and no import wizard to click through. Upload a campaign's worth of leads and the columns get detected automatically — here's exactly how, what's required, and what happens to a lead once it's in the queue.
▸ THE ONLY THING A LEAD ACTUALLY NEEDS
One field is required: a value with at least 10 digits once everything except numbers is stripped out. That's it. Any row without something matching that gets skipped on upload rather than silently corrupting your campaign — you'll get a count of exactly how many rows made it in.
Everything else — name, email, state, custom fields — is optional and additive. A file with nothing but a column of phone numbers is a valid upload.
▸ HOW COLUMN DETECTION ACTUALLY WORKS
The importer checks a list of common header spellings for each field, case-insensitive. If your file uses one of these, it gets mapped automatically — no manual field-matching step:
phone, Phone, phone_number, Phone Number, mobile, cell — or, if none of those match, the first column with at least 10 digits in it.first_name, First Name, firstname, first, namelast_name, Last Name, lastname, lastemail, Emailstate, Stateconsent_date, consent date, consentdateconsent_source, consent sourceconsent_description, consent text, consent_textconsent_proof_url, consent_proof, proof_urlAnything in your file that doesn't match a recognized header isn't discarded — it's kept on the lead record as extra data, so custom columns specific to your business (policy type, property value, whatever you track) survive the import even without a dedicated field.
▸ THE CONSENT COLUMNS ARE OPTIONAL BUT WORTH USING
If your leads come with documented consent — a web form opt-in, a signed agreement, a call recording where consent was given — the four consent columns above let you attach that proof directly to each lead at upload time: when consent was given, where it came from, what it said, and a link to supporting documentation.
None of this is required to dial a lead. But if a consent dispute ever comes up, having the record attached to the lead itself — rather than buried in a separate spreadsheet somewhere — is the difference between answering the question in thirty seconds and not being able to answer it at all. See how we keep compliance for the fuller picture of what DialerSeat enforces automatically versus what depends on records like these.
▸ WHAT HAPPENS TO A LEAD AFTER IT'S UPLOADED
A lead isn't just dialed once and forgotten if nobody answers. There's a built-in retry cycle before a lead gets set aside for good:
UNCALLED
Fresh in the queue, never dialed. This is every lead's starting status right after upload.
NO ANSWER / SKIPPED
Dialed but not connected, or manually skipped by the agent. Goes back into the queue automatically — up to 3 total attempts.
MAXED
Hit 3 attempts without a connection. Removed from the active dial queue so agents stop wasting time on it, but the record and history stay intact — nothing is deleted.
CALLED / APPOINTMENT / CLOSED / DNC
Set by whatever disposition the agent selects after a connected call. A “Do Not Call” disposition removes the lead from future dialing immediately, campaign-wide.
Every attempt is timestamped and logged against the lead, so a manager reviewing a campaign can see exactly how many times a given number was tried and what happened each time — not just the final outcome.
▸ A FEW PRACTICAL NOTES
- Duplicate phone numbers aren't rejected at upload — if your source data has the same number twice, both rows come in. Clean lists in are clean lists dialed; the importer won't catch what your source data doesn't already handle.
- Every upload is scoped to one campaign. There's no “global” lead pool shared across campaigns — leads live where you put them.
- Uploads are additive, not a replace. Running a second upload into a campaign that already has leads adds to the existing list rather than overwriting it.
- DNC scrubbing against the national registry is still on you before upload — the importer accepts what you give it. See how we keep compliance for the full split of what's enforced automatically versus what's the seller's responsibility.
One practical tip — if a file has a column named something unexpected — say Telephone instead of Phone — the fallback detection (first column with 10+ digits) usually catches it anyway, but the safest move is renaming your phone column to one of the recognized headers above before uploading, especially on large files where you want to be certain every row mapped correctly.
$35/week. Unlimited leads uploaded, no per-record fee.
Sign up, create a campaign, and drop in a spreadsheet — no template, no import wizard.
GET STARTED →