Leads & Import
Build lead lists, import from CSV, Excel, or JSON with dedupe, suppression and address checks, and attest your list source
Cold Outreach works from lead lists, prospects you intend to contact cold. A lead is its own record, with its own list, status and sending history. When the person importing can create CRM records, an import also adds each lead to your CRM as a person, with their company, and links the two (see Adding leads to your CRM below). That person is added with marketing consent pending: a cold list is not consent, so no marketing campaign that needs confirmed consent reaches them until someone confirms it. You can also promote a lead by hand when they reply (see Cold Replies in Your Inbox).
One lead, as many lists as you like. An email address is a single lead in your organization, whichever list you first met it in, and that one lead can sit in any number of lists at once. Putting it in a second list is not a copy: the same lead, with the same history, status and personalization fields, is in both, and editing it in one place edits it everywhere. Taking it out of one list leaves it in the others. Deleting a lead is the one action that is not per list: it deletes the lead everywhere and cancels any pending sends, which is why the confirmation says so.
From the Leads tab, choose Import and upload a file. We accept CSV, Excel (.xlsx), and JSON, up to 25,000 rows.
File structure. One row per person. The only column we need is their email address, and a file can hold up to 25,000 rows. Here is what we look for, and the column headings we recognize for each. Capitalisation and spacing do not matter, and you confirm every match on the next step.
| Field | Description |
|---|---|
| Email address* | email, email address, work email, contact email |
| First name | first name, first_name, fname, given name |
| Last name | last name, last_name, surname, family name |
| Company | company, company name, organization, account, employer |
| Job title | title, job title, position, role |
| Country | country, country code, country ISO. Two letters, like US or GB. |
| Time zone | time zone, timezone, tz, iana timezone. ET, Central, PST, GMT+1 or a name like America/New_York. No time zone column? A State or Province column is used for United States and Canada leads. |
| State or province | state, province, state or province, person state. A US state or a Canadian province, as a code or a name. It sets the time zone when there is no time zone column. |
Any other column is saved as a personalization field. An industry column becomes {{industry}}, ready to drop into your emails. Nothing in your file is thrown away. The upload step has a downloadable sample file with two example rows and every column we recognize. One column is kept apart: an Email Status column, as a lead source tool writes it, is saved on the lead as its Source status, a record of what your source said that is never treated as an address check and never offered as a personalization field. The lead panel shows it under the email address, for example Source status: Verified (import). The Map step still lists that column as a custom variable: keep the name it suggests and the lead stores the value as its source status. A column you rename there stays a personalization field.
Naming a personalization field. On the Map step, any column you send to Custom variable gets a Variable name you write however you like, spaces and capitals included. We show the variable it becomes right underneath, so “Company size” reads as {{company_size}} in your emails. The name is what you see in the Variables menu when you write a step. The variable is what we replace with the lead’s value when the email goes out. Import the same spreadsheet again later and the names you chose come back, because we remember each name with its variable.
Two columns cannot quietly become one. If two columns would end up as the same variable, the Map step names both of them and the variable they would share. It asks you to give one a different name. Two columns pointed at the same built-in field are called out the same way, with the fix that applies there: skip one, or send it to a custom variable instead. And a column set to Custom variable with no name yet is named back to you and blocks the step until you either name it or skip it. Nothing is dropped on your behalf.
Adding leads to your CRM. On the Map step, each column can also go to the CRM person (phone, LinkedIn profile, city and the rest of the mailing address), to the company (website, domain, industry, size and more), or to one of your CRM custom fields. A column whose heading matches a custom field you already have is matched to it for you. When a column has no field yet, a manager can choose Create a CRM field from this column; it counts toward your plan's custom field limit. A column sent to the CRM also stays a personalization field, so it can still go in your emails. A Tags column adds its cell to the person as one tag. When your workspace already has that tag, in any letter case or spacing, the import uses it. When it does not, the import creates it. The tags the person already has stay. Undo does not remove the tags an import added to people. The tags it created also stay in your workspace. Fields that record consent or where someone is in your sales cycle are never offered, because a cold file carries no consent.
During the import, each lead is matched to a person already in your CRM by any of their email addresses. The company is matched by the company website or domain column, or else by the domain of a work email address (a personal website or a free mail account never names a company), and a company in Trash is never a match. When nothing matches, a new person and company are added. A person who already exists is only ever filled in: a value they already have is never replaced, and their consent is never changed. A new person needs a first name and a company, so a row without either still imports as a lead and the completion screen says how many were not added to the CRM and why. The Checks step shows the counts before you start: new people, people matched, and new companies. Adding people to the CRM needs the CRM import permission; without it, the import adds leads only and says so. New people count toward your plan's contact limit, and if an import reaches it, the leads keep importing while new people stop being added, and we let you know once.
Several email addresses for one person. A file can carry more than one email column. One of them is the sending email: the address the campaign writes to, which is the first email column unless you pick another. Every other email column is an Additional email: it is saved on the same CRM person and never written to. An additional address that belongs to someone marked do not contact keeps that row out of the import, exactly as the sending address would.
Time zones. Nobody needs to type a time zone name. A Time zone column can say ET, CT, MT, PT, Eastern Time, Pacific, GMT, CET, UTC+1 or GMT-5, or a full name such as America/New_York. Where a label can mean more than one place (CST is both US Central and China; IST is India, Israel and Ireland), the lead's country or state settles it, and without one the lead is left as not detected rather than guessed. With no time zone column, a State or province column sets the zone for United States and Canada leads, and the country sets it for the rest. Each lead is worked out in that order: the time zone column, then the state with the country, then the country. A lead none of those settle sends in the campaign's fixed zone. Before you start, the Map step shows how many leads land in each zone, named in plain words (for example Eastern (New York) or London), how many are not detected, and how many rows have a time zone that disagrees with their state (the time zone column wins). The launch checklist shows the same breakdown for the leads ready to enroll.
While it runs. Your file uploads from this browser in one step, and then we check it, which takes a moment: keep the tab open until the screen says you can close the window. From then on the import runs on our side, so you can close the window and carry on. We let you know when it is done. If you come back to Leads while it is still going, a quiet line at the top shows Import in progress with a progress bar, the running count and a View progress link. The page of the list it is filling shows the same line. Dismiss hides it for that import, on every later visit too. If the page reloads while your file is being checked, the import page in that same tab picks the import back up. A new tab or window does not have that record. While the check runs, it continues on our side: when the file passes, the import runs and the line on Leads shows it. If the check stops before it finishes, only the tab that started the import can resume it. If that tab is closed, we end the import and send you a notification, so you can start a new one. When the check refuses the file itself (its size, its rows, its columns or the security scan), we send you a notification with the reason. Any other answer, such as another import already running or a short outage, shows in the tab that started the import. If another import is running, the page says so and keeps your upload for a day. Press Resume import when that import finishes. If the other import is your own, the page shows its progress when you open the page again in that tab.
During import, Laureo runs several safeguards before any lead becomes eligible to send:
Dedupe
Existing-customer skip (with override)
Suppression subtraction
Address check
Blocked-domain exclusion
Personal addresses. The Checks step also shows what share of your file is at personal mail providers, because some of those providers disable inactive accounts that can still pass an address check, so a small share of those addresses bounce. Two rows show it: Consumer addresses for every personal mail provider, and a second row for the provider family where inactive accounts can bounce. Both are information only. The addresses import as usual, and a campaign's Skip personal email addresses switch is what leaves them out, when leads enroll.
Addresses you already have. The Checks step counts the rows in your file that are already leads in your workspace and asks what this import should do with them, under Already in your outreach leads. There are four answers. Add to this list too is the default: they join this list and stay in every list they are already in. Move into this list takes them out of the lists they are in now, and holds back two groups it will not move, each named with its own count: leads that are active in a running campaign, and leads sitting in a teammate’s list. Skip them changes nothing at all for those addresses. Update them adds them to this list too, and refreshes their time zone and personalization fields from this file, and their State once the State field is available; leads in a running campaign are left as they are. It is how a second import of the same file fills in what the first one missed. Each answer shows the number it will really land in this list before you start, so the figure on the completion screen is the one you were shown.
What the completion screen says. When something landed, it reads Import complete and spells out each part on its own: leads imported, then added to this list under the add answer or moved from another list under move, then duplicate rows inside your file, then skipped, then any with errors. When nothing landed there is no green check and no anonymous number: it reads Import finished, Nothing was added to this list., and names the reasons the rows were skipped for. Under Skip them, the addresses you chose to leave alone are counted under Already in another list. See the import result opens the list this import was aimed at, not the index, and so does the Lead import complete notification we send when it finishes.
The free checks above run for every workspace: format, disposable domains, and a mail server for each new lead's domain. A lead you add by hand gets the same checks. When your workspace also has address checking, Laureo asks an outside address-checking service, after each import, whether each new address can receive mail. It runs in the background, and the list page shows its progress in the caption, for example Verifying 120 of 500, refreshed every couple of minutes. Re-verify list on the list page runs it again.
| Field | Description |
|---|---|
| Invalid | The address cannot receive mail. The lead is held back from campaigns, unless a campaign uses Include anyway. |
| Catch-all or unknown | The domain accepts any address, or the check could not be sure. The campaign’s catch-all choice decides: Skip them or Send to them. Skip them also holds a first email still waiting to send to such an address: it is not sent, and the lead stops. |
| No answer | The service gave no answer, for example because it was busy or the daily limit was reached. The address stays unchecked. Re-verify list checks it later. In a campaign set to Skip them, a first email to an unchecked address waits up to a day after the lead enrolls and stops if no answer comes; a campaign set to Send to them sends it as before. |
Each workspace can check up to 2,000 addresses a day. Past it, the rest of the list stays unchecked, and the owner of the list gets one notice that day. Re-verify list on a later day checks the rest. A launch never waits for address checking. Without address checking, none of this runs, and the free checks above still do.
You do not need a file to add a prospect. Add lead sits on the Leads tab in both the All leads and Lists views, and on every list's own page. It opens the Add a lead panel, grouped as Lead, Company, Location, List, and Personalization fields. It collects every field an import can carry: email address (the only required one), first and last name, company, and job title, plus country as two letters. It also collects one thing a file cannot: a Time zone, picked from a searchable list rather than typed, so the send window can be read on that lead's own clock.
Under Personalization fields you can add your own named fields, exactly like the extra columns in an imported file. Each row takes a field name and a value, and Add field adds another. You write the name however reads best. The variable it becomes shows underneath the row as Use it as followed by the variable, so naming a field Industry shows {{industry}} before you save. If two fields would land on the same variable, the panel says so and asks you to rename one. A running size is shown beside Add field once you have typed something, so a very large set of fields is never refused without warning. A lead added by hand is a normal lead: it can be enrolled, sequenced, and promoted like any imported one.
Every lead needs a list, so the panel asks which one to add to. Pick an existing list, or choose Create a new list and name it. Creating a list here asks where the contacts came from at the same time, because a list cannot be used in a sequence until that is recorded (see below).
New list on the Leads page makes a list in two steps. Name this list takes the name, an optional description, and where the contacts came from, and Continue creates the list. Add leads then offers the three ways to fill it: Add existing leads opens the picker of leads you already have, Import a file opens the import wizard with this list already chosen, and Skip for now leaves it empty. All three open the new list, and so does Done for now.
The same safeguards apply to a lead added by hand as to an imported one: an address on your suppression list, one marked do-not-contact in your CRM, one belonging to an existing customer, or one on a blocked domain is refused with the reason. An address you already have as a lead is not refused. The panel asks Add it to this list too?, naming the list it is already in when that is a list you can see, with Add to this list too beside Not now; answering yes puts the lead you already have in this list as well, rather than making a second one.
Every import requires you to attest to the source of your list: that you have a lawful basis to contact these people and did not buy a scraped list of unknown provenance. This attestation is recorded and is a hard requirement: a sequence cannot launch against leads imported without it. It gives you a record for compliance purposes.
Wherever it is asked, the attestation is the same two questions: Where did this list come from?, with choices for contacts you collected yourself, a purchased or licensed list, an export from another tool you own, and Other; and a confirmation that the list was collected lawfully and holds business contacts you have a legitimate reason to email. A purchased list asks for the provider name and an Other list asks you to describe the source, in both cases at least a short sentence. The confirmation is never ticked for you.
The same applies to a list you built by hand. Creating a list from the Add-lead panel asks the same questions in place, so the list you just made is usable straight away. If a list has no source recorded, its page shows a line saying it cannot be used in a sequence until you record where the leads came from, with a Record list source action beside it, and the same action sits in the list header. Answer once and the line clears. Your answer is stored with the list for compliance records.
Your organization can have up to 10,000 leads active in cold sequences at once. The Leads tab shows a gauge of how much of that headroom you are using. When you launch a sequence, Laureo checks that enrolling its leads would not exceed the ceiling. If it would, the launch is blocked with a message telling you exactly how many leads over the ceiling you are. Resolve enrollments or finish existing sequences to free up headroom.
A lead list does not send anything on its own. It has to be attached to a sequence. Open the sequence builder and, in the Leads section at the top (above the Steps), use Attach a list to pick the lead list (or lists) this sequence emails. You can attach up to 20 lists to one sequence.
Attach a list shows your lists newest first, and Load more lists at the bottom of the menu brings in the next page. Type to search every list you have by name, archived ones excluded. Each row shows how many leads the list holds.
Once a list is attached, the builder shows how many of its leads are ready to enroll, written as Ready to enroll: 1 of 5. The first number is what this sequence will email. The second is how many leads the list holds, or how many rows your file had when the list came from an import.
The summary lists one line for every reason that applies to the lists you attached, with its own count beside it, and hides none of them. These are the reasons you will see most often.
| Field | Description |
|---|---|
| Already in this campaign | The lead is already enrolled in this sequence, so it is not enrolled a second time. |
| Paused leads | The lead is paused, and Resume these leads sits beside the count. |
| Already replied | The lead wrote back, so it is not added unless the campaign has Also contact leads who already replied turned on. |
| Unsubscribed or suppressed | The address opted out or sits on your suppression list, and can never be emailed again. |
| Bounced or reported as spam | An earlier email bounced or was reported as spam, so the address is out. |
| On your blocked-domain list | The address is at a domain, or a subdomain of one, on your blocked-domain list. |
| Blocked by your country rules | The lead is in a country your country rules are set to skip. |
Three more appear when they apply: Held by your per-company limit, when the sequence caps how many people it emails at one company; Suppressed earlier; and Promoted to a contact.
An import can add fewer leads than your file had rows. The notice when it finishes, and the builder whenever the two numbers differ, both end with See the import result, which opens that result on the page of the list you imported into: every skipped address is listed under the reason it was skipped for, a few at a time with Show all for the rest.
Two of those reasons are yours to overrule: Active in another campaign, and In a teammate’s list, which only an admin can reach. Both carry an Add anyway control in the import result, with the group’s own count in it. The confirmation tells you that the other campaign keeps running, so the same person can be emailed by two campaigns, and it asks you to write down why, which is kept with the import for your records. Unsubscribed, bounced, blocked and region-restricted addresses can never be overruled.
There is no rule that skips a lead for being contacted recently, and being in another list is no longer a reason on its own. Already in another list appears only when you chose Skip them at the Checks step, and it has no Add anyway: running the import again under Add to this list too is the change. Active in another campaign is read only when you chose Move into this list, because moving a lead mid-send is what that guard exists to stop, and adding one takes nothing away. Already in this list means the lead was in this list before the import started.
What Review and launch counts before you launch, and the switches beside the counts.
By default a campaign adds only leads whose status is Active. In Review and launch, under the Leads line, each of the other six statuses has its own row with its count, and a row at 0 still shows: Paused leads, Unsubscribed or suppressed, Bounced or reported as spam, Already replied, Suppressed earlier and Promoted to a contact. The paused row carries Resume these leads. The replied and promoted rows each carry a switch, described below. If one of those two rows shows no switch, this panel cannot show or change that setting yet. Leads with that status are then added only if the assistant turned the setting on for this campaign. The other three rows have no switch, because those leads are never contacted. On an active or paused campaign the panel is called Review changes, and it shows these rows only when it can count exactly the leads this campaign did not add.
Up to four switches sit in this block. Every one of them reads Also contact, so on always means more leads are contacted:
- Also contact leads who already replied is off by default. Turn it on to add leads whose status is Replied. It sits on the Already replied row.
- Also contact leads already added to the CRM is off by default. Turn it on to add leads whose status is Promoted. It sits on the Promoted to a contact row.
- Also contact leads active in another campaign is off by default, so a new campaign leaves out leads that are active or paused in another campaign. Turn it on to contact those leads too. An existing campaign keeps its own setting. The switch shows when some of your leads are running in another campaign, under a line that says how many and which campaigns they are in.
- Also contact leads who are already customers is on by default. Turn it off to leave out leads whose contact record is marked as a customer.
A replied or promoted lead that a switch lets in meets every other check, like any other lead. A lead who opted out, or who is marked do not contact, is never contacted, whatever these switches are set to. The lead keeps its Replied or Promoted status, and if it replies again, this campaign stops emailing it. Turning on either of these two switches is recorded in the consent log with your name and the date. If that record cannot be saved, the switch stays off.
These switches belong to this one campaign, so a change to one changes nothing in any other campaign. You set them before launch: on an active or paused campaign they are fixed. Unsubscribed, bounced, blocked and region-restricted addresses are never contacted, whatever these are set to.
The Leads tab opens on All leads, a single table of every cold lead across all your lists. Individual lists are one toggle away, and a Filter by list control narrows the all-leads view to any one list, alongside filters for status (Active, Replied, Paused, and more), the Reply filter, a country filter and a search box. The search matches part of an address, a first name or a last name, and two words match a first name and a last name together. Once you choose a country with states or provinces, a state filter appears beside it. Add filter narrows by one of your own fields, such as a State or Industry column from your file: pick the field, then is (the exact value), contains (part of the value, upper and lower case alike) or is empty. A list’s own page offers the same filters, apart from state. A muted note at the top restates that these are cold leads, kept separate from your CRM contacts and the CRM Lead stage.
What the list counts mean. On the Lists view, Replied counts the leads in a list where a person wrote back at least once. An automatic reply, such as an out-of-office message, does not count. A lead that replied and later unsubscribed, was promoted to your CRM or was set back to active still counts, because that person did reply. In campaigns counts the leads that are taking part in a running or paused campaign right now; a lead that finished, stopped or was never added to a campaign is not in it. On a list’s own page the Replied filter opens exactly the leads the count names. In a campaign’s figures, Replies (people) counts each person once, on their first reply from a person.
Opening a lead reveals its activity timeline beside its imported fields: the emails sent to that lead, any reply, and its enrollment and opt-out events, drawn from the real send and consent history rather than a guess. From the same panel you can pause or resume, promote, unsubscribe, or remove that one lead. Pause in sequence holds the lead's next email in every campaign it is in, and the lead stays enrolled. Resume in sequence makes that email due again.
Archive a lead to keep its history but take it out of every campaign, count and default list; Unarchive puts it back with its status unchanged. Opt out and Mark bounced are also in the same menu. The Archived filter beside the status pills is where archived leads are, and an archived lead reads as its own status with Archived after it, so a lead that replied still reads as one.
A Variables list above the timeline reads everything back: email, the built-in fields, the picked Time zone, and every personalization field the lead carries, whether it arrived from a spreadsheet column or was typed into the Add-lead panel. Each one is captioned with the name you gave it rather than its variable, so a column you called “Company size” reads that way here too.
On a list’s own page the table adds a Time zone column at wider widths, and the lead panel carries the same answer at every width. It names the zone that lead’s send window is read on and, after a middle dot, where that zone came from: from your time zone column when your file carried one, from state or from country when it was worked out from where the lead is, set by you when you picked it by hand, and No time zone with sends in the sequence time zone when nothing answered. A zone worked out from a state or a country is a representative one for that place, which is why the line says where it came from.
Select rows to act in bulk. Add to list puts the selected leads in one more list and leaves every list they are already in alone. Move to list on a list’s own page puts them into another list and takes them out of the list you are looking at, and only that one; leads that are mid-sequence stay where they are, and the message says how many. Remove from list takes them out of this list and keeps the leads: before it runs it warns you about any lead that would then be in no list at all, naming how many for the rows you ticked, and afterwards it says how many are. Promote to CRM promotes them all at once, which pairs naturally with the Replied filter: narrow to leads who wrote back, select them, and promote the batch into your CRM in one step. Leads already in the CRM are counted as such and skipped rather than duplicated.
Select all in a list. On a list’s page, tick every row of a page and the bar offers Select all with the number of leads your filter shows in that list. The selection is then every one of them, on every page; untick a row to leave it out, and the bar reads, for example, 3,286 selected (2 excluded). Move, Add to list, Remove from list and Promote on a selection that size run in the background as one action: you can leave the page, the bar shows the progress while you stay, and a notification says when it is done and what it did. Deleting leads stays one lead at a time.
Four ways to put a lead you already have into another list. On the page of the list you want it in, Add existing leads opens a picker of every lead that is not in that list yet, with a search box, a status filter, a filter that narrows to one other list, and a running count of what you have ticked; up to 100 go in at a time. From All leads, select rows and press Add to list. In the Add a lead panel, typing an address you already have offers Add to this list too instead of a refusal. And an import does it in bulk with Add to this list too on the Checks step. All four leave every other list the lead is in exactly as it was.
Deleting a list keeps its leads. Removing a list does not remove the people on it. A lead that is also in another list simply loses this one and carries on in the others. A lead whose only list was this one is moved into a new list named Unassigned followed by the deleted list’s name, so no lead is ever left with nowhere to be found, and the message afterwards names that list and how many leads went into it. Deleting a list does not stop a lead that is enrolled in a running or paused sequence: those leads keep sending, and the confirmation counts them before you decide.
Exporting a list. On the Lists view, Export CSV in a list’s row menu downloads every lead in that list, archived leads included. Besides the standard columns, the file holds Last Reply At, Last Reply Intent, Archived At and one column per personalization field the leads carry, up to 500 fields. A field with the same name as a standard column, such as email, gets (custom) after its heading. When the leads carry more than 500 fields, the file keeps the first 500 in alphabetical order, and its last lines say how many fields it left out. If an export cannot finish in time, its last line says the file is incomplete and how many leads it holds.
The leads list has a Reply column. It shows what a lead’s last reply meant, in the same words the inbox uses, with the date under it. Where the last read was not a confident one, a short note beside the date says so, so a guess never looks like a certainty. A lead who has not written back shows a muted dot. The same answer sits on that lead’s own panel, beside Status.
The Reply filter beside the status pills narrows the list to one of those meanings. A person replied and No reply from a person come first: they ask whether anyone wrote back at all, counting a reply from a person and never an automatic one, which is the same rule the Replied count follows. Two more options answer the questions a label cannot: No reply of any kind for everyone who has not written back at all, and Replied, no label for people who did write back but whose reply we could not read or have not read yet. Nothing in there is waiting on you to judge it: where the first read was unsure, a second read settles the label on its own.
With any filter on, the leads list and a list’s own page offer Make a list from this filter. The window names the filter in words and how many leads match before you create anything. Matching leads are added to the new list. A lead can belong to several lists, so they stay in the lists they are in now and nothing is taken off anyone, including the leads that are part way through a sequence. Name the list, press Create list and add, and the cohort the filter described is a list you can send to. One press is enough for any size: a large filter fills the new list in the background, the window shows the progress while it is open, and a notification tells you when the list is complete.