Chatbot Lead Qualification Questions: 30 Examples (No Form Wall)

Lead-qualification advice for chatbots often borrows the sales call: budget, authority, need and timeline, asked up front, often in a form before the visitor types a word. But a website visitor opened the chat with a question of their own, and every question asked before answering it is a reason to close the window.

This guide is for founders, service businesses, coaches and course creators who use a website chat to find buyers. It gives 30 qualifying questions sorted by what each one tells you, when to ask them, how to phrase them, what to leave out and where the answers go. The case against form walls and the capture flow itself are in the AI chatbot lead generation guide; this page is the question bank that goes with it.

PepoChat is our product; its lead capture behaviour below was checked in its code and documentation on 22 October 2026, and every study and regulator page cited was read the same day. The questions work in any chatbot whose instructions you can edit.

What is a lead qualification question?

A lead qualification question is a question a chatbot asks to decide whether a visitor should be followed up, how fast and by whom, such as "Roughly how many people would use it?" or "When do you need this running?" Qualification is a different job from lead capture, which is getting a way to reach the visitor, usually an email address.

The classic sales checklist is BANT, short for budget, authority, need and timeline: four things a salesperson confirms before spending time on a deal. BANT is a sound list of topics and a poor running order for a chat. A visitor who asks whether you work with Shopify has already stated their need, and asking for their budget next turns help into a sales funnel.

In a chat the order changes. Need comes first, because the visitor brought it. Fit comes next, meaning size, platform or location, because it decides which answer is right. Timeline and urgency tell you how fast to follow up, authority tells you who to invite to the call, and budget comes last or waits for the call. The 30 questions below follow that order and add two groups BANT leaves out: the visitor's current setup, and how they want to be contacted.

Should a chatbot use a pre-chat form or ask in the conversation?

A chatbot should ask qualifying questions inside the conversation, after it has helped, and keep a pre-chat form for pages where nearly every chat is a sales or intake request, because people share more once they have received something. A pre-chat form is a set of fields a visitor must fill in before the first message can be sent: the form wall of chat.

The order of asking matters more than the number of fields. In a 2007 study, Luciano Gamberini and colleagues at the University of Padova asked visitors to a website of guidelines on managing multimedia files for their contact details, either before they could read the guidelines or after. Nielsen Norman Group's summary of the study reports that people gave out more information when asked afterwards, while asking first drew more form submissions. A gate collects more forms; helping first collects fuller ones.

Conversation also draws better answers to open questions. In a 2020 field study in ACM Transactions on Computer-Human Interaction, Ziang Xiao and colleagues gave about 600 people the same mostly open-ended survey, half as a Qualtrics form and half through an AI chatbot that probed their answers. Across more than 5,200 free-text responses, the chatbot version drew significantly higher engagement and answers rated more informative, relevant, specific and clear. Four of the seven authors worked at Juji, whose chatbot was tested.

We found no published study, with its method stated, that measures how many chat visitors a pre-chat form turns away, so this guide relies on the research above instead. A form still earns its place on a demo or quote page, in regulated intake and on a widget flooded with junk chats, as the table shows.

What should a chatbot ask before the chat starts?

Before the chat starts, a chatbot should ask nothing, or at most an email plus one field that changes who replies, such as company for a B2B sales team, because every field is asked before the visitor has been helped.

Routing does not need a field. Two or three suggested questions under the greeting, such as "See pricing", "I'm a customer and need help" and "Book a call", sort visitors by intent with one tap, and the tap becomes the first message. In PepoChat you can set up to three suggestions under the required greeting.

As of October 2026, choosing Before the first message under PepoChat's Lead Capture shows a "Before we start" card with a required email and at most one more field: the first of name, phone or company that you ticked, in that order. There is no custom question field, so a routing question such as "What brings you here?" belongs in the greeting or the suggestions. The optional consent text, up to 300 characters, appears under that form and nowhere else.

The other two timings move the ask into the conversation: When the agent needs a follow-up asks before a reply that needs a person to get back to the visitor, and Before handing off to the team asks right before a human handoff. Either way the agent asks once, only for the fields you ticked, and keeps helping if the visitor declines.

When should a chatbot ask each qualifying question?

A chatbot should ask each qualifying question right after it has answered something, one question per message, in the order need, fit, timeline, authority and budget, and should stop after about three unless the visitor keeps volunteering more. Eight rules cover nearly every case.

1. Answer first. Every question follows an answer. A visitor who asks about pricing gets the prices, then "Roughly how many people would use it? That decides which plan fits." The answer is what pays for the question.
2. One question per message. Two questions in one message get one answer, usually to the easier one. PepoChat's base rules already tell its agent to ask one question at a time.
3. Give the reason in the same sentence. "What's the ZIP code, so I can check we cover your area?" In Baymard Institute's checkout research, some shoppers asked for a phone number with no reason given assumed it was for marketing, and some typed a fake number.
4. Offer choices for sizes and dates, and keep the need open. "Just you, 2 to 10 people, or more?" is quicker to answer than "How many users?" The need question stays open, because the visitor's own words are what your follow-up should quote back.
5. Never ask what the visitor already said. If the first message was "We're a 12-person agency on WordPress", size and platform are answered. Asking again tells the visitor nobody read it.
6. Stop at a no. A visitor who ignores a question or says they are just browsing has answered. Keep helping; PepoChat's agent asks for contact details once and never re-asks after a decline.
7. Ask for the email last. The email is the one detail a follow-up needs and the one visitors guard most, so ask only when a follow-up is genuinely needed. In PepoChat, lead capture asks it for you, and when Team availability says nobody can reply live, the agent asks once before handing over even with lead capture off.
8. Stop at three. Three questions after three answers is a conversation; six is an interview. Leave the rest for the follow-up call.

What are the best lead qualification questions for a chatbot? 30 examples

The best lead qualification questions for a chatbot are short, follow an answer and change what happens next; the 30 below are grouped by what each one tells you, with when to ask it and the businesses it suits best.

Reword them in your own voice, keep the reason clauses, and choose two or three per page rather than all 30. The coaches and consultants guide shows a persona prompt built on two of them that ends in a discovery call. In PepoChat, lead capture asks question 28 for you once it is switched on, so it needs no instruction of its own.

Need and intent questions

Need questions find out what the visitor is trying to get done, in their own words.

Fit and size questions

Fit questions decide which plan, package or service is right and whether you serve the visitor at all; offer ranges, not exact numbers.

Current setup questions

Setup questions tell you what the visitor would switch from and what your team must support.

Timeline and urgency questions

Timeline questions tell you how fast to follow up, so ask them once the visitor shows buying interest.

Authority questions

Authority questions tell you who else belongs on the call; ask them before booking a demo, never as an opener.

Budget questions

Budget questions are the ones visitors skip most often, so ask them last, as a range anchored on your own prices.

Contact and source questions

Contact questions come last because they are worth asking only when someone will follow up; the source question is optional.

All 30 questions were written for this guide on 22 October 2026; the timings follow the eight rules above.

How do you make qualifying questions sound like a conversation, not a form?

Qualifying questions sound like a conversation when each one acknowledges what the visitor just said, gives a reason and offers an easy answer; the same question asked cold, or bundled with three others, reads as a form. Compare two openings for a cleaning company:

Form-style
Bot: Before I can help, please share your name, email, phone number, ZIP code and budget.

Conversation-style
Visitor: Do you do move-out cleaning?
Bot: Yes. A move-out clean covers the oven, the inside of cupboards and the windows. What's the ZIP code, so I can check we cover your area?
Visitor: 78704
Bot: We cover 78704. Roughly how many bedrooms is the place? That sets the price.
Visitor: Two, and I hand the keys back on the 28th.
Bot: A two-bedroom move-out clean fits on the 28th if you book this week. Would you like the quote by email?

The second version asks two questions, each after the visitor got something, and skips the date because the visitor volunteered it.

In PepoChat, the order and wording go into the How to sound and behave field of the agent instructions (up to 4,000 characters) and the refusals into Never do this (up to 2,000):

When a visitor asks about a quote or a booking, qualify them in the conversation:
- Answer their question first, then ask one question per message.
- Ask in this order, skipping anything they already told you: the type of clean, the ZIP code, the number of bedrooms, the date.
- Give the reason in the same sentence, for example "so I can check we cover your area".
- Ask at most three of these. If they decline or change the subject, stop and keep helping.
- Do not ask about budget; the quote covers price.

Never ask for card numbers, bank details, passwords or ID numbers.
Never ask about health, age, religion, ethnicity or family status.

The agent still follows its base rules: it searches your knowledge base first and never invents an answer, so a qualifying question never replaces the reply it follows. After saving, test the block in the Test the agent drawer as a vague visitor, a ready buyer and an existing customer; test chats are free and never create contacts.

Which questions should a chatbot never ask?

A chatbot should never ask for passwords, full card or bank numbers, government ID numbers, health details or details about a child, and should ask for a phone number only when someone will actually call it.

Data minimisation is the rule that personal data must be "adequate, relevant and limited to what is necessary" for the purpose it is collected for. The UK regulator's guide to the principle reads like chatbot advice: identify "the minimum amount of personal data you need to fulfil your purpose", and do not collect data "on the off-chance that it might be useful in the future". Its example of excess is a recruitment agency asking every applicant health questions that matter only for some manual jobs, which is "irrelevant and excessive" for someone applying for an office job.

That is where a conversation beats a form. A form asks everyone the same fields; a chatbot can ask for the ZIP code only from people who want a visit, and for team size only from people asking about team plans. The ICO's guidance makes the same point: information needed about certain people only should be collected "just for those individuals".

Four kinds of question deserve a hard no in a sales chat:

• Health. A clinic's chat can book the appointment; the medical history belongs in the clinic's own intake, not a chat transcript.
• Money beyond a budget range. A B2B budget band is an ordinary sales question; income, debts, credit scores and account numbers are not.
• Children. For tutoring, schools and kids' activities, ask the parent for their email and the child's year group, not the child's name, birthday or school.
• Protected characteristics. Family status, religion and national origin have no place in qualification, and in housing they raise fair housing problems; the real estate chatbot guide lists what an agency's bot must never ask.

Phone numbers need the most care. In Baymard's 2025 quantitative study of 1,026 online shoppers, 14% were reluctant to give a phone number, and 39% of the sites in its benchmark required one without explaining why. Ask for a number only when a person will call, and say so in the question.

Marketing calls are regulated separately. In the UK, marketing calls to numbers registered with the Telephone Preference Service need the person's specific consent, according to the ICO's telephone marketing guidance. In the US, prerecorded telemarketing calls need a signed written agreement, which the FTC's Telemarketing Sales Rule guide says a website form can collect. This is general information, not legal advice.

Say what the details are for where you ask for them. PepoChat's consent text appears only under the pre-chat form, so when the agent asks in the conversation, your privacy policy has to carry the notice; the privacy notice templates include lines you can paste.

Where should the answers to qualifying questions go?

Qualifying answers should land where the person who follows up already looks: contact details on a contact record, the qualifying answers in the conversation or a CRM note, and a short alert in Slack or email.

Checked in PepoChat's code and documentation on 22 October 2026.

The gap to plan for: PepoChat's contact record holds the four contact fields, the source and the visit times, while qualifying answers stay in the transcript; the new-lead webhook carries the contact and a link to the conversation, not the answers.

To send the answers on as data, use an action. The prebuilt Send to Zapier action posts event, customer_name, customer_email and details; edit the description of details so the agent's summary includes the need, size and timeline. A custom action can post named inputs such as team_size, up to 10, but every input is required, so the agent asks for any it lacks. The Zapier guide maps each field and shows how to stop duplicate rows.

Rule-based bots handle this part better. HubSpot's chatflow bots can ask a question and save the reply to a contact property, skipping the question when that property is already filled, according to HubSpot's knowledge base in October 2026. The trade-off is the script: a rule-based bot follows the flow you built rather than answering whatever the visitor asked first. An AI support agent answers the real question and asks around it, but its qualifying answers arrive as text that a person or an automation has to read.

Does a chatbot need lead scoring?

A small team does not need a lead-scoring engine for chat leads: two or three qualifying answers and a three-tier rule (reply today, reply this week, not a sales lead) sort them faster than points do.

Lead scoring is giving each lead points for who they are and what they have done, so sales works the highest scores first. HubSpot's knowledge base describes fit scores built from properties such as region, company size and industry, and engagement scores built from actions, and lists lead scores on the Professional and Enterprise tiers of Marketing Hub and Sales Hub. Scoring pays off when hundreds of leads a week compete for a sales team's time.

PepoChat has no lead-scoring engine, as of October 2026. Each contact carries its source (pre-chat form, chat, verified email or booking) and a link to its conversation, and a booking is the strongest signal a chat produces, because the visitor picked a time themselves.

What to do next

• Choose three questions from the bank, one need, one fit and one timeline, and add them to your chatbot's instructions in that order; the agent instructions docs show where each line goes in PepoChat.
• Turn on a new-lead alert in Slack or a webhook, agree who replies to the "reply today" tier, and use the HubSpot and Salesforce guide to push qualified leads into your CRM.
• Create a free workspace to try it on your own content: lead capture, the Slack card and the webhook are on every plan, and new-lead emails start on Starter.