chatleadr Docs

The Leads Table

Every lead a bot has captured, on every channel, in one table.

Leads All channels Leads 128 captured this month Download CSV Name Email Phone Came from Files Tags Date Thandi Mokoena @thandi.designs thandi@example.com +27825550101 WhatsApp number Meta ad: Websites in 10 days View 3 files Quote request 17 Oct Riaan de Villiers riaan@example.com 082 555 0143 Google: winter_sale /winter View 1 file Booking 17 Oct Aisha Patel aisha@example.com Home page Newsletter 16 Oct Sipho Ndlovu @sipho.ndlovu sipho@example.com Story reply Booking 16 Oct
Captured leads, each with what brought them in the Came from column.

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, Came from 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#

Each row holds one lead, in these columns:

ColumnWhat it holds
NameThe name captured, under a channel icon, with the visitor's WhatsApp or Instagram account beneath
EmailThe email captured
PhoneThe phone captured. On WhatsApp, when the visitor typed none, the number they messaged from, marked WhatsApp number
Came fromWhat brought them: a Meta ad, a campaign, a story or the page they were on, or the channel when nothing more is known
FilesA button such as View 3 files, which opens every file saved on the lead, such as a Form node's file upload
TagsYour own labels and any Chatleadr applied, as coloured chips
DateWhen the lead was captured

To see a lead's files side by side, click the button in the Files column. Click a file to open it in a new tab. An image appears as a picture only after a safety check passes it. Until then, and for an image type the check cannot read, a crossed-out eye stands in for the picture. To see that image, click the crossed-out eye. An image that fails the check is kept but cannot be opened, here or from its link in a spreadsheet you downloaded earlier.

A lead that automated lead tracking wrote when the conversation ended carries every file Chatleadr stored from that conversation, up to 20, unless a workflow already saved the file on another lead. Those files are labelled file, file_2, file_3 and so on.

A Name reading Visitor, or an Email shown as a dash, means the conversation gave no name or no email. When you expected one, the workflow wrote that answer to a differently named variable. See how a lead is captured.

On WhatsApp and Instagram, the line under the name is the account they messaged from, such as Thandi Mokoena (+27825550101). When the account shared no name, the line shows the number or handle it did share, such as +27825550101 or @thandi.designs. When the account shared none of them, the line reads No name or number shared, or No name or handle shared on Instagram. Name not recorded marks an older conversation whose account Chatleadr did not keep, and Contact erased marks a contact you erased.

Came from names the ad, campaign, story or page behind each lead. What each value means, and how to tag your ad links so it names your campaigns, is in see which ad or campaign brought a visitor.

To list only the leads that one kind of origin brought, such as Meta ad or Campaign, choose it in the filter that reads Came from: any. Only the channel lists the leads where nothing more than the channel is known. Download CSV then writes only the leads the filter lists.

Open a Lead to Read the Conversation#

Click View Chat on a row to open 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.

The Came From card at the top lists what brought them, and on WhatsApp and Instagram their WhatsApp ID or Instagram ID, with a Copy button for erasing a contact. The lead keeps the card after its conversation is deleted.

When the panel has no conversation to show, it says why:

  • This lead was saved without its conversation. Nothing linked a conversation to the lead when it was saved.
  • This conversation was deleted at the end of your plan's retention period, but the lead is kept. The transcript expired with your plan's retention period. When the lead kept a copy of where it came from, the sentence ends but the lead and where it came from are kept.
  • Chatleadr could not load this conversation. Try again. The conversation exists and did not load. Open the lead again.

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, with its columns in this order:

  • The lead: id, name, email, phone, status and date, then sessionId, the ID of the conversation the lead came from. status reads New on every lead. Opened from the rail, the file adds botId and botName after sessionId.
  • Where the lead came from: the Came from columns listed in the next table, on every row.
  • Every value the workflow saved, each as its own column prefixed payload_, so a form field called budget_range arrives as payload_budget_range. Files arrive as links, apart from an image that failed a safety check, which arrives as Not available: this image failed a safety check. A file saved under several names arrives in each of those columns, and the files on a lead from automated lead tracking arrive as payload_file, payload_file_2 and so on.

Every column up to first_came_from is on every row and keeps its place, so an import that maps columns by position stays mapped. The payload_ columns that follow depend on what your workflows saved. Tags are not exported.

The Came from columns, in order:

ColumnWhat it holdsExample
channelThe channel of the conversationwhatsapp
channelIdentityThe account line under the name, or the WhatsApp or Instagram ID when there is no line. Blank on the web and for an erased contactThandi Mokoena (+27825550101)
profile_nameThe name on their WhatsApp or Instagram profile, chosen by themThandi Mokoena
profile_usernameTheir WhatsApp username or Instagram handle@thandi.designs
whatsapp_numberThe number WhatsApp shared, which can differ from a phone they typed+27825550101
whatsapp_or_instagram_idThe ID that Erase a contact asks for. Blank on the webZA.0000000000000042
phone_sourcewhatsapp when phone is their WhatsApp number, typed when they gave it, and blank when there is no phonewhatsapp
came_fromThe kind of origin, for a pivot table: Test chat, Meta ad, Meta post, Story reply, Story mention, Product, Shared post, Campaign (UTM tags or an ig.me link tag), Follow-up reply, Ad click, Facebook or Instagram link, Another website, Website page, or the channel's name when nothing more is known. came_from_detail says which oneMeta ad
came_from_detailWhich one: the headline, campaign name, keyword, link tag, product code, page or siteWebsites in 10 days
came_from_noteThe notes the Came From card shows for this conversationMeta sent this ad's ID and link, but not its headline, text or image.
ad_networkMeta, Google, Microsoft or TikTok when the visit is known to be an adMeta
ad_idThe Meta ad's ID, or the post's120200000000000001
ad_headlineThe ad's headline, or its title on InstagramWebsites in 10 days
ad_textThe ad's main text. WhatsApp ads onlyDesign, copy and hosting at one fixed price.
ad_mediaimage or videoimage
ad_image_linkA link to the copy of the ad's picture, or a still from a video ad, that Chatleadr savedA link to the picture
ad_linkMeta's link to the ad or post. WhatsApp onlyhttps://fb.me/example1
ad_details_atWhen the message carrying the ad's details arrived, in UTC. Meta does not say when the ad was tapped2026-10-17T07:14:00.000Z
link_tagThe tag on an Instagram ad or an ig.me linkwinter_flyer
catalogue_productThe product's code from your WhatsApp catalogueWEB-STARTER
first_messageTheir first message, or the label of the first button they tapped, up to 200 characters. Once the conversation is deleted, the lead keeps only a button's label, so the cell is blank unless the conversation opened with a buttonHello! Can I get more info on this?
utm_source, utm_medium, utm_campaign, utm_content, utm_termThe UTM tags of the page they arrived on, or of their first page with tagsfacebook
landing_pageThe page they arrived on, without its tagshttps://fynbosweb.example/winter
chat_pageThe page of their first message, without its tagshttps://fynbosweb.example/pricing
later_pagesOther pages they messaged fromhttps://fynbosweb.example/contact
click_id_fromWhich ad network's click code the address carried, never the code itselfGoogle Ads
arrived_fromThe website that sent them, by its address onlywww.google.co.za
previous_conversationsOn WhatsApp and Instagram, how many conversations the same person had with the bot before this one2
previous_conversation_idThe latest of those conversations6710a1b2c3d4e5f60123abce
first_conversation_atWhen their first conversation with the bot started, in UTC2026-10-02T08:30:00.000Z
first_came_fromThe came_from of that first conversationMeta ad

A column holding a list, such as later_pages or two notes in came_from_note, separates its items with a vertical bar. Every time is in UTC, and a blank cell means Chatleadr does not know the value.

payload_url and payload_utm keep the page of the first message, as the lead email's Page row does. landing_page and the utm_ columns describe the page the visitor arrived on, so the two differ when the visitor browsed before they typed.

ad_id, whatsapp_or_instagram_id, utm_campaign, utm_content, catalogue_product and whatsapp_number are written as spreadsheet text when the value is all digits, with or without a leading plus, so a spreadsheet keeps every digit of an 18-digit ad ID and the plus of a number. The file holds such a value as ="120200000000000001". A spreadsheet shows the digits alone. In LibreOffice Calc, tick Evaluate formulas in the import window to see them that way. A system that imports the file as plain text receives the equals sign and the quotes as well, so remove them in that system's import.

The download from a bot's Conversations page carries the same Came from columns, with account in place of channelIdentity. Its conversation_id matches sessionId here, so the two files join on it.

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, by what brought the lead 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. The lead keeps its account line and where it came from when the transcript goes.

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.