30 Chatbot Lead Qualification Questions for B2B SaaS (With Scripts)
Most advice about chatbot lead qualification questions stops at a category list: ask about budget, ask about authority, ask about timeline. Useful as a reminder, useless at 11pm on a Tuesday when a visitor on your pricing page types “does this work for a team of 40?” and your widget has to decide what to say next. The pages ranking for this query publish a handful of question stems per bucket or a few scripted flows, and the response-time statistics they lean on either carry no link at all or trace back to sources that do not exist - checked on July 29, 2026. None of them pairs a full library with data you can follow to its origin.
So here is what they are missing: a real library. Thirty questions a B2B SaaS buyer will actually answer in a chat window, what each reveals, how to score the answer, and what happens next - plus three complete conversation scripts and the handoff rules that keep it honest.
Read the number 30 correctly. It is a library you draw four to six questions from, not a script you run end to end. Nobody answers thirty questions in a chat window. The library exists so the four you ask on your pricing page differ from the four you ask in your docs, and so every one of them feeds something downstream.
One scoping note: where to put the widget is a separate decision, and we covered it in AI chat for B2B SaaS. This post is what it should ask once it is there.
What a chat can ask that a form cannot
The reflex when you see a 30-question library is “that is too many, short forms convert better.” The data does not support the reflex. In RevenueHero’s 2026 demo funnel benchmarks, drawn from more than a million inbound form submissions across a full year, top performers converted at 77% with two fields and 76% with thirteen fields. Their conclusion: “The number of fields doesn’t matter. What matters is whether each field does something useful for routing, qualification, or personalization.” (RevenueHero sells inbound conversion software and all that data flowed through their product, which self-selects for teams already paying attention here - treat it as directional vendor data.)
Quantity is the wrong variable. Sequence and earned context are the right ones, and that is what a conversation has and a form does not:
- It can answer before it asks. A form demands five fields before giving anything back. A chat resolves the blocking question first - “does this handle SSO on the Growth plan?” - so the next question lands as conversation, not as a toll.
- It can branch. The docs reader and the pricing reader are different people with different jobs. One form serves both badly.
- It can ask awkward things gently. “Are you the one who’ll make the call, or gathering options for the team?” is a normal sentence in a chat and an insulting radio button on a form.
- It can stop. Poor-fit answers end the conversation helpfully instead of adding another record to your CRM. Aggressive disqualification is not the risk people fear: in the same dataset, enterprise-segment companies disqualified 71.2% of leads and still converted the remainder to meetings at 70.1%, against SMB teams disqualifying 21.8% and converting 63.2%.
That is the house distinction we keep coming back to in lead qualification software: scoring guesses, routing distributes, forms filter, and conversation asks. Peer-reviewed research points the same way - conversational capture beats static forms on lead volume and quality - and the sources are laid out in our fact-checked chat statistics.
The frameworks your sales team already uses - BANT, MEDDIC and their descendants - are a reasonable skeleton, and HubSpot publishes a solid BANT primer. But HubSpot also wrote the sentence explaining why a chat needs its own library: buyers today “have identified their own needs, and started to design their own solutions” before they ever talk to a salesperson, so “BANT isn’t good enough anymore”. The buyer research agrees. In 6sense’s B2B Buyer Experience Report, a vendor study of 2,509 recent B2B buyers, 81% had already picked a preferred vendor before speaking to a rep. Opening with “do you have budget?” asks a buyer that far along something they settled privately weeks ago.
The 30-question library
Organized under the five signals that decide fit for B2B SaaS - team size, use case, role, current tool, timeline - plus a sixth bucket for budget and procurement. This is our framework - a judgment call about what actually routes and qualifies, not a research finding. Score each answer Hot, Warm, or Cold against your own ideal customer profile; the bands below are illustrative.
Team and company size (questions 1-4)
| # | Question | What it reveals | Scoring | Handoff rule |
|---|---|---|---|---|
| 1 | ”How many people would be using this day to day?” | Seat count, plan tier, deal size | Hot: at or above your target seat band. Cold: a single user on a self-serve tier | Cold answers get the self-serve signup link, not a meeting |
| 2 | ”Is this for one team, or the whole company?” | Land-and-expand shape | Hot: company-wide. Warm: one team with a named second team | Company-wide answers go to your senior rep, not the queue |
| 3 | ”Roughly how big is the company overall?” | Segment (SMB, mid-market, enterprise) | Hot: your core segment. Cold: two orders of magnitude off | Enterprise answers trigger the security and procurement branch |
| 4 | ”Are you looking for yourself first, or planning a team rollout?” | Self-serve versus sales-assisted motion | Hot: rollout. Warm: an individual with a team behind them | Self-serve intent should never be forced into a demo |
Use case and problem (questions 5-10)
| # | Question | What it reveals | Scoring | Handoff rule |
|---|---|---|---|---|
| 5 | ”What are you trying to fix?” | The pain in their own words - the most valuable field we capture | Hot: a use case you win. Cold: a use case you lose | Store the verbatim answer on the lead record; do not summarize it away |
| 6 | ”What does that look like today?” | The manual workaround, and how much it hurts | Hot: spreadsheets, contractors, or a person doing it by hand | A vivid workaround answer is your rep’s opening line |
| 7 | ”Closest match: A, B, or C?” (three of your real use cases as tap options) | Routing, in one tap, with no typing | Hot: your strongest use case. Cold: “none of these" | "None of these” routes to a human before anything is promised |
| 8 | ”What would have to be true in 90 days for this to have been worth it?” | Success criteria, and whether they are achievable | Hot: a metric you move. Cold: an outcome you do not control | Unachievable criteria are a disqualification, not a challenge |
| 9 | ”Is there anything this has to integrate with?” | Technical blockers, before a demo gets wasted | Hot: an integration you ship. Cold: one you do not | Unsupported integrations go to a human before any meeting is offered |
| 10 | ”Roughly what volume are you dealing with a month?” | Sizing, pricing tier, and whether you can carry it | Hot: inside your supported band. Cold: above your ceiling | Above-ceiling volume gets an honest “not yet,” said immediately |
Role and decision (questions 11-15)
| # | Question | What it reveals | Scoring | Handoff rule |
|---|---|---|---|---|
| 11 | ”Are you the one who’ll make the call on this, or gathering options for the team?” | Authority, without the word “authority” | Hot: decision maker. Warm: an evaluator with a named owner | Evaluators get enablement material, not a closing push |
| 12 | ”What’s your role on the team?” | Routing and message fit | Hot: your buyer persona. Warm: an adjacent function | Route by function; an engineer and a VP need different first calls |
| 13 | ”Who else will want a look before this goes ahead?” | The rest of the buying group | Hot: names finance, security, or an exec sponsor | More than three named stakeholders means a longer cycle - flag it |
| 14 | ”Has anyone above you already agreed this needs solving?” | Internal mandate versus personal curiosity | Hot: yes, with a name attached | An existing mandate justifies a same-week meeting |
| 15 | ”Would it help if I sent something you can forward internally?” | Champion enablement, and a natural email capture | Warm at minimum - the offer itself qualifies interest | A yes captures the address and starts the follow-up sequence |
Current tool and alternatives (questions 16-20)
| # | Question | What it reveals | Scoring | Handoff rule |
|---|---|---|---|---|
| 16 | ”What are you using for this today?” | Competitive context and switching cost | Hot: a tool you displace well. Cold: an in-house build nobody will kill | A named competitor should reach a human the same day |
| 17 | ”What’s not working about it?” | The wedge, in their words | Hot: a gap you close. Cold: a complaint you share | This answer belongs in the first sales email verbatim |
| 18 | ”Are you in a contract, and when does it renew?” | Whether a deal is even possible this quarter | Hot: renewal inside 90 days. Warm: three to nine months out | Distant renewals go to a dated nurture track, not to sales |
| 19 | ”Are you comparing us with anyone else right now?” | The competitive shape of the deal | Hot: a short list you are on | Never disparage the alternative; route to a human for the real comparison |
| 20 | ”Is this replacing something, or is it new spend?” | Where the money comes from | Hot: replacement budget already exists | New-line-item deals need a business case; send one |
Timeline and trigger (questions 21-25)
| # | Question | What it reveals | Scoring | Handoff rule |
|---|---|---|---|---|
| 21 | ”What made you start looking today?” | The trigger event, in our experience the strongest single tell that a deal is real | Hot: a named event (new hire, outage, funding, audit) | The trigger is your reason to prioritize the follow-up |
| 22 | ”When would you want this live?” | Timeline, stated plainly | Hot: this quarter. Cold: “sometime next year” | Anything past two quarters belongs in nurture, not the sales queue |
| 23 | ”Is there a date driving this - a launch, a renewal, an audit?” | Whether the timeline is real or aspirational | Hot: a hard date | A hard date sets the follow-up cadence automatically |
| 24 | ”What happens if this slips a quarter?” | Cost of inaction, and whether urgency survives contact | Hot: a consequence they can name. Cold: “nothing much" | "Nothing much” is a nurture lead wearing a hot lead’s clothes |
| 25 | ”Would you want to see it this week, or is this early research?” | Meeting readiness, asked without pressure | Hot: this week. Warm: early research, honestly stated | ”Early research” gets material and a check-back, not a calendar |
Budget, procurement, and security (questions 26-30)
Ask these last, and only when the earlier answers have earned them. A visitor eleven seconds into their first conversation with you does not owe you their budget.
| # | Question | What it reveals | Scoring | Handoff rule |
|---|---|---|---|---|
| 26 | ”Do you have budget set aside, or is that part of what you’re working out?” | Budget reality, phrased so that “no” is safe to say | Hot: allocated. Warm: being worked out, with a date | ”Being worked out” is warm, not cold - keep them |
| 27 | ”What are you spending on this problem today?” | The number your pricing will be measured against | Hot: current spend at or above your price point | Feed the number into the proposal; never quote a discount in chat |
| 28 | ”Does this need to go through security review or procurement?” | Cycle length, and who else you will meet | Neutral on fit, decisive on timeline | Yes routes to a human with your security documentation ready |
| 29 | ”Any requirements we should know up front - SOC 2, SSO, data residency?” | Hard blockers, surfaced before the demo | Hot: requirements you meet. Cold: one you do not | Never guess on compliance answers; route them to a person |
| 30 | ”If this is a fit, what does signing off actually look like on your side?” | The real buying process, from the person inside it | Hot: a process they can describe | A vague answer means your champion has no path yet |
Two rules keep a library like this from becoming an interrogation. Never ask what you already know - if the visitor landed on your enterprise page from a paid search term about SSO, do not ask their company size. And every question must feed a field that exists somewhere: if your CRM has nowhere to store “what are you using today,” the chat should not ask it.
Three full qualification scripts
Conventions in all three: the assistant identifies itself as an assistant in its first message, answers the visitor’s question before asking one of its own, asks a single question per turn, and never invents an answer. Meeting times are proposed, not confirmed, because a person on your side confirms them.
Script 1: the pricing-page visitor
The most valuable script you will write, for a structural reason. In RevenueHero’s 2024 mystery shop of 1,000 B2B SaaS companies (the vendor’s own research, methodology disclosed - treat it as directional), only 165 of them - 16.5% - had a pricing page at all, and just 95 of the 1,000 showed actual prices on it. The person reading your pricing page is very often reading a page that cannot answer their actual question.
Visitor: Is this priced per seat or per usage?
Assistant: Hi, I’m the AI assistant here - happy to help. It is per seat on Starter and Growth, and usage-based above that, with the crossover usually landing around 25 seats. Are you sizing this for a specific team?
Visitor: Yes, about 40 people in support.
Assistant: At 40 you would be on the usage-based tier, which most teams your size prefer because seat churn stops moving the bill around. What are you trying to fix with it?
Visitor: Our response times are a mess and we’re doing routing manually in a spreadsheet.
Assistant: That spreadsheet is the exact thing this replaces. Two quick questions so I point you at the right person: are you the one who’ll make the call on this, or gathering options for the team?
Visitor: I’ll decide, but our COO signs anything over $30k.
Assistant: Understood. And is there a date driving this - a launch, a renewal, anything like that?
Visitor: Our current contract renews October 1.
Assistant: That is a real deadline and worth moving on now. I can propose Thursday at 11:00 or Friday at 2:00 for a working session on the 40-seat setup and the migration path. Which suits you?
Visitor: Thursday works. jane@company.com
Assistant: Thanks Jane. I have put Thursday 11:00 down as tentative and someone from our team will confirm shortly, with the pricing breakdown for 40 seats attached so you have something to send your COO.
Four questions asked: seat count, use case, decision role, and timeline trigger. Everything else arrived free, attached to the answer the visitor already wanted.
Script 2: the docs visitor
A different person entirely. Docs readers are checking feasibility, frequently are not the buyer, and will disengage from anything that smells like a sales script. The win condition here is not a meeting.
Visitor: What’s the rate limit on the events API?
Assistant: I’m the AI assistant here. It is 1,000 requests per minute per workspace on Growth and 5,000 on Enterprise, with burst allowance on both. Is there a volume you are trying to hit?
Visitor: We’d be pushing maybe 2M events a month, spiky.
Assistant: That fits comfortably, though spiky is the part worth planning for - most teams at that volume use the batch endpoint for the peaks. Are you building against this now, or working out whether it fits?
Visitor: Working it out. We’re replacing an internal pipeline.
Assistant: Useful context. Is there anything it has to integrate with on your side?
Visitor: Snowflake and our own service bus.
Assistant: Snowflake is a supported destination out of the box. The service bus would go through the webhook layer, and I would rather have one of our engineers confirm the pattern than guess at it. Is someone else driving the evaluation with you, or is it your call?
Visitor: Our platform lead owns it, I’m doing the technical read.
Assistant: Then let me make your read easier. I can send the API reference, the batch ingestion guide, and a one-page architecture summary you can forward. What is the best email?
Visitor: dev@company.com
Assistant: I have those queued to go over to you now. I have also flagged the service bus question so one of our engineers follows up with a concrete answer rather than a maybe, and if your platform lead wants a technical session we can set one up.
Notice what did not happen: no budget question, no urgency push, no meeting offered to someone who just said they are not the owner. The output is a captured contact, a routed technical question, and follow-up aimed at the person actually deciding. That is the discipline behind our demo request conversion benchmarks: pushing a non-buyer into a calendar slot flatters one metric and damages the next.
Script 3: the comparison-page visitor
The highest competitive intent on your site, and the script where honesty does the most work.
Visitor: How are you different from [Competitor]?
Assistant: I’m the AI assistant here, and I will keep this straight. They are stronger on reporting depth. We are stronger on setup time and on routing rules you can change without an admin. Which of those matters more to you?
Visitor: Setup time, honestly. Ours took four months.
Assistant: Then the comparison is worth having properly. What are you using today?
Visitor: [Competitor], for about two years.
Assistant: What is not working about it?
Visitor: Every routing change needs their support team and takes a week.
Assistant: That is the thing our routing builder exists for. Are you in contract with them, and when does it renew?
Visitor: March.
Assistant: March gives you room to evaluate properly rather than in a panic. Are you comparing anyone else alongside us?
Visitor: You and one other.
Assistant: Fair enough. The useful next step is a side-by-side on the routing workflow with someone who can answer migration questions properly. I can propose Tuesday at 10:00 or Wednesday at 3:00, and if neither works I will pass your details on either way.
Visitor: Tuesday. marcus@company.com
Assistant: Thanks Marcus. Tuesday 10:00 is down as tentative and someone from our team will confirm shortly, with the migration checklist so you can see the work involved before we meet.
Conceding a competitor’s genuine strength in the first message is not a bug. It is why the visitor kept typing, and if you are working on booking more demos, it beats a widget that claims to win at everything.
Handoff rules: when a human takes over
Be precise about what “handoff” means, because most vendor copy here over-promises. A grounded AI chat qualifies and captures; it does not summon a person into the chat window on demand. The truthful pattern is asynchronous: the assistant captures the contact, proposes times, and the thread lands in a shared inbox flagged as waiting on a human, who follows up on the channel the visitor gave.
| Trigger | What the chat does | What the human does |
|---|---|---|
| Hot lead (fits the ICP, has a timeline) | Captures contact, proposes two meeting times, attaches the full transcript | Confirms the time, opens with the visitor’s own words about the problem |
| Warm lead (fits, no timeline) | Captures contact, sends the relevant material, starts a follow-up sequence | Reviews at the next check-in, not the next minute |
| Poor fit | Answers helpfully, points to self-serve or a better-suited option, ends cleanly | Nothing. That is the point |
| Visitor asks for a person | Says a person will follow up, captures the best contact method | Replies from the inbox as soon as the thread is picked up |
| Compliance, security, or custom contract question | Declines to guess, captures the question verbatim | Answers with the real documentation |
| Anything outside the documented information | Says it does not know, and offers to find out | Supplies the answer, and the gap gets added to the source material |
Those last two rows are what protect you. A grounded chat should refuse to improvise, and “I don’t know, but I’ll get you a real answer” beats an invention you have to walk back.
Two more rules most question libraries skip.
Disclose that it is an assistant, in the first message. Now a compliance matter as well as a courtesy. Article 50 of the EU AI Act requires systems that interact directly with people to be designed so those people are informed they are interacting with an AI system, unless that is obvious from context, and Article 113 sets the general application date at 2 August 2026 - four days after this post was published. In the US, California Business and Professions Code section 17941 has since July 2019 made it unlawful to use a bot to mislead a California resident about its artificial identity to incentivize a sale, with an explicit safe harbor if you disclose that it is a bot, clearly and conspicuously. One sentence at the top covers both. None of this is legal advice - check it with your own counsel.
If you ask for a phone number, be honest about what it is for. That is a real consent moment. Under the TCPA implementing rules, 47 CFR 64.1200(f)(9) defines prior express written consent as a written agreement clearly authorizing marketing messages, including a disclosure that signing is not a condition of purchase, and 64.1200(c)(1) restricts telephone solicitation to residential subscribers to between 8am and 9pm local time at the called party’s location. A number collected to confirm a meeting and a number enrolled in a marketing sequence are different things, and the second needs consent language at the moment of capture.
Wiring the answers into segments and follow-up
Questions that feed nothing are theater. The value of the library is downstream, in three places.
Segments. Answers to questions 1, 3, 12, and 16 are segment definitions: team size band, company size, function, incumbent tool. Once those land as fields, “everyone evaluating us against [Competitor] with a renewal inside 90 days” stops being a manual export and becomes an audience you can message. Answers to 18 and 22 give you dated segments, which is where automated lead follow-up gets its timing.
Follow-up. The warm branch is where most chat programs lose their return. Questions 5, 17, and 21 - the problem, the gap, the trigger - are what make follow-up sound like it came from the conversation rather than a template. Someone whose contract renews in March should hear from you in January, about renewal, in their own words. If text is in the mix, our SMS consent and TCPA guide covers the mechanics.
Attribution. Answers should stay attached to the record, so a closed deal traces back to the conversation that started it. Otherwise chat shows up in reporting as untracked direct traffic, which is how good programs get cut in a budget review. Mechanics in traced attribution versus modeled attribution.
Speed governs all three. The MIT and InsideSales Lead Response Management Study found roughly a 21-fold drop in the odds of qualifying a lead when response time stretched from 5 minutes to 30 - the most solid figure we have found in this space, though it is around 2007 phone-sales data and vendor-funded. The shape has not improved: in the same 2024 RevenueHero mystery shop, 63.5% of those 1,000 companies never responded to a demo request at all, and the rest averaged 1 day, 5 hours. More in speed to lead for B2B SaaS.
One number should make a first marketing leader at a Series A or B company sit up. In the same 2026 RevenueHero dataset caveated above, Series A converts qualified leads to booked meetings at 53.6% and Series B at 55.3%, against a 62% median - the two weakest cohorts, below unfunded startups, which RevenueHero attributes to speed and process rather than lead quality. That is a handoff problem, not a question problem.
How Marqeable runs this
We build for this loop, so weigh what follows accordingly. Marqeable’s AI website chat is grounded in your real business information - plans, pricing, integrations, docs, FAQs - so it answers rather than invents, and it asks qualifying questions like team size and timeline in the same conversation. One snippet installs it, with bot and spam protection built in. Ready visitors get captured and turned into booked meetings, with a person on your side confirming; when they are not ready, it can start a follow-up automation instead. The wider case is in what an AI website chat widget actually does.
Around the widget: audience segments with live reach, outbound SMS and email campaigns synced from HubSpot, Salesforce or ServiceTitan, automated follow-up across text and email, and a conversations inbox where SMS replies land with a “your turn” flag on threads waiting for a human. For early customers, AI drafts sit above the composer for a person to edit and send, and email replies are always drafts for approval. Opt-outs are handled automatically, and sends stay inside a 7am to 9pm window in the recipient’s timezone - a product setting, not a compliance guarantee. Attribution ties revenue back to the exact message. We are in private beta with a small early cohort: hands-on onboarding, beta pricing locked for life, month-to-month.
An honest note on what this does not fix
A question library is a conversion tool, not a demand tool. If your pricing page gets forty visitors a month, the highest-leverage work is upstream - the same caveat we gave in the pricing-page post.
Three preconditions before you launch. The chat can only answer from information you have written down, so if your pricing is undocumented, question 26 lands on a visitor who still does not know what you cost. The answers only persist if there are fields to hold them, which usually means adding two or three custom fields to your CRM first. And someone has to work the inbox: a hot lead captured at 11pm and left flagged until Thursday is a hot lead you turned into a form fill with extra steps.
Frequently asked questions
What questions should a chatbot ask to qualify leads?
Ask the questions that decide fit and routing: how many people would use it, what they are trying to fix, whether they own the decision or are gathering options, what they use today, and what date is driving the timeline. Budget and procurement questions come last, once the conversation has earned them. Pull four to six from a library rather than running the same fixed script at every visitor.
How many qualification questions should a chatbot ask?
Fewer than you think in any one conversation - four to six - but the count is not the variable that matters. In RevenueHero’s 2026 benchmark data, top performers converted at 77% with 2-field forms and 76% with 13-field forms. What matters is whether each question routes, qualifies, or personalizes. Questions that feed nothing should be cut.
How do chatbots qualify leads?
A grounded AI chat answers the visitor’s real question from your product and pricing information, then asks a few qualifying questions in the same exchange: team size, use case, role, current tool, timeline. It scores those answers against your ideal customer profile, captures the contact, and routes accordingly - hot leads get meeting times proposed, warm leads enter follow-up, poor fits get a helpful answer without burning a sales cycle.
When should a chatbot hand off to a human?
When the visitor asks for a person, when the question involves a custom contract, security review, or anything outside your documented information, when the honest answer would be a guess, and whenever a hot lead has given their contact details. The truthful handoff is asynchronous: the assistant captures the contact and proposes times, the thread lands in a shared inbox flagged for a human turn, and a person confirms. Do not promise a live agent will appear in the chat window.
The bottom line
Thirty questions is a library, not a script. Draw four to six per page, put each one behind an answer the visitor actually wanted, and make sure every one feeds a segment, a follow-up, or a routing decision - the benchmark data says field count is not what separates good funnels from bad ones. Then spend the rest of your effort on the handoff, where Series A and B teams lose the most ground: a 53.6% qualified-to-meeting rate against a 62% median is not a question problem. It is what happens after the visitor answers.
See it live: Marqeable’s AI website chat answers buyer questions and qualifies visitors from your real business information, the conversations inbox is where SMS replies land, and attribution ties the dollars back to the message.
Marqeable runs your campaigns, answers every visitor, text, and email in seconds, and turns them into booked jobs and meetings - even at 9pm on a Saturday. We’re in private beta with a small early cohort. Get early access
