The best lead qualification questions for website chat are the ones a visitor can answer in a tap or a few words, and whose answers change what you do next. Start with a universal core (what they need, how big it is, when they need it, and how to reach them), then add one or two questions specific to your industry. Ask three to five in total. If an answer wouldn't change how you route, prioritize or reply, cut the question.
This page is a question bank. For the step-by-step build (branches, handoff, testing), see our guide to building a lead qualification chatbot.
The universal core
These four questions work in almost any business:
| Question | Answer type | What it decides |
|---|---|---|
| What can we help you with? | Buttons | Which path the visitor takes (sales, support, browsing) |
| How big is the job? (team size, project size, number of items) | Buttons or number | Priority and who should respond |
| When do you need this? | Buttons | Whether someone should reply now or later |
| What's the best email to reach you? | Follow-up, especially when nobody's online |
Everything else is optional. Add a question only when you can complete the sentence "If they answer X, we'll do Y."
How to pick your questions
A quick process that works for any industry:
- Write your outcomes first. For example: book a call now, send a quote by email, send to support, point to resources.
- List the facts that sort visitors into those outcomes. Usually need, size and timing.
- Choose answer types. Buttons for anything that fits a short list, number for thresholds you'll compare, email for contact details, free text only where nuance matters.
- Order them easy-first. Intent first, contact details last, once the visitor has seen some value.
- Add a "Not sure yet" option to any question that might stall people.
Question banks by industry
Each bank below gives more questions than you need. Pick the ones that change your routing. Variable names are suggestions; use short, lowercase names you'll recognize later.
Marketing, design and web agencies
| Question | Answer type | Variable | Use it to |
|---|---|---|---|
| What kind of project is it? (Website / Branding / Ongoing marketing / Not sure) | Buttons | service |
Route to the right specialist |
| Is this a new project or a change to something existing? | Buttons | project_type |
Set expectations on scope |
| What budget range are you working with? | Buttons | budget |
Separate small requests from priority leads |
| When would you like to start? | Buttons | timeline |
Prioritize near-term projects |
| Are you choosing for your own business or for a client? | Buttons | buyer |
Spot partner or white-label inquiries |
Home services and trades
| Question | Answer type | Variable | Use it to |
|---|---|---|---|
| What do you need help with? (Repair / Installation / Quote / Emergency) | Buttons | job |
Send emergencies to a person or phone line first |
| What's your ZIP code or area? | Text | area |
Check you serve that location |
| How soon do you need someone? | Buttons | urgency |
Prioritize this-week jobs |
| Is it a home or a business property? | Buttons | property |
Route to residential or commercial |
| What's the best phone number for scheduling? | Phone | phone |
Book the visit |
Ask for the area early. A visitor outside your service area deserves a polite answer before they've typed out their whole problem.
Clinics, salons and wellness businesses
| Question | Answer type | Variable | Use it to |
|---|---|---|---|
| What would you like to book? (one button per service) | Buttons | service |
Send to the right booking path |
| Are you a new or existing client? | Buttons | client_type |
Show first-visit information |
| Which days or times suit you? | Buttons | availability |
Help the team offer slots |
| What's the best email or phone number to confirm? | Email or phone | email / phone |
Confirm the appointment |
Keep health and personal details out of the chat. Ask what service someone wants, not why they need it. Our guide on chatbot variables shows how to skip the client-type question for returning visitors.
Accounting, legal and consulting firms
| Question | Answer type | Variable | Use it to |
|---|---|---|---|
| What area do you need help with? (one button per practice area) | Buttons | practice |
Route to the right person |
| Is this for you personally or for a business? | Buttons | client_kind |
Separate personal from business work |
| How large is the business? | Buttons | company_size |
Match to the right service level |
| Is there a deadline we should know about? | Buttons | deadline |
Flag time-sensitive matters |
Don't ask visitors to describe confidential details in a website chat. Collect the topic and a contact method, and discuss specifics properly once you've been engaged.
B2B software and SaaS
| Question | Answer type | Variable | Use it to |
|---|---|---|---|
| What brings you here? (Pricing / Demo / Support / Just looking) | Buttons | intent |
Keep support away from sales questions |
| How many people would use it? | Number | team_size |
Route larger teams to sales |
| What are you using today? (A tool / Spreadsheets / Nothing yet) | Buttons | current_setup |
Shape the first conversation |
| When are you hoping to decide? | Buttons | timeline |
Prioritize active evaluations |
| What's your work email? | email |
Follow up |
Training, coaching and courses
| Question | Answer type | Variable | Use it to |
|---|---|---|---|
| Is this for you or for a team? | Buttons | audience |
Separate individual and group sales |
| Which program are you interested in? | Buttons | program |
Send relevant details |
| How many people would take part? | Number | seats |
Route group inquiries to a person |
| When would you like to start? | Buttons | start |
Point to the next intake or date |
How to word the sensitive questions
Budget, company size and timelines can feel intrusive. A few wording rules help:
- Say why you're asking: "So we can suggest the right option, what budget range are you working with?"
- Use ranges, not exact numbers. "Under $5k / $5k–$15k / Over $15k" is easier to answer than an open box.
- Always include an escape: "Not sure yet" or "Rather not say" keeps people moving.
- Ask after you've helped a little. A visitor who has already picked a service is more willing to share scope.
Turning answers into routing
Questions only qualify leads when answers drive decisions. Typical rules look like this:
- IF
urgencyis "Emergency" → hand off to a person now. - IF
team_sizeis greater than your threshold → hand off to sales. - IF
budgetis "Not sure yet" → share a pricing guide and ask for an email. - ELSE → confirm a follow-up by email.
Two practical tips: make any question you'll compare numerically a number question, and remember that a button answer is saved as the button's label, so a condition must match that label exactly (case doesn't matter). The variables and conditions reference lists every rule you can use.
Mistakes to avoid
- Asking every question in the bank. Three to five is plenty for most businesses.
- Leading with contact details. Ask for the email once the visitor knows what they'll get.
- Qualifying existing customers. Send support requests straight to help.
- Dead ends for "unqualified" leads. Give them something useful: a resource, an answer, or a promise to follow up.
- Free text where buttons would do. Typed answers are harder to branch on and slower to give.
For more on keeping visitors engaged from the first question to the last, see our chatbot flow best practices.
How to do this in RetroChat
In RetroChat's no-code flow builder, each question can take a quick-reply choice, text, email, phone or number answer, and the answer is saved to the variable you name. Condition steps branch with IF/ELSE rules such as is, contains, is greater than, is less than and is set, and a hand-off step brings in a person when the answers say it's worth it. The Lead capture template is a good starting point: it collects a name, email and interest, then qualifies by budget, and you can swap in the questions for your industry.
Everything the bot collects appears on the contact's profile next to the conversation, so whoever takes over never asks again. On Team plans and above, you can export contacts to CSV.
Pick your five questions
Choose the universal core, add one or two from your industry's bank, and build the flow this week. You can test it with real visitors in a free 14-day RetroChat trial, no credit card required.
Frequently asked questions
What are the most important lead qualification questions?
Need, size and timing, plus a way to follow up. What does the visitor want, how big is the job, when do they need it, and what's the best email or phone number? Most other questions are refinements of these.
How many qualifying questions should a website chat ask?
Three to five, including the contact question. Each extra question is another chance for the visitor to leave, so keep only the ones that change your routing or response.
Should I ask about budget in a chatbot?
Only if budget changes what you do next, such as who responds or which option you suggest. Use ranges as buttons, explain why you're asking, and include a "Not sure yet" option.
Are BANT questions still useful for chat?
Budget, authority, need and timeline make a good checklist, but a website chat isn't a sales call. Need and timeline usually matter most in chat; authority and detailed budget are often better left for the follow-up conversation.