If you are still weighing whether to qualify at all, start with Stop Wasting Free Consultations on Bad-Fit Leads, which covers the why and the cost of taking every call. This guide assumes you are sold on the idea and just need the questions.
The one test for a good qualifying question
Before you write a single question, run it through one test: would you actually say no to a booking based on the answer? If the answer is no, the question does not belong in your qualifying flow. It belongs in the form they fill out after they book.
A good qualifying question is tied to a real decision. "What's your monthly ad spend?" with a $5,000 floor changes what happens next. "What's your company name?" does not. The first routes the visitor toward booking or a polite decline. The second is just data you could collect any time.
The three answer formats that work
A chatbot has to score the answer, so the answer has to be something it can read cleanly. Three formats do that reliably:
- Yes or no. One clear accepting answer. "Are you pre-approved with a lender?" accepts "yes."
- A minimum number. The bot compares the answer to a threshold you set. "What's your monthly ad spend?" accepts $5,000 or more.
- A value from a fixed list. You define the buckets and which ones qualify. "What's your timeline?" with "this month," "this quarter," or "just browsing," where the first two accept.
Free text is deliberately not an option. "Tell us about your project" produces a paragraph the bot cannot score consistently, so the outcome becomes a judgment call instead of a clean yes or no. Every qualifying answer should be a tap or a short, structured reply.
Question recipes by business type
The structure stays the same across verticals: one to three short questions, each tied to a real decision, asked only when the visitor wants a commitment. The questions change. Pick the one or two that actually route your bookings.
Marketing agency offering a free audit or strategy call
Question: "What's your monthly ad spend?" min number
Accepting answer: $5,000 or more.
Polite decline: "We usually work with $5k+ monthly spend, so we may not be the right fit yet. Here's a DIY toolkit that can help you get there."
Contractor or home services offering a free estimate
Question: "What's your budget range for this project?" fixed list
Accepting answer: "$5k to $20k" or "$20k+" (not "under $5k").
Polite decline: "We focus on projects $5k and up. Here's a planning guide for smaller jobs, and reach back out when you're ready for a bigger one."
Consultant or coach offering a free discovery call
Question: "What stage is your business in?" fixed list
Accepting answer: "Established with revenue" (not "pre-revenue").
Polite decline: "Most of our clients are past their first revenue. Here's a free starter resource, and we'd love to talk once you're there."
Real estate agent offering showings
Question: "Are you pre-approved or working with a lender?" yes / no
Accepting answer: "yes."
Polite decline: "Showings go fastest once you're pre-approved. Here's a first-time-buyer guide, and I'll keep an eye out for you."
Fitness studio or coach offering a free intro session
Question: "When are you looking to start?" fixed list
Accepting answer: "this week" or "this month" (not "just exploring").
Polite decline: "No rush. Here's a free at-home starter, and grab a session whenever you're ready to commit."
B2B or SaaS offering a demo
Question: "How many people are on your team?" min number
Accepting answer: 10 or more (set this to wherever your product fits).
Polite decline: "Our self-serve plan is a better fit for smaller teams. Here's the link to get started today."
What a not-a-fit turn looks like
The visitor still gets a real answer, still gives you their contact info, and still leaves with something useful. The lead lands either way. Here is the decline path, end to end.
The contact turn comes first. The lead and the outcome badge follow the email, not the qualifying answer.
Phrase it as help, not an interrogation
The same question can feel like preparation or like a bouncer at the door. The difference is framing and timing.
- Frame it as making the deliverable better. "So the audit is actually useful, what's your monthly ad spend?" beats "What's your budget?" asked cold.
- Ask at the commitment moment, not on hello. Qualifying should fire when the visitor asks for the audit, the quote, or the call, never on their first message.
- Use a proxy when the direct question feels blunt. "What's the size of the project?" lands softer than "Do you have the budget?" and gives you the same routing signal.
Common mistakes
- Collecting a number you won't act on. Asking budget without a threshold is theater. The visitor answers, the bot books them anyway, and you both discover the mismatch on the call.
- Using free text. If the bot can't score it, it can't route it. Keep answers to yes/no, a number, or a fixed list.
- Asking too many. One to three questions feel like the team being thoughtful. Five feels like a form, even though the system allows up to five.
- Firing on every visitor. Someone asking your hours should never get qualified. Save it for commitment requests.
How Simple Business Bots handles this
On the Premium plan, this runs as a feature called Fit Check. You define one to five qualifying questions in the dashboard, each as a yes/no, a minimum number, or a fixed list. The questions fire only when a visitor signals a commitment, such as asking about pricing, a free audit, a consultation, or a quote. The bot asks them one at a time, then collects the visitor's name and email and computes a Qualified, Not a fit, or Needs review outcome.
Qualified visitors see your booking link by default, or clickable Google Calendar slots right in the chat if you connect your calendar. Visitors who don't fit get the polite decline you wrote, plus an optional helpful link. Either way the lead lands in your dashboard with the full conversation, the contact info, and a colored outcome badge, so you get a meeting list instead of a triage queue.
Fit Check is widget-only, and medical and legal industries are excluded for compliance reasons.