The Qualification Call: Questions That Separate the Curious From the Buyer

A qualification call has exactly one job: to decide, within fifteen minutes, whether this enquiry deserves a slot in your calendar. It isn't a mini-demo and it isn't a persuasion attempt. It's a screening exercise built on pre-set questions and written acceptance criteria, ending in one of only three outcomes: qualified, deferred with a date, or declined with a reason.

The problem this call solves isn't a shortage of enquiries — it's a surplus. A team can spend its entire week meeting people who are genuinely interested: they ask good questions, they request a proposal, they reply to messages. And they don't buy, because they have no budget, no decision-making authority, or no urgency. Interest is not purchase intent, and the difference between them is discovered either in one call or after twelve weeks of follow-up.

What This Call Actually Settles (and What It Doesn't)

The call settles four things: that the customer has a problem they recognise and can describe; that they have a reason to solve it this quarter rather than next year; that the person you're speaking to either decides or has access to whoever does; and that the size of the problem is proportionate to your price, so the conversation doesn't collapse at the first number.

It does not settle the technical solution, the integration details with their existing systems, the final price, or the implementation roadmap. Anyone who tries to settle those on a qualification call makes two mistakes at once: they hand valuable information to someone who hasn't proven they're serious, and they stretch the call to forty minutes — which is why the prospect won't agree to one next time.

A practical rule: if the customer asks a detailed technical question during this call, answer it in one sentence and then say, "That's exactly the point we'll spend thirty minutes on in the next meeting." Deferring here isn't evasion; it's respecting what the call is for.

Four Acceptance Criteria to Write Down Before You Pick Up

Unwritten criteria mean every rep qualifies by instinct, and your team's calendar fills up with people who simply had a pleasant tone of voice. Put the criteria on a single page, distribute it, and review it quarterly.

Criterion	Minimum acceptable	How to verify it
Described problem	A concrete, recurring situation	They describe a specific incident, not a generality
Time driver	An event forcing action within 90 days	"What happens if you postpone?"
Authority	They decide, or can name the decision-maker	"Who signs off on this with you?"
Size fit	Volume justifies the annual cost	User count and activity volume

Require three out of four, not four out of four. Demanding all four rejects good customers who are one point short of ready; accepting two throws the door wide open. Then fix one strict rule: anyone with no time driver at all does not qualify, however enthusiastic they sound. Enthusiasm without a deadline evaporates at the first distraction.

The Seven Questions — Exact Wording, and Why It Matters

Wording isn't cosmetic. A closed question gets you a "yes" that means nothing; an overly open one gets you a speech.

1. "What specifically prompted you to look for a solution now?" — The word "now" surfaces the time driver in the very first question. An answer like "we've been thinking about it for a while" is an early negative signal.
2. "Describe the last time this problem happened." — Asking for a concrete incident separates people in genuine pain from people surveying the market. If they can't narrate an episode, they don't have a problem yet.
3. "How are you handling it today?" — The current workaround is your real competitor, even if it's a spreadsheet. Anyone who says "we're not handling it" usually means the pain is tolerable.
4. "What happens if things stay exactly as they are for another six months?" — This measures the cost of delay. If the answer is "nothing serious," you're looking at a deferral, not a rejection.
5. "Who else will be involved in the decision?" — Note the phrasing. Don't ask "Are you the decision-maker?" — that pushes people to claim authority they don't have. "Who else" presumes others exist, which makes naming them easy.
6. "How many people will actually use the system? And roughly how many deals or orders do you handle monthly?" — Ask about size without embarrassment. User count and activity volume determine whether the subscription is proportionate.
7. "If we agree the solution fits, what steps do you need internally before signing?" — This exposes committee buying, a long procurement cycle, or the fact that the phrase "next year's budget" will surface in two months.

Seven questions is enough. Adding an eleventh turns screening into interrogation.

Signals of the Interested Non-Buyer: Hearing Them Early

Some phrases recur often enough to build a list:

• "I just want to see the pricing" with no problem described — they're collecting quotes for a file or an internal comparison.
• "We're currently studying the market" with no decision date — exploration, not a project.
• "Let me check with management and get back to you" on the first call, combined with an inability to name anyone in management — no access to the decision.
• Strong enthusiasm about features paired with dodging the size question — usually a business smaller than your pricing model assumes.
• Someone asking about integrations and technical detail before mentioning a single problem — possibly a technical evaluator preparing a report for someone else.

These are indicators, not verdicts. The right move is to hear them, then test with a direct question: "So I don't waste your time — do you have a target date for going live?"

From Inbound Enquiry to Qualification Decision: The Screening Path

The path has five stops: the enquiry arrives from the website form, WhatsApp, or an exhibition; a single record is created for it no matter how many channels it touched; it's assigned to a named owner, not to "the team"; the qualification call happens within one business day; and the decision is logged — qualified and moved to the meeting stage, deferred with a review date, or declined with a reason from a short list.

The decisive condition is that the decision is mandatory: no inbound enquiry closes without one of the three. Enquiries left without a decision are exactly the ones that pile up by the hundreds and render your pipeline report meaningless. In Effistar you can make the "qualification outcome" field required before an enquiry moves to the next stage, so nothing slips through in silence.

## The Polite Decline and the Documented Deferral

A decline isn't a dismissal. The wording that works: "Thank you for being so clear. From what I've heard, the better fit for you right now is X, and we'd add more value once your team reaches Y. I'll make a note and get back in touch in six months if that suits you."

Three gains from that sentence: respect that keeps the door open, honest information that makes them refer others to you, and a calendar freed of a meeting that would have ended in "we'll get back to you."

A deferral, meanwhile, must be documented rather than polite: a specific review date, a one-sentence reason, and the event that reopens the file ("after the 2026 budget is approved," "after their current contract expires in April"). A deferral without a date is a rejection nobody wants to name.

Capture the Answer Once: Qualification Fields, Not Scattered Notes

The worst thing that can follow a good qualification call is having the answers typed into a free-text note box — so the rep, or their manager in the meeting, asks the customer the same question two weeks later. Repeating the question tells the customer one thing: we weren't listening.

Make the call's outputs separate fields on the customer record:

• Time driver (short text) and the date of the event
• The problem in the customer's own words, not your paraphrase
• The current workaround in use
• Decision-maker: name and title
• Expected user count and monthly activity volume
• Internal purchasing steps
• Qualification outcome and reason

Separate fields can be sorted and filtered; a free-text note cannot. And once these fields are standardised across the team, you can ask a genuinely useful question at quarter's end: what's the most common reason for declining? If "too small" dominates, your problem is your lead sources, not your team's skill. If it's "no time driver," your marketing content is attracting browsers rather than buyers.

A Sample Call: Fifteen Minutes, Start to Finish

An illustrative scenario: a contracting firm submitted an enquiry through the website.

Rep (0:00 — framing): "Khalid, thanks for your time. Today's call is fifteen minutes. The goal is for me to understand your situation and work out whether we're even the right fit. If the answer is yes, we'll book a detailed meeting. Does that work?"

Khalid: "Sure."

Rep (1:00): "What specifically prompted you to look for a solution now?"

Khalid: "We lost two tenders because of late submissions, and all our follow-up lives on WhatsApp."

Rep (3:00): "Describe the last time that happened." — (The concrete incident confirms the first criterion.)

Rep (6:00): "And how do you manage it today?" Then: "If nothing changes for six months, what happens?"

Khalid: "We'd lose our rating with at least two clients."

Rep (9:00): "Who else will be involved in the decision?"

Khalid: "My brother, the finance director, and the operations manager."

Rep (11:00): "How many users do you expect? And how many tenders do you track monthly?"

Rep (13:00): "If we agree the solution fits, what are your steps before signing?"

Rep (14:00 — close): "That's clear. You meet the criteria we look for, so I'd suggest a thirty-minute meeting on Tuesday, with your operations manager present since he'd use the system daily. Shall I send the invite now?"

Notice what didn't happen: no price was mentioned, no screen was shared, no integration was explained. Only one thing occurred — both sides established that the next meeting is worth holding.