How do you turn website enquiries into leads when the chat ends the moment the visitor leaves? A renovation business brought us that question. Their chatbot was answering visitors well — whether they worked in an area, what a service included — but the conversations ended there. Interested visitors left without anyone knowing who they were or what they needed, and by the time the sales team saw the chat history, the visitor had signed with someone else.
What they told us
A website chat is where buying intent shows up first. People ask things they would never put in a contact form: rough budgets, timing, worries. A chat that only answers lets that intent leave. But a chat that demands a name and phone number before it says anything puts visitors off before the conversation starts.
They wanted the assistant to answer first and then ask the business's own questions, the way a good salesperson would, and to keep what visitors told them somewhere the team could act on it.
How we approached it
Asking for personal details is a matter of the visitor's trust, so we planned the order and the limits as carefully as the questions:
- The business writes its own questions, and the assistant asks them inside the conversation, in the visitor's language.
- A visitor is never asked again for details the business already holds.
- Every set of answers lands in one table the team can work from.
- A visitor's details can be erased completely when they ask.
How it works
With Data Forms, a business writes the questions it needs answered — name, contact details, the project, the budget range, a preferred time to talk — and attaches them to its chatbot. The assistant asks them at the start of a session or when the conversation calls for it.
It reads as a conversation. Questions are asked in the chat, and on messaging apps one at a time, so the visitor answers as part of the conversation they were already having.
It never asks twice. Contact details the business already holds are filled in, so a returning visitor is not asked for their name and email again.
Every lead lands in one table. Each set of answers becomes a row the team can filter and export as CSV. Free-text answers can be stored in one language for the team, with the visitor's own wording kept beside it.
It respects the visitor. A visitor's details and every response they gave can be erased in one action when they ask.
Where it leaves the sales team
A visitor who asks about a service gets an answer, and is then asked whether they would like a quote. The answers they give arrive as a row the team can follow up. The assistant collects what the visitor chooses to share; it does not contact anyone on the team's behalf.
Frequently asked questions
How can a chatbot turn website enquiries into leads?
Attach a Data Form to it. The assistant answers the visitor's questions and asks yours — contact details, needs, timing — and each set of answers becomes a row your team can export.
Will visitors be put off by a form?
The questions are asked inside the conversation, in the visitor's language, and details you already hold are filled in, so it reads as part of the chat.
Can I export the leads?
Yes. Responses can be filtered and exported as CSV.