17 Lead-Qualification Questions Your Chatbot Should Ask

What is BANT, and why does it still work for most businesses?

BANT — Budget, Authority, Need, Timeline — is a lead-qualification framework that gives a chatbot four dimensions to evaluate before routing a visitor to a salesperson. HubSpot describes BANT as "a conversation guide" that provides structure and intention, not just a checklist to run through. Each dimension addresses a distinct disqualification risk.

Budget filters visitors who cannot pay for what you offer. Authority surfaces whether the person you are talking to can actually sign off on the purchase or needs to loop in a manager. Need confirms the visitor has a real problem your service solves — not just idle curiosity. Timeline separates ready-to-buy leads from early-stage researchers who might convert in six months. The combination means a chatbot can segment a visitor into hot, warm, or cold before a human ever reads the conversation.

BANT's limitation is that it assumes a single decision-maker and a relatively short sales cycle. For transactional services — a landscaping company, an accounting practice, a web design agency — those assumptions hold. For enterprise software or commercial construction projects involving committees and procurement workflows, BANT leaves too many disqualification risks unaddressed. That is where MEDDIC fills the gap.

What is MEDDIC, and when should you use it?

MEDDIC stands for Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion. It was originally created inside PTC in 1996 by Dick Dunkel, and helped grow PTC's sales from $300 million to $1 billion in four years. The framework was built specifically for complex, multi-stakeholder deals that BANT cannot adequately qualify.

The six components address what BANT misses. Metrics quantifies the economic benefit the buyer expects — not just "we need this" but "we expect to cut response time by 40%." Economic Buyer identifies who actually controls the budget, which in an organization is often not the person initiating the inquiry. Decision Criteria surfaces what evaluation framework the buyer uses. Decision Process maps the approval workflow so you know what happens between interest and signature. Identify Pain uncovers the specific, measurable cost of the problem — which creates urgency. Champion finds the internal advocate who will fight for your solution when you are not in the room.

Salesforce Trailhead identifies MEDDIC as "a comprehensive framework" particularly suited to deals where a salesperson pursuing unfit prospects wastes significant time. In a chatbot context, you will not ask all six MEDDIC questions in a single conversation — but the framework determines which questions to prioritize based on the signals the visitor gives in the first two turns.

What are the 5 core qualifying questions every chatbot should ask?

These five questions apply regardless of industry, deal size, or qualification framework. They collect the minimum viable signal to route a lead correctly without overwhelming a first-time visitor.

What are the 12 advanced qualification questions for high-ticket sales?

These questions layer MEDDIC logic on top of the 5 core questions. They are appropriate when your average deal value exceeds roughly $2,000 or involves multiple stakeholders. In a chatbot, you would ask 3–4 of these per conversation depending on the visitor's earlier answers — not all 12 in sequence.

How should a chatbot ask all 17 questions — with full intent and sample phrasing?

The table below maps every qualification question to its framework dimension, the intent behind asking it, and a chatbot-ready phrasing that avoids sounding interrogative.

How do service businesses qualify leads without BANT or MEDDIC?

Most service businesses — home services, legal, healthcare, accounting, cleaning — do not have a sales team running structured frameworks. Their qualification needs are simpler, but no less important. The four dimensions that matter for service businesses map to a practical framework: Service area, Urgency, Scope, and Type-of-customer (SUST).

Service area is the first gate: asking it immediately filters out leads you cannot serve and saves both parties time. Urgency determines whether this is an emergency call (plumbing leak, same-day legal filing) or a planned project (kitchen renovation, annual tax return) — which affects staffing and response priority. Scope gives you enough information to quote or at least pre-qualify for a site visit: number of rooms, square footage, number of employees, nature of the legal matter. Type-of-customer distinguishes residential from commercial, existing clients from new prospects, and referral leads from cold web traffic — each group converts differently and deserves different follow-up treatment.

A service-business chatbot that asks these four questions in under 90 seconds of conversation time can route a lead to the right team member, generate a rough estimate, and set an appointment — without any human involvement in the intake step.

How do you ask qualifying questions without sounding like an interrogation?

The single biggest mistake in chatbot qualification design is writing questions that sound like a form with a chat UI bolted on. Visitors abandon interrogative flows for the same reason they abandon long forms: it feels like the business is extracting data, not having a conversation.

Three tactics close the gap. First, lead with the visitor's problem before asking about your qualification criteria. "What are you trying to solve?" before "What is your budget?" creates a logical sequence — you are establishing relevance before asking for a commitment. Second, provide graceful off-ramps on sensitive questions. "Do you have a rough budget in mind, or is this still early-stage?" gives the visitor two honest answer paths instead of forcing a number they may not have. Third, signal why you are asking. "So I can connect you with the right team member — are you the decision-maker here, or is someone else involved?" is less confrontational than the bare question because it frames the ask as service, not gatekeeping.

Pacing matters too. Asking one question per conversational turn, waiting for the answer, and responding to what the visitor actually said before moving to the next question reads as attentive. Firing three questions in a single bot message reads as a survey. Even if the substance is identical, the pacing changes the visitor's experience of the conversation entirely.

When should a chatbot politely disqualify a lead?

Disqualification is not failure — it is efficiency. A chatbot that routes every visitor to a sales follow-up regardless of fit wastes your team's time and sets the visitor up for a disappointing conversation. The right approach is to disqualify gracefully, not dismissively.

Three clear disqualification signals: the visitor is outside your service area, their budget is materially below your minimum engagement, or they describe a need that is a poor fit for what you offer. In each case, the chatbot should acknowledge the situation honestly — "We do not currently serve that area, but here is what we recommend" — and, where possible, offer a referral or resource. A visitor who was disqualified courteously will refer others and may return when their situation changes. A visitor who was ignored or strung along will not.

Disqualification is also the correct response when a visitor refuses to answer qualifying questions. Do not hard-gate lead capture behind qualification. Instead, collect contact details without qualification data and tag the lead as unscored in your CRM. An unscored lead is lower priority than a hot BANT-qualified lead, but it is still worth a low-touch nurture sequence.

How do you map chatbot qualification answers to lead scores?

Lead scoring converts unstructured conversation data into a number your CRM can route automatically. A simple point-based system works for most small businesses.

Assign weights to the answers that most predict conversion in your specific business. For a service business using the SUST framework: in-service-area = 3 pts (hard requirement — no other signals matter if this is absent), urgency "this week" = 3 pts / "this month" = 1 pt / "exploring" = 0 pts, scope described in detail = 2 pts / vague = 0 pts, existing client = 2 pts / referral = 1 pt / cold web = 0 pts. A score of 8–10 gets an immediate callback; 4–7 enters an automated nurture sequence; 0–3 receives a low-touch long-cycle drip.

For B2B businesses using BANT, a similar structure applies: confirmed budget match = 3 pts, decision-maker confirmed = 2 pts, clear specific need = 2 pts, timeline under 30 days = 3 pts. Knobot passes all captured field values via webhook on lead submission, so you can run scoring logic in your CRM or a simple Zapier workflow without any custom code.

How do you design your own qualification flow in 5 steps?

Use this process to adapt the 17 questions above into a qualification flow specific to your business, rather than deploying a generic script.