chatleadr Docs
Open Chatleadr

My Lead Did Not Arrive

Work down the list in order. Each check is quicker than the one after it.

Path 1: a workflow reaches an End node End node Goal Tracking decides which arrow is taken. Default: None The leads table A row in your dashboard, plus a lead in Analytics. Save to the leads table Email notification Sent to the addresses on the Lead capture tab. Send to your lead integrations A ClickUp task Created in the list you picked, Growth and above. Send to your lead integrations Path 2: the conversation ends, with Automated Lead Tracking on Session ends A model reads the transcript and extracts the configured fields. Skipped if any are missing. Reaches the same email and ClickUp destinations, independently of the switch on any workflow.
One End node, up to three destinations. Each is enabled separately, and “Send to your lead integrations” with no integration enabled does nothing at all.

1. Check the Destination Is Switched On#

Open the bot, then the Lead capture tab. Automated Lead Tracking carries one row per destination: one writes the leads table, one sends the email, and one creates the ClickUp task. A row switched off receives nothing, whatever the workflow did.

The switch at the top of the card is not a master switch. It governs the automated path only, so a workflow's End node still dispatches while it is off.

2. Check the End Node the Run Finished On#

Goal Tracking on an End node defaults to None, which records nothing. A workflow with several endings may also have finished on a different End node from the one you set up, and the execution log names the node each run reached.

Set the success ending to Send to your lead integrations for all three destinations, or Save to the leads table for the Leads page alone. See the End node.

3. Check the Field Names#

Every destination reads bare state keys, so name the contact fields exactly name, email and phone. On a Form node it is the field id that sets the key, not the label. A lead saved with the name Unknown, the address unknown@example.com, or Not provided on a line reached its destination with the answer written under a different name. See how a lead is captured.

4. Wait Fifteen Minutes for the Automated Path#

Automated Lead Tracking reads the transcript once the conversation has been idle for ten minutes, so a lead arrives ten to fifteen minutes after the visitor's last message, and never while a chat is still open. After that, one thing stops it: a field marked required under Lead fields that the visitor never gave. That cancels the whole lead, so no email, no task and no row.

A workflow's End node behaves the opposite way, sending whatever it has and filling each missing field with Not provided.

5. Check the Suppression List#

A contact who has been erased reaches no destination on either path, and the execution log says so on the run. Capturing them again means taking them off the suppression list. See erase a contact.

What to Send Support#

Email support@chatleadr.com with four things:

  1. The bot's name, and the destination the lead should have reached.
  2. The time of the conversation, and the channel it came in on.
  3. Whether the lead appears on the Leads page.
  4. The execution log entry for that run.

A lead on the Leads page but not in ClickUp is an integration problem. A lead missing from both is a workflow problem, and the execution log is what settles which.

Common Questions#

Why Am I Getting Two Emails per Visitor?#

Both capture paths ran. A workflow's End node sent the lead when the run reached it, and Automated Lead Tracking sent a second one when the conversation went idle ten minutes later. They are independent, and the switch on the card does not govern the End node. To send one email per visitor, switch Automated Lead Tracking off on any bot whose workflows already capture the lead. That switch also stops the summary: only Automated Lead Tracking reads the transcript, so the remaining emails and tasks carry no summary of the chat, no page address and no campaign tags, and the Leads page shows no summary either.

The Task Arrived but Every Line Reads Not provided. Why?#

The workflow sent the lead without setting the fields the template reads. The integration still reports success, so the task arrives looking captured and carrying nothing, and saving a workflow in that state opens a dialog naming each missing field. Check the Form field ids against the names in check 3.

How Long Should I Wait Before Deciding a Lead Is Missing?#

A workflow End node sends the lead within a few seconds of the run reaching it. Automated Lead Tracking waits for ten minutes of silence, and the lead follows within five minutes of that. Start checking a minute after the run for an End node, or fifteen minutes after the conversation goes quiet.