The moment a chatbot asks for contact details is the most delicate in the conversation. Ask too early and the visitor feels interrogated. Ask too late and they have already left. Ask clumsily and they type a fake number, close the window or lose trust. Yet capturing a contact detail is what turns a chat into a lead, and getting it right is a matter of timing, wording and honesty more than technology. This guide explains when to ask, what to say, whether to ask for a phone number or an email, how to handle refusals, how to validate what visitors give you, what consent you need and what to do with the details once you have them.
The golden rule: give first, ask second
People share details when they see a reason to. The assistant should answer the question first, then offer a next step that needs contact details: a booking, a quote, a callback, a guide by email. The request feels natural when it is the price of something the visitor wants.
| Order | Feels like |
|---|---|
| Ask for name and email before answering anything | A toll gate |
| Answer, then offer a callback and ask for a number | Service |
| Answer, offer to send the price list by email, ask for an email | A fair exchange |
Choose the right detail
| Detail | Best when | Watch for |
|---|---|---|
| Phone number | Urgent or high-value enquiries; callbacks | Some visitors do not want calls; consent and hours |
| Email address | Sending information, quotes or confirmations | Slower response; spam filters |
| Name only | Conversation continuity | Not enough to follow up |
| Preferred contact method | Any enquiry | Respecting the choice |
Ask what the visitor prefers when you can: 'Would you like a call or an email?' Then ask only for that.
When to ask
- When the visitor asks for a callback, a quote, availability or a booking.
- When the conversation cannot be finished in chat and needs a person.
- When the assistant cannot answer and wants to pass the question on.
- After the visitor has shown interest, such as asking about price twice.
- Before the visitor leaves, if they have shown intent and there is a natural pause.
Do not ask in the first message or before the visitor has received any value.
Wording that works
| Weak | Better |
|---|---|
| Enter your email. | I can email you the price list and a link to book. What is the best address? |
| Phone number required. | Would you like a call back today? What number should the team use? |
| Please provide contact details. | So the team can confirm this, what is the best number or email to reach you? |
| Submit your details to continue. | I can hold that time for you. What name should I put it under? |
- Say what the detail is for.
- Keep the ask short.
- Offer a choice of channel.
- Say what happens next: 'Priya will call you within the hour.'
- Thank them, and repeat the detail back for confirmation.
Handle refusals gracefully
Some visitors will decline. Accept it and keep helping. 'No problem, you can also book yourself here, or call us on this number.' A visitor who refuses today may come back tomorrow, and pushing loses them. Offer an alternative route that needs no details: a booking link, a phone number and hours.
Validate without annoying
- Check that an email looks like an email and a number has the right number of digits, and ask kindly to correct it.
- Accept common formats for phone numbers, with or without spaces and country codes.
- Do not reject unusual but valid addresses.
- Confirm by reading it back: 'That is sam@example.com, correct?'
- For bookings, send a confirmation email; a bounce tells you it was wrong.
Fake details usually mean the visitor did not see a reason to share. Improve the reason, not the validation.
Consent and honesty
- Tell visitors they are talking to an AI and link to your privacy policy.
- Say how you will use the detail.
- Do not add people to marketing lists without a separate, clear opt-in.
- For calls or texts, respect the rules on consent where you operate.
- Delete details you do not need.
See chatbot lead capture and privacy law and the GDPR checklist for website chatbots.
What to do with the details
- Deliver the lead instantly to the person who will follow up, with the conversation attached.
- Reply within the time you promised.
- Record the source and outcome.
- Keep it secure and delete it when it is no longer needed.
Crescelo sends leads to your email with instant alerts, and can deliver them to Slack, Google Sheets or webhooks. See the lead capture feature and instant lead routing in chat.
A sample conversation
| Speaker | Mensaje |
|---|---|
| Visitor | How much does a deep clean of a three-bed house cost? |
| Assistant | A deep clean of a three-bedroom house is usually $220 to $290 depending on size and condition, and takes about four hours. Would you like a firm quote? I can have someone call you today, or email you a link to book. Which do you prefer? |
| Visitor | Email is fine. |
| Assistant | Great. What is the best email? I will send the price details and a booking link. |
| Visitor | sam@example.com |
| Assistant | Thanks, Sam. I have sent it to sam@example.com, so please check your inbox. If you would rather talk, our number is on the page. |
Worked example: a cleaning company
A cleaning company's chat asked for name, phone and email in its first message. Most visitors left, and about one in five gave a number that turned out to be wrong. The owner changed the flow: answer first, then offer a quote by email or a call, and ask for only the chosen detail. Chats that ended with contact details rose from about one in ten to about one in four, and wrong details became rare. The same visitors were asked less, and gave more.
| Cambiar | Result (illustrative) |
|---|---|
| Ask after answering | More visitors continue |
| Offer a choice of channel | Higher completion |
| Ask for one detail | Fewer fake details |
| Say what happens next | More trust |
Common mistakes
- Asking in the first message.
- Asking for phone and email and name at once.
- Requiring details to get a price.
- Not saying what will happen next.
- Never following up on leads.
- Adding contacts to newsletters without consent.
Frequently asked questions
When should a chatbot ask for an email or phone number?
After it has answered the question and when a next step needs a contact detail, such as a callback, a quote or a booking.
Should I ask for phone or email?
Ask which the visitor prefers. Phone suits urgent or high-value enquiries; email suits information and quotes.
What if the visitor refuses?
Accept it and offer a route that needs no details, such as a booking link or your phone number.
How do I stop fake details?
Give a clear reason for asking and ask for one detail, and confirm by reading it back or sending a confirmation email.
Do I need consent to collect a contact detail?
You need a lawful basis and transparency. Marketing needs a separate opt-in.
Where do the details go?
To your inbox, and with Crescelo optionally to Slack, Google Sheets or a webhook.
Try a contact capture in the playground, read conversational lead capture and start a free trial.
Further reading
- Google Search Central: creating helpful, people-first content: What Google looks for in useful pages.
RESPONDE A CADA VISITANTE. RESERVA CITA A QUIEN ESTÁ LISTO.
Instala Crescelo en tu sitio web en 15 minutos
Entrena a tu asistente con tus listas de precios, documentos y condiciones de servicio. Activa respuestas basadas en tus fuentes las 24 horas y reservas de citas en el chat sin solapamientos.