A visitor lands on a kitchen fitter's website at 9pm and types a simple question: roughly how much does a new worktop cost? The assistant replies, "Great question! Before I help, can I take your name, email and phone number?" The visitor closes the tab.
Nothing about that request was unreasonable on paper. The business does need details to quote. But the order was wrong, the reason was missing and three fields at once felt like a form wearing a friendly hat.
When you set up a chatbot to collect contact details, the wording and the timing matter more than the fields you pick.
The value exchange, in plain terms
People give details when they can see what they get back. "Can I take your email?" offers nothing. "I can have Dan send a proper quote tomorrow morning, what is the best email for that?" offers a quote, a name and a time.
A quick test for any request you write: read it aloud and ask what the visitor gains by answering. If the honest answer is "they get added to our list", rewrite it.
Good exchanges usually fall into a few types:
- A specific follow-up. A quote, a callback, a site visit, a sample.
- A copy of something. The answer they just got, a brochure, a price sheet.
- A place in a queue. A booking request passed to the team with their preferred times.
- Help the assistant cannot give. A person who can look at their account or their photos.
Timing: when to ask
The rough rule is to ask once the visitor has signalled intent, not the moment they arrive. Here is how that plays out across typical moments in a chat.
| Moment in the conversation | Ask for details? | Why |
|---|---|---|
| First message, general question | No | They have not decided you are worth talking to yet |
| After a price range has been given | Offer, lightly | They are weighing it up; a quote is a natural next step |
| They ask about availability or dates | Yes | They are planning, and you need a way to confirm |
| The assistant cannot answer | Yes | Capturing the enquiry is better than a dead end |
| They mention a problem with an order or job | Yes | You need to find them to fix it |
| They say they are just browsing | No | Point to useful pages and leave the door open |
Requests that feel like a trap
Some wording puts people on guard even when the intent is harmless. These are the patterns to remove from your assistant's instructions.
Visitor: Do you do boiler servicing in Leeds? Assistant: I can help with that! Please enter your full name, email address, phone number and postcode to continue.
This gates a yes-or-no answer behind four fields. The visitor does not yet know if you cover their area.
Visitor: What does a deep clean cost? Assistant: Prices vary. Leave your number and someone will call you to discuss.
This withholds information the business could have shared, and swaps it for a sales call nobody asked for. If you have a price range, give it.
Also watch for fake urgency ("only two slots left, enter your email now"), asking for a phone number when the team only ever replies by email, and asking again after the visitor has already said no.
Requests that tend to work
Compare the same visitor with a better sequence.
Visitor: Do you do boiler servicing in Leeds? Assistant: Yes, we cover Leeds and most of West Yorkshire. A standard annual service is usually between £80 and £110 depending on the boiler. Would you like us to get in touch to arrange a date? Visitor: Yes please. Assistant: Lovely. What is the best phone number for the team to reach you on? They usually call back within the working day. Visitor: 07700 900123 Assistant: Thanks. And roughly how old is the boiler, if you know? It helps them bring the right parts.
The answer came first. The request was tied to a callback. It asked for one detail, then used the next question to make the visit better rather than to fill a database. (The prices are an example; your assistant should only quote ranges that are in your own content.)
A few habits sit behind replies like that:
- Answer the question in full before any request.
- Ask for one detail per message.
- Say who will get in touch and roughly when, only if that is true.
- Ask only for what the follow-up needs. A callback needs a number and a name, not a postcode and company size.
- Accept a no gracefully and keep helping.
For more on getting the first line right, see building trust in the first message.
Which details to ask for
Every extra field costs you some visitors. Decide the minimum set by working backwards from what your team actually does next.
If the next step is a phone call, you need a name and a number. If it is an emailed quote, you need a name, an email and the job details. If it is a booking request, you need preferred days and a way to confirm. Company name, job title and budget are worth asking only when your process genuinely changes based on them.
Once captured, the details reach you with the conversation attached, so your reply can pick up where the chat left off. Our guide to writing the follow-up email after a chat covers that part. If a visitor would rather fill in a short structured form than chat, a simple form is a reasonable alternative to offer.
Handling the visitor who says no
Some people will not share details, and that is their right. The worst response is to ask again in the next message. The second worst is to go quiet.
A decent reply sounds like: "No problem. If you want to pick it up later, the contact page has our number, and you are welcome to ask me anything else in the meantime." Then keep answering their questions. Visitors who were not pushed are more likely to come back when they are ready.
What to do next
Open your assistant's lead capture instructions and read every request aloud. Cut any that ask before answering, bundle several fields together, or give no reason. Rewrite each one to name the thing the visitor gets back.
Then look at your last twenty conversations where someone left without sharing details and find the message where they dropped off. That message is usually the one to fix first. If you want help drafting alternatives, the reply generator is a quick way to try a few wordings side by side.