Tradesly · Guide
Importing leads from a spreadsheet
Bring a reviewed CSV into Leads, with a preview before anything is imported.
A CSV import is useful when contact information already lives in another system or a spreadsheet. Import CSV brings reviewed rows into People so your team can find and inspect them in Leads.
Importing is not permission to contact someone, and it is not an outreach action. No call or text should be assumed merely because a row appears in the preview or is added to Leads.
1 Prepare the file first
Export only the fields your team actually needs. Remove unrelated notes, sensitive personal information, payment data, credentials, and columns whose meaning is unclear. Use a Phone column and the supported identity or contact fields shown in the sample file.
Keep the original consent evidence separately. The import attestation records an admin’s confirmation; it does not create, verify, or expand a recipient’s permission. A past transaction, old estimate, or earlier inquiry should not be treated as blanket permission for every channel, purpose, or calling technology.
If you cannot explain where a row came from and what permission covers it, leave it out until your compliance owner or counsel reviews it.
Importing a person again does not clear a Do not call status already attached to that lead. If the same lead appears in a new upload, the AI still will not call them. Verbal consent recorded with a ticket disposition also remains in the Ticket List.
2 The steps
Open Import CSV on the People tab.
From Leads, admins may need to switch from Call Lists to People first. Open the dialog titled “Import leads from CSV”.
Choose the reviewed file.
Use “Drop a spreadsheet here, or click to choose a file”. If you need the accepted layout, start with the sample spreadsheet rather than guessing at field names.
Read every preview count.
Review the ready, skipped, duplicate, and invalid rows. Open the source CSV and correct unexpected results there before continuing.
Confirm the company and permission basis.
In a multi-brand account, make sure you are importing into the intended company. Read the permission attestation and select it only if your business has the underlying records needed for these people and the intended contact use.
Select Import {n} lead(s), then Done.
Return to People and open a few imported leads to confirm the names, numbers, and notes landed as expected.
Choose outreach separately.
If an admin later creates a Call List, use Upload a list on the Call Lists tab and perform a new audience, consent, and readiness review before Start calling.
3 Treat the preview as a warning, not a verdict
Preview labels help you inspect the file, but they do not prove that two similar rows are the same person or that an existing record contains the right job context. After a large import, sample records with shared names, household numbers, or incomplete details before anyone reaches out.
Do not add invented columns in the hope that the AI will infer what they mean. Put the customer-facing facts your team needs into clearly named, supported fields, and keep internal or sensitive notes out of automated outreach.
Never re-upload a person to try to reset a contact restriction. A lead marked Do not call remains unavailable to AI calling across later lists.
4 If something looks wrong
Stop before importing another copy. Re-uploading a corrected file can leave your team with more rows to reconcile. Contact support with the import filename, approximate time, company, and a small number of lead identifiers. Avoid emailing the full CSV unless support provides an approved secure method.
Your leads in one place explains how to review imported people. Call Lists: dormant spreadsheets become revenue explains the separate outbound workflow.