AI Chatbot Lead Management
Control the lead prompt and manage visitor email addresses captured during chat.
Capture and notify
Lead capture is enabled by setting the visitor-message threshold in Bot Settings. When a visitor submits an email, the lead is linked to its chat session.
In Webhooks, enter up to 20 valid comma-separated Notification Emails. They receive new-lead notifications and human-escalation notifications, including urgent distress escalations when the safety flow is triggered.
Manage leads
- Review captured date and session message count.
- Open the related conversation when it still exists.
- Export all bot leads as CSV.
- Delete an individual lead without deleting its related conversation.
Human follow-up and distress escalations
Request human follow-up is an escalation request, not a promise of live chat. A successful request marks the conversation for review and sends the configured escalation notification without delaying the visitor response.
When the deterministic distress-safety flow activates, the visitor receives safety guidance first and the session is marked Escalated. The current widget can show a call action for 988 in the U.S./Canada, a local-crisis-help action, and Request human follow-up.
If an anonymous visitor chooses human follow-up, the widget can ask for an optional contact email. That address is attached to the urgent follow-up context but is not silently created as a normal chatbot Lead record.
Why chatbot lead capture matters
A chat widget often talks to a visitor at the exact moment they are deciding whether your product fits their need. Capturing an email address during that conversation turns an anonymous session into a contact you can follow up with through K2Mailer or PushWave, instead of losing the visitor the moment they close the tab.
Because the lead is linked to its chat session, your sales or support team can read the full conversation before replying, so the first follow-up email or call references what the visitor actually asked instead of a generic greeting. That context is usually the difference between a reply and a lead that goes cold.
Getting more value from captured leads
Export leads regularly and bring them into a K2Mailer list so they receive a proper welcome sequence, segmented by the bot they came from or the topic they asked about. Pairing chat leads with auto follow-ups or a drip series keeps the conversation going without manual work.
Review the notification emails sent to your team for accuracy. If the same question keeps triggering a lead prompt, that is a signal to expand the bot knowledge base so fewer visitors need a human reply at all, while still capturing the ones who do.
Frequently asked questions
- How many notification addresses can I add?
- Up to 20 valid, comma-separated addresses can receive new-lead and human-escalation notifications for the bot.
- Can I delete a lead without losing the conversation?
- Yes. Deleting a lead removes the lead record only; the related conversation stays available if it still exists.
- Does lead capture work the same on every bot?
- Each bot has its own visitor-message threshold in Bot Settings, so capture timing can differ between a sales bot and a support bot.
Was this guide enough?
Contact support if your screen or result is different.