Uploading leads
Create a whole list of leads at once from a CSV
Upload a CSV and create the whole list in one go. Each row carries its own lead type, so one file can hold a mix of them.
Upload a file
- Open Sales and go to the Leads step.
- Click New Lead and switch to Upload.
- Choose who the batch is assigned to. Leave it on Unassigned to send them to the agency's pool, where they are handed out from distribution.
- Check the TCPA box if the people in the file consented to automated texting.
- Click Choose file, pick your CSV, and review the preview. It shows how many rows are valid and lists any that will be skipped.
- Click Import.
The file
One format, with these columns. Extra columns are ignored.
| Column | Format | Required |
|---|---|---|
type | A lead type value | ✓ |
first_name | Text | ✓ |
last_name | Text | ✓ |
phone | +16025551188 | ✓ |
state | AZ | ✓ |
email | name@example.com | |
address | Text | |
city | Text | |
postal_code | 85201 | |
language | en | |
sex | male | |
spouse_first_name | Text | |
spouse_last_name | Text | |
sourced_at | Date or timestamp | |
tcpa_date | Date or timestamp |
type decides which presentation deck the lead gets and which bucket it counts under on the WAR and reports. There is a value for each type, like fwk for a Free Will Kit lead and fe for a Final Expense one. Lead types has the full list.
state has to be where the lead lives, not where you are, because it sets the products and rates in the presentation. Either AZ or Arizona is read.
phone is read whether the file writes it as +16025551188, 6025551188 or (602) 555-1188, as long as it is a real US number.
language is en, es or fr. Left blank, it is English.
sex is male or female. It carries into the presentation, where the Final Expense rates are priced off it.
spouse_first_name and spouse_last_name put a spouse on the household, so the presentation opens with both names already on it.
sourced_at is when the lead was generated by whoever supplied it. It is what the Age column on the Assign tab counts from, so a list you bought two months ago reads as two months old rather than as new. Left blank, the lead is stored with no sourced date and its age counts from the upload instead.
Both date columns take either a date on its own or a date and a time:
| You write | It is read as |
|---|---|
2026-09-14 | Midnight on the 14th, your time |
9/14/2026 | The same, in US month-first order |
2026-09-14 09:30 | 9:30 that morning, your time |
2026-09-14T09:30:00-07:00 | 9:30 Arizona time, whatever time it is where you are |
A date on its own is anchored to midnight where you are, not midnight UTC, so a lead sourced on the 14th never reads as the 13th.
tcpa_date is when consent was given, for a file that came with it. Left blank, the TCPA box you checked is recorded against the moment you upload.
type,first_name,last_name,phone,state,email,address,city,postal_code,language,sex,spouse_first_name,spouse_last_name,sourced_at,tcpa_date
fe,Marcus,Webb,+16025551188,AZ,marcus.webb@example.com,412 W Palm Ln,Mesa,85201,en,male,Lorene,Webb,2026-09-14,2026-09-14
fwk,Dana,Ortiz,+17025550142,NV,dortiz@example.com,,Henderson,89011,en,female,,,2026-09-14,
csk,Priya,Raman,+14805550117,AZ,,2240 S Cooper Rd,Chandler,,,,,,,
globe,Sam,Coleman,+12145550193,TX,scoleman@example.com,,,,es,male,,,2026-08-02,After an upload
When the import finishes you get a summary of how many leads were created, how many were flagged, and how many could not be imported.
A row is flagged as a possible duplicate when it matches a lead already in the CRM by phone, by email, or by first name, last name and state together. Flagged leads are still created. Open one and answer the review with Not duplicate or Confirm duplicate; until that is answered, the review is the only thing the lead offers and no automation will start on it.
Rows that could not be imported are the ones named in the preview: a missing required field, a lead type that is not one of the lead type values, a state or phone number that cannot be read, a language or sex outside the values above, or a date that is not readable.