Turn chatbot conversations into leads, handoffs, and better answers
Capturing a name and email is only the first step. Here is how lead capture, human handoff, and the analytics pages fit together in a working website chatbot.
A chatbot that answers questions well is useful. A chatbot that also captures the right contacts and escalates at the right moment is a channel. The difference is mostly configuration.
Capture leads inside the conversation
Lead capture runs as a step in the chatbot flow rather than as a popup competing for attention. When the step runs, the visitor gets a form in the chat, and a successful submission saves both a contact and a lead record scoped to that workspace and chatbot.
Beyond name and email, you can define custom lead fields for your workspace so the form asks what your team actually needs, such as company size, service interest, or location. Field availability follows your plan limits.
Escalate to a person when it matters
Some conversations should not end with an answer. A handoff step moves the conversation into a waiting state and notifies workspace users.
Notification routing depends on who is around:
Users who are present in the app get an in app notification
When nobody is present, an email fallback goes out instead
Browser push is delivered when a user has subscribed and push is configured
Conversations that sit pending are closed by a timeout worker, so a missed handoff does not stay open forever.
Read what actually happened
The conversation archive lists sessions with status, a preview, metrics, and visitor context. Opening one shows the full transcript with source references, captured leads, session details, and any images the visitor uploaded.