Lead capture: every extra question costs you people and buys you quality

A lead capture bot should ask as few questions as your sales capacity allows: usually what the person wants, when they need it, and how to reach them. Every question tells you more about the person and loses some of them, and that trade is the whole design problem. Many implementations treat more information as better.

More information is not always better. A bot that asks eight questions produces well-described leads and fewer of them. Whether that is an improvement depends on three numbers: what a lead is worth, what it costs to talk to an unqualified one, and how many leads you can handle.

What we'll cover

• The trade, stated properly
• Where your optimum sits
• The three questions worth asking
• Order matters more than count
• Building it with CodeWords
• Speed beats qualification
• The handover, where most leads are lost
• Scoring that somebody actually uses
• What never to ask a bot to decide
• Making it survive
• Limits of lead bots
• What to measure first
• Frequently asked questions

Key takeaways

• Each extra question lowers the completion rate and raises lead quality, so the right number depends on what an unqualified lead costs you.
• Businesses with spare sales capacity should capture almost everything and sort later, while capacity-constrained businesses should ask more.
• Ask what the person wants, when they need it and how to reach them, and ask the cheapest question first.
• Speed to the first human reply matters more than how well the bot qualifies the lead.
• Log abandoned conversations, because where people stop is the only data that shows whether you ask too much.

The trade, stated properly

Completion rate and lead quality move in opposite directions as you add questions.

Completion rate falls. Each question is a moment somebody can stop, and the drop is steepest on anything that feels intrusive or that they cannot answer quickly.

Lead quality rises. You know more, so your team wastes less time and can prioritise.

The net effect depends on what an unqualified lead costs you. If a salesperson spends forty minutes discovering that somebody was never a fit, questions are worth asking. If qualifying takes two minutes on a call your team was making anyway, the questions cost you leads for little gain. (Both times are illustrative examples.)

Most businesses have never worked this out and default to asking more, because a form with more fields feels more professional. Asking more is the more expensive option when sales capacity is spare.

Where your optimum sits

Your optimum depends on three numbers, and you can estimate all three in an afternoon.

What a closed deal is worth, and roughly what proportion of enquiries close.

What it costs to handle an unqualified enquiry, in the time of whoever handles it.

How many enquiries you can actually handle. Capacity decides the answer and teams often ignore it. A team at capacity should filter hard. A team with spare capacity should capture everything and sort later, because a lead lost at question four is worth nothing.

The result: capacity-constrained businesses with expensive sales time should ask more. Businesses with spare capacity and cheap qualification should ask almost nothing beyond how to reach somebody.

The three questions worth asking

Three questions earn their place ahead of all others.

What they actually want. In their words, not from a list. A single open question produces more useful information than four multiple choices, and people answer it willingly because it is what they came to say.

When. Timing separates a live enquiry from research more reliably than budget questions do, and people answer it honestly.

How to reach them, and which channel they prefer.

Budget is the question teams most want to ask and the one that loses the most people. Where the work has a genuine range, saying so and asking whether that is the right territory works better than asking what they have to spend.

Order matters more than count

Ask the cheap question first and the expensive one last, where cost means how likely the question is to end the conversation.

The visitor's need costs almost nothing to ask, because it is what they arrived to tell you. Timing is cheap. Contact details cost moderately and should come after somebody has invested a little. Budget is expensive. Questions about their organisation's internal structure are expensive and rarely useful early.

The common failure is asking for a name and email first, before the visitor knows whether you can help. That reads as being captured instead of helped, and some people leave at the point where their intent is highest.

Get the shape of what they need first. Contact details are then a reasonable request, because there is something to follow up on.

Building it with CodeWords

CodeWords connects to 3,000+ integrations, and each connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: what you need to know, in what order, and what a qualified lead triggers.
3. Authorize the connections to your CRM and whichever channel the enquiries arrive on.
4. Describe the exceptions: somebody who will not answer a question, somebody who asks something unexpected, an existing customer, an enquiry outside what you do.
5. Record every conversation including the abandoned ones, because where people stop is the only data that shows whether you are asking too much.

You describe the outcome; Cody builds it, connects it, and deploys it. The Free plan covers light use. Pro costs $39 per month ($33 per month billed yearly) and Business costs $100 per month (CodeWords pricing page, 2026); details are on the pricing page.

Speed beats qualification

Speed of the first human response matters more than how well the bot qualifies. If you improve one thing, improve that.

A person enquiring usually contacts several suppliers, so the order of replies matters. A lead answered while they are still thinking about the problem is in a different conversation from one answered the next morning, after they have spoken to somebody else.

The bot's most valuable job is therefore often not qualification. Its job is acknowledging immediately, capturing enough to be useful, and getting a person in front of the enquiry quickly. A lightly qualified lead that reaches a human in ten minutes beats a thoroughly qualified one that reaches a human tomorrow.

Measure your time to first human response. Most businesses do not know this number, and many are slower than they believe.

The handover, where most leads are lost

Most leads are lost at the handover: the bot does its job and the lead then disappears, which is a process problem, not a bot problem.

Send the whole conversation, not a summary of fields. What somebody actually wrote carries information no form captures.

Name somebody. A lead arriving in a shared inbox belongs to nobody. Assign it, with a time by which it must be picked up.

Tell the customer what happens next, specifically. "Someone will be in touch" feels like nothing. "Sarah will call you this afternoon" sets an expectation and makes your team accountable.

Make the handover visible so an unactioned lead is obvious. A lead untouched for two days should be a named person's responsibility.

Scoring that somebody actually uses

Most lead scores are ignored because they use factors that never predicted outcomes.

Two rules. Base the score on what actually correlated with closing in your own history, rather than on a template. And keep it to a handful of factors, because nobody trusts a number they cannot explain.

Check it against reality quarterly. If your highest-scored leads do not convert better than the rest, delete the score instead of tuning it. A score nobody trusts is worse than none, because people use it as a reason to ignore leads.

What never to ask a bot to decide

Whether to reject an enquiry. Filtering into a lower priority is fine. Telling somebody you cannot help them is a person's decision, because a bot's mistakes can become public complaints.

Anything about price beyond published figures. A number a bot mentions becomes the number the customer expects.

Commitments about timing or availability that the bot cannot verify.

Anything where somebody has expressed frustration. Send it to a person immediately.

Making it survive

Log abandoned conversations, because where people stop is the most useful data.

Measure time to first human reply and treat it as the primary metric.

Pass the full transcript to whoever picks up the lead.

Check the score against outcomes quarterly and delete it if it does not predict.

Re-read twenty real conversations monthly, particularly the ones that ended early.

Limits of lead bots

More questions do not mean more leads. The trade depends on your economics.

A bot cannot judge fit. It collects only what it was told to collect.

Qualification cannot fix slow follow-up, which is usually the larger loss.

Scores decay as your market and customer mix change.

Some enquiries cannot be qualified in advance. For those, capture the details and route them quickly.

What to measure first

Measure where people stop first. Instrument the abandoned conversations before changing anything, because the question that loses the most people is rarely the one anybody predicted, and without that data every change to the flow is a guess.

Two habits matter most. Ask what the person wants before asking who they are, because contact details requested before any value is offered read as capture, not help. And prioritise time to first human reply over qualification quality, because the lead you answer first is often the one you win.

Frequently asked questions

How many questions should a lead bot ask?

As few as your sales capacity allows. The right number depends on what an unqualified enquiry costs you and whether you have spare capacity. Capacity-constrained businesses with expensive sales time should ask more, while businesses with room should capture nearly everything and sort afterwards.

What are the most useful qualifying questions?

Ask what the person wants in their own words, when they need it, and how to reach them. Timing separates live enquiries from research more reliably than budget questions, and an open question about the need produces more useful detail than a multiple-choice list.

Why is asking for budget a problem?

Budget loses more people than any other question and is often answered inaccurately. Where the work has a genuine range, state your own range and ask whether that is the right territory. This gives you the same information without asking the visitor to name a number.

What order should questions come in?

Ask the cheapest question first, where cost means how likely the question is to end the conversation. Ask what they want, then timing, then contact details. Asking for a name and email first reads as being captured, and some visitors leave at that point.

What matters more than qualification?

Time to first human reply matters more. A lightly qualified lead that reaches a person in ten minutes generally beats a thoroughly qualified one that reaches a person tomorrow, because enquirers talk to several suppliers. Measure this number before you change the qualifying flow.

Where do captured leads get lost?

Leads are lost at the handover. Send the full transcript instead of summary fields, assign a named person with a deadline to pick it up, tell the customer specifically what happens next, and make unactioned leads visible so nobody can ignore them.

Is lead scoring worth doing?

Scoring is worth doing only if it uses what correlated with closing in your own history, keeps to a few explainable factors, and is checked against outcomes every quarter. A score nobody trusts becomes a reason to ignore leads, so delete it if it does not predict.

What should a bot never decide?

A bot should never decide whether to reject an enquiry, quote anything about price beyond published figures, or make commitments it cannot verify. It should also pass any frustrated customer to a person immediately, because these cases carry the highest cost when a bot gets them wrong.

What should I instrument?

Instrument abandoned conversations, grouped by the question at which people stopped. This is the only data that shows whether you are asking too much. The costly question is rarely the one teams predict, so measure it before you change the flow.

Should the bot or a person qualify?

Use the bot for questions that are cheap to ask and unambiguous to answer, and use a person for judgement. The bot's most valuable contribution is often speed, not depth: it acknowledges the enquiry immediately and gets a person in front of the lead quickly.

Related reading

• Asking without interrogating
• Connecting conversations to your CRM
• Designing the conversation