Lead capture: how details are collected in the chat
The bot asks for contact details in conversation - there is no form - and every lead lands in your dashboard.
Last verified 2026-11-18
There is no form in the chat
The widget has one text box and a send button. It has no form, no fields and no submit button. Contact details are collected the way a person would collect them: the assistant asks for them in a sentence, and the visitor replies in the same box they have been typing in all along.
This is deliberate. A form interrupts someone mid-question and asks for trust before it has given anything useful. Asking in conversation, after the question has been answered, gets a far higher share of real contact details.
What the assistant asks for
Every bot collects a name and a phone number, whatever its Conversation Goal is set to. It asks for one thing per message - name first, number second - and never lists what it wants.
The order is fixed: it answers the visitor's question first, then asks. Someone who has not been helped yet has no reason to hand over anything, and asking too early tends to lose both the answer and the number.
It makes at most two attempts per detail. If the visitor declines twice it stops asking and keeps helping them anyway.
With the lead capture Conversation Goal, the assistant goes further once the visitor shows real interest, asking for details such as city, company and email in the same conversational way.
Nothing has to be asked for to be captured. If a visitor types an email address into the chat at any point, Matram records it as a lead automatically.
Phone numbers are checked before they are stored. A number that is clearly mistyped is queried once, kindly; a number with a country code is accepted at whatever length it is, so overseas visitors are never told theirs is wrong.
Returning visitors do not create duplicates
Leads are deduplicated per chatbot and email address. If someone who already left their email comes back and chats again, Matram updates the existing lead with any new details rather than creating a second record. One person, one lead per bot.
Dedupe depends on the email address. A lead captured without an email cannot be matched to a later visit.
AI summaries and CSV export
Open your chatbot and go to the Leads tab to see every captured contact. Shortly after a lead is captured, an AI-written summary of the conversation is added to the lead's note, so you can see what the person wanted without reading the full transcript. Click a lead to view the summary in a popup.
Use the export button on the Leads tab to download all leads as a CSV file for your own tools or reporting.
Push leads to your tools
Connectors can send each captured lead onwards automatically:
- HubSpot: connects via OAuth from the Connections page, upserts the contact by email, and attaches the chat transcript as a note.
- Zendesk: creates a ticket that includes the transcript.
- Webhook: sends a signed POST with the lead payload to any URL you choose. When you set a secret, the request carries an HMAC signature you can verify.
These connectors fire when a lead is captured and when a conversation escalates to your team.
Try it on your own content
Everything in this article works the same on the free trial. Train a bot on your site and see it answer with sources.
Book a demoNo credit card required. Plans start at $29/mo after the trial.