Channels
AI CRM
By team
Alternatives
Learn
Guides
Lead database
Import leads from a CSV or XLSX, keep every column, and run email, LinkedIn and WhatsApp from the same list. People and companies exist once, however many campaigns they are in.
One list
Most stacks keep a list per tool, so the same person gets an email, an invite and a WhatsApp message from three systems that never compare notes.
Shared by every channel
Hannah Weiss
Head of Growth · lumen-freight.example
Import
Bring a list in from a spreadsheet, match it to who you already have, and keep the columns you care about.
Headers are matched ignoring case, spaces and punctuation, so Job Title, job_title and JOBTITLE are the same column. Every row needs an email or a LinkedIn URL. Rows with neither are dropped before the import starts.
Phone numbers typed without a country code use your organization's default phone country. A malformed phone number is dropped and the rest of the row is imported.
| Lead field | Accepted headers |
|---|---|
| email, email address | |
| LinkedIn URL | linkedin, linkedin url, linkedin profile |
| Full name | name, full name |
| First name / Last name | first name, last name |
| Job title | title, job title, headline |
| Company name | company, company name |
| Company domain | domain, company domain, website, company website, company url |
| Phone | phone, phone number, mobile, mobile phone, mobile number, whatsapp, whatsapp number, work phone |
| Notes | notes |
Duplicates
linkedin.com/in/rcosta (no email)
[email protected] + a profile of someone else
Merge them first
A blank cell never erases what is already stored. One bad row never blocks the rest.
Custom fields
Store a plan tier, a region or a renewal date on a person or company, typed, per organization, without touching the database.
Typed, per organization
Removed fields
Remove hides a field everywhere and keeps its data. Restore brings it back.
Protect your list
The people you must not message should be impossible to message by accident, from any tool.
Do Not Contact
Samir Haddad
COO · parcelly.example
Enforced by the server before each send, not just hidden in the UI. Clear the flag from the same menu to send again.
| Name | Job title | Source |
|---|---|---|
| Hannah WeissLumen Freight | Head of Growth | CSV import |
| Rafael CostaBrightloop | VP Sales | LinkedIn search |
| Aiko TanakaKestrel Health | Growth Lead | Table |
| Samir HaddadParcelly | COO | CSV import |
Imported people appear on the Leads page with their company, job title and source, ready to add to a campaign.
Search covers email, LinkedIn URL, name, title, company and domain, plus imported extra columns. Filters narrow People down further.
The details
The small things that keep a list usable as it grows.
Straight into campaigns
Extra columns kept
Companies by domain
Lead categories
Reach at a glance
Suppression list
Per organization
No silent merges
Import runs
Get started
Import your list
Check the result
Add your own fields
Launch from the list
FAQ
One list of people and companies for your whole organization. A person exists once, no matter how many email, LinkedIn or WhatsApp campaigns they are in, and a company is identified by its domain. The Leads page shows who you can reach, which campaign they are in and their CRM state.
On the Leads page, open Import people and choose an .xlsx, .xls or .csv file. The first sheet is read and the first row must be the headers. Every row needs an email or a LinkedIn URL. Imports take up to 5,000 rows per file, and the summary lists processed, created, updated and failed rows, with the reason for each failure.
Yes, in a campaign import. A mapping screen shows each column with a sample value and a Platform field dropdown, pre-selected where the header looks familiar. A column can map to one field only. Choose Keep as variable for any column you want to use in messages, so Job Title becomes {{jobTitle}}.
Each row is matched to an existing person by email, ignoring case, then by LinkedIn profile. A match is updated and no match creates a new person, so importing the same list twice does not duplicate anyone. A blank cell never erases stored data. If a row's email and LinkedIn profile belong to two different people, that row fails and asks you to merge them first. In an email campaign, an address already in the campaign is counted as a duplicate and not enrolled twice.
Fields you add to people or companies beyond the built-in ones, such as plan tier or renewal date. They are defined per organization, typed (Text, Number, Currency, Checkbox, Date, URL, Email, Image from URL, Select, Multi-select or JSON), and keep a permanent key that starts with x_. You can rename a field, change its type where the values convert, remove it and restore it, or delete it permanently.
Yes. Mark a person Do Not Contact from their CRM record and sending is refused on every channel: email sequences, LinkedIn replies, WhatsApp and CRM sends. Separately, a suppression list of unsubscribed, bounced, manual and complaint addresses is checked before every email, and email imports skip suppressed addresses.
Leads belong to an organization. Someone in another organization never sees them and you never see theirs, which is how an agency keeps one deployment with a separate organization per client.
Clone the repo, import a CSV and launch from one list. It runs in your own database, with no per-contact pricing and no one else holding your leads.
