It earns the ask
The assistant answers from your own content first. Nobody hands over an email to a bot that has not yet proved it knows anything.
A contact form asks before it gives, which is why most of them are ignored. CustomerBot answers the visitor's actual question from your own content, and only then collects details — arriving with the whole conversation attached.
| Moment | Contact form | Assistant with lead capture |
|---|---|---|
| What the visitor sees first | Six fields and a submit button | An answer to the thing they came to ask |
| When contact details are requested | Before anything is given | After the assistant has already been useful |
| What the business receives | A name, an email and a one-line message | A name, an email and the entire conversation |
| What happens outside office hours | It waits in an inbox | The question is answered; only the follow-up waits |
| The visitor who does not convert | Leaves no trace at all | Still shows up in analytics as a question you cannot answer |
The assistant answers from your own content first. Nobody hands over an email to a bot that has not yet proved it knows anything.
Lead capture is a message in the conversation, not a modal over the top of it. You write the prompt yourself — the default asks for a few details so support can follow up properly.
The transcript is stored with the lead. Whoever picks it up can read what was actually asked instead of opening with “how can I help?” to someone who already explained.
Leads have statuses you can filter and bulk-update, so a hundred captured enquiries do not become an undifferentiated pile.
Captured leads land in a workspace with statuses, filtering and bulk updates. Mark a batch as contacted, filter to the ones still open, export the rest into whatever CRM your team already lives in.
Priya N.
Asked about enterprise SSO
Tomás R.
Wanted delivery times to Spain
Anna K.
Pricing for a team of 30
Jae-won P.
Integration with existing helpdesk
You do not need a scripted question tree. Most qualification falls out of the conversation if you have trained the right content.
Budget band
A Q&A pair that states your minimum engagement, so unqualified enquiries self-select out.
Timeline
A suggested question — “How soon do you need this?” — surfaces urgency without an interrogation.
Location or region
Your service-area page answers it, and the answer is recorded in the transcript.
Use case
Whatever the visitor asked about is itself the strongest qualifier you will get.
Lead capture is a toggle on the assistant, with a message you write. The natural moment is after the assistant has given a useful answer and the conversation is continuing — which is also the moment a visitor is most willing.
Yes. The full transcript is stored alongside the lead. That context is usually more valuable than the email address itself, because it tells your team what the person actually wants.
Export as CSV and import wherever you work. You can also filter and bulk-update statuses first, so you are exporting a working list rather than a raw dump.
It complements it. Keep the form for people who know exactly what they want and prefer it. The assistant catches the much larger group who had a question first and would have left without asking it.
Only if you write the prompt that way. Lead capture can be switched off entirely on assistants where deflection matters more than capture — a docs assistant, for example, usually should not be asking for emails.
They still generate signal. Their questions appear in analytics, including the ones the assistant could not answer, which is a direct list of the pages your site is missing.
Lead capture is on by default. Train the assistant, write the prompt in your own voice, and see what arrives.
Start free