DealSleek · How-to guidePreview

Import leads

11 steps, from “Where are the leads coming from?” to “Review before importing”, with what to enter at each one.

Audience: Administrator, Operator
Owner: DealSleek product documentation
Last reviewed: Oct 12, 2026
Reading time: 10 min

Steps

01
Where are the leads coming from?
Paste rows directly, or upload a CSV file.
Paste or uploadRequired
Paste is quickest for a short list; upload handles thousands of rows.
02
Paste your rows
Shown only when “Paste or upload” is Paste.
One lead per line. We will work out the columns next.
Your rowsRequired
Order does not matter — the value containing @ is treated as the email.
Column separatorRequired
Most exports use a comma. Check your file if the preview looks wrong.
First rowRequired
If the first row says "Email, First name", it is a header, not a lead.
03
Upload your file
Shown only when “Paste or upload” is File.
A .csv export from your list, CRM, or event platform.
CSV fileRequired
CSV only, up to 1,000 rows per import.
Column separatorRequired
Most exports use a comma. Check your file if the preview looks wrong.
First rowRequired
If the first row says "Email, First name", it is a header, not a lead.
04
Which column is which?
Email is required — a row without one cannot become a lead. The rest are optional.
Email columnRequired
The only required mapping. Rows with no email are reported, not imported.
First-name column
Last-name column
Company column
05
Why may we contact these people?
Every outbound action checks this before it sends. The import is refused without it.
Channels you have consent forRequired
Only the channels you can evidence. You can add more later.
Country the leads are inRequired
The stricter of the leads’ regime and yours applies.
Sub-region
Only needed where the rules split below the country, such as California.
Evidence referenceRequired
What you would show a regulator if asked.
06
What if we already have them?
Decide what happens when an imported row matches an existing lead.
When a row matches an existing leadRequired
Matched on email address within this workspace.
On merge, which values winRequired
Applies only to fields where both sides have a value.
07
What happens next?
Who owns these leads, and what the system should do with them once created.
Owner
Leave blank to route by your workspace rules instead.
Once created, these leads shouldRequired
Imported leads sit inert unless you choose otherwise.
08
Which sequence?
Shown only when “Once created, these leads should” is Enroll.
The outreach sequence these leads join immediately after import.
SequenceRequired
Enrolment respects the consent channels you recorded above.
09
What should wake them?
Shown only when “Once created, these leads should” is Cryo.
These leads park in cryo until this signal fires.
Wake signalRequired
Cryo leads consume no capacity until the signal fires.
10
Why are they disqualified?
Shown only when “Once created, these leads should” is Disqualify.
Recorded against every row so the cohort stays reportable.
BANT reasonRequired
Use this to import a known-dead list for suppression.
11
Review before importing
Nothing has been written yet. Check the counts, then commit.