Qualifying without an interrogation

Qualification exists because sales time is finite. That is a real constraint. The problem is that the standard solution, asking a series of questions before anyone talks to anyone, trades away the top of the funnel to protect the bottom of it.

What is already known before you ask anything

On a marketing site, a visitor who has engaged in conversation has already told you a surprising amount:

• Which pages they read, and in what order.
• Whether they arrived from search, a comparison page, or a direct link.
• Whether their questions are capability questions or implementation questions.
• Whether they mentioned a team, a client, a timeline or a competitor.
• How technically specific their language is.

Someone who arrived on a comparison page, asked about data handling, and mentioned their team is qualified without a single form field. Someone who asked whether the free plan has a time limit is qualified differently, and both are useful to know.

The two questions worth asking

When you do need to ask, two questions carry most of the information:

The first is about the situation: what are they trying to do. Not their role, not their company size, but the actual job. This one question separates the serious from the browsing more reliably than any firmographic field.

The second is about timing: is this something they are looking at now or later. It is the least intrusive prioritisation signal available and people answer it honestly because it does not feel like a test.

What not to ask in the conversation

Budget, authority and company size are all things a salesperson can establish in a first reply, and asking them in a chat widget reads as screening. The visitor can tell they are being sorted, and the ones who are early stage but would have become customers later disengage.

The counter argument

There is a legitimate case for hard qualification: if your sales team is genuinely capacity constrained and every conversation has a real cost, filtering earlier is rational. That is a real situation for high touch enterprise sales.

For self serve software it usually is not. The cost of an unqualified conversation is low, the cost of losing a qualified one is high, and the asymmetry argues for letting more through and sorting afterwards from the transcript.

Scoring from behaviour rather than answers

A workable approach: score conversations after they happen using signals already present, and use that score to prioritise follow up rather than to gate the conversation.

This inverts the usual model. Instead of qualifying to decide who gets to talk, you let everyone talk and qualify to decide who gets called first. Same finite sales capacity, more information, and nobody was turned away at the door.

Why two questions is the ceiling

Every question after the first changes the register of the conversation. One feels like someone helping. Three feels like a form that learned to talk.

The visitor is also doing arithmetic the whole time: how much am I spending here against what I am getting. Answering first puts you in credit. Each subsequent question spends it.

Two is the point where most people are still in credit if the answer was good. Past that, completion rates fall and the answers get less honest, which makes the extra questions worse than useless.

Which two questions to ask

The pair that changes what happens next, not the pair that fills a CRM.

For most products that is scale and timing. How many people or how much volume, and when they are trying to have something working. Those two decide routing and priority, which is the only reason to ask anything.

Current tool is a good substitute for scale when scale is hard to phrase. It carries budget, sophistication and switching cost in one answer.

Job title is almost never worth a question. It is the least informative field commonly collected, and it is usually inferable later anyway.

Reading the answers you already have

Half of qualification is already in the transcript before you ask anything, and most implementations ignore it.

The question itself carries stage. Someone asking about migration has a current tool. Someone asking about a specific limit has modelled their usage. Someone naming a competitor is comparing rather than discovering.

The page carries context. The same question on a pricing page and on a blog post are different conversations.

Asking someone to state what they already told you is the fastest way to make an assistant feel mechanical, and it is entirely avoidable.

What to do when they decline

Some visitors will not answer a qualifying question, and the response to that decides whether the assistant reads as helpful or as a funnel.

Answer anyway, completely, and do not ask again in the same conversation. A single graceful acceptance does more for the brand than the contact detail would have been worth.

Do not gate anything behind the answer. The moment a visitor discovers that declining costs them the answer, the earlier help is retroactively reframed as bait.

And log the decline rather than treating it as a null. A high decline rate on one page usually means the ask is arriving too early there, which is a placement fix rather than a wording one.

Where the two questions should live

Not at the start, and not at the end. The workable position is immediately after an answer the visitor engaged with, which usually means after their second message rather than their first.

A visitor who asked one question and got an answer may be finished. A visitor who asked a follow up is in a conversation, and a question asked inside a conversation reads very differently from one asked at the door.

This is also why hard coding qualification to message number rarely works. The signal is engagement, not count.

What good qualification sounds like

The difference between helpful and mechanical is mostly phrasing, and it is worth being specific about what works.

Ask in service of the answer, not in service of the record. Asking how large the team is so the assistant can say which plan fits is a question with an obvious payoff for the visitor. Asking company size because a field exists is not, and people can tell the difference immediately.

Make the question specific enough to answer quickly. Roughly how many people would use it is answerable in three words. Tell us about your use case is an essay prompt, and it is where conversations end.

Offer the reason before the question rather than after. So I can point you at the right plan, roughly how many people would be using this. The order matters because the justification arriving second reads as backfilling.

And accept an approximate answer as complete. A visitor who says a few dozen has answered. Pushing for an exact figure converts a conversation back into a form in one message.