Skip to content
Supa Brain

A common chatbot mistake

Your chatbot won’t answer until the customer hands over their details

Asked a question your FAQ answers in public, the bot asks for a name, email or phone number first. Most visitors close the chat.

Lead capture is a reasonable goal. But when the bot holds back published answers until it gets an email address, the visitor who just wanted your opening hours leaves.

We never give personal data to the bots we test. When a bot insists, that’s where our test, and most customers’ patience, ends.

Do you install batteries as well as panels?

Before I can help, can I get your name and email?

Your page says

Yes, battery installation is on the services page

Services page

Name and email firstA mistake we found in a live bot, retold with a made-up business.

Why it happens

It isn’t random

01

Lead form before the answer

Many builders put a contact form at the start of every flow by default.

02

No exception for simple questions

The bot treats “what are your hours” like a sales enquiry.

What it costs you

  • Visitors who wanted a quick answer leave, and you don’t get the lead either.
  • In the EU and the UK, asking for personal data you don’t need for the request sits badly with data minimisation rules.

How we check

  1. 01We ask questions your site already answers in public and note where the bot asks for details instead of answering.

What the fix looks like

  • Answer published questions first; ask for contact details only when the customer wants a quote or a call back.

Where we see it

Other mistakes we find

See your assistant answer your customers first

Email us your store’s address. Within a working day you get five questions your customers ask and the answers your assistant would give, each with the page it comes from. Free, no call needed.