The Leads Table
Every lead a bot has captured, on every channel, in one table.
Find the Lead You Want#
Rows arrive newest first. The search box matches the Name, Email and Phone columns only, so search for the person rather than for what they asked about, and narrow the rest with the channel and date filters. Opened from the rail, the table spans every bot in the workspace and adds a bot filter and a Bot column.
Read the Columns#
| Column | What it holds |
|---|---|
| Name | The name captured, under a channel icon, with the visitor's WhatsApp or Instagram account beneath |
The email captured | |
| Phone | The phone captured |
| Files | Anything a Form node collected as a file upload |
| Tags | Your own labels and any Chatleadr applied, as coloured chips |
| Date | When the lead was captured |
| Status | New on every row. Nothing changes it, so track progress with tags |
A Name reading Unknown or an Email reading unknown@example.com means the workflow wrote that answer to a differently named variable. See how a lead is captured.
Open a Lead to Read the Conversation#
Opening a row shows the conversation the lead came out of, beside a summary: the record says the visitor asked for a quote, and the transcript says what the quote was for. A lead whose conversation has expired has no transcript, and the panel says so rather than showing an empty thread.
Tag the Leads You Want to Find Again#
Tags are yours to define, and they keep the table usable past a few hundred rows. Tag what the person wants, such as "quote request" or "already a customer". A tag applied to every row narrows nothing.
One is applied for you. possible-duplicate marks a lead whose uploaded file has already been seen on another lead in the workspace, and carries a warning icon so a machine's suspicion does not read as a person's judgement.
Download the Table as a Spreadsheet#
Download CSV writes every row matching your current filters to a file: the contact columns, the status, the date, the channel, and every value the workflow left in the payload, each as its own column prefixed payload_. So a form field called budget_range arrives as payload_budget_range. Files arrive as links, and tags are not exported.
One file holds 25,000 leads. Past that the download is refused and names the number, so narrow the date range and download again.
Common Questions#
Can I Filter or Search the Table?#
Yes, on the contact columns, by channel and by date range. For analysis across many rows, download the CSV instead.
Do Leads From WhatsApp Appear Here?#
Yes. Every channel writes to the same table, and each row shows the channel of the conversation it came from. A lead with no conversation attached shows as web. There is no separate WhatsApp inbox.
How Long Are Leads Kept?#
Indefinitely. A lead is kept until you erase the contact or erase the workspace. The conversation behind it expires on your plan's retention period, so a lead can outlive its own transcript.
How Do I Remove a Lead?#
There is no per-row delete. Erase the contact instead, which removes every lead for that person in the workspace along with their files, and adds them to the suppression list. See erase a contact. A deletion request under POPIA or GDPR also covers anything you exported, which erasing the contact here cannot reach.
Does the Leads Table Count Toward My Plan?#
No. Plan limits count conversations, not leads. See what counts as a conversation.