Skip to content

Revenue & Sales Systems

Lead qualification: an answer for every inquiry, the same day

Some inquiries are a yes, some are a “not yet”, and some are work you don't do. Most businesses answer the first kind quickly and leave the rest waiting. A qualification system gives every inquiry a verdict with its reason, sends the reply that goes with it, books what can be booked, and passes anything outside your rules to a person. We write your fit rules down with you and build the system that applies them.
Talk through your inquiriesFollow one inquiry ↓
InquiryVerdict and reasonWhat happens nextR.W. · web form 07:31Water heater leaking, Eastsideyesin area, we offer itBooked Fri 08:00–10:00, text sentG.H. · web form 07:52New boiler, thinking next springnot yetin area; wants springCheck-in set for early MarchD.F. · call 09:10Pool heater repairnot usnot a service we offerPolite reply with three referralsT.Y. · email 10:44AC tune-up in Westbrooknot usoutside the service areaPolite reply, sent in minutesN.O. · call 11:203 rooftop units, restauranta personcommercial, unusualTo W1 with the call notes5 inquiries, 5 answered on Tuesday · every reason on the CRM

Unanswered is also an answer

When inquiries pile up, the team answers the obvious yeses and leaves the rest. The customer with a job you don't do waits two days for nothing. The one who wants a boiler next spring never hears from you again, and in spring calls whoever answered. Each one remembers how you made them feel.

A qualification system gives every inquiry a verdict on the day it arrives: yes, not yet or not us, each with the reason written down. Each verdict comes with its reply: a booking, a check-in at the right time, or a polite answer with somewhere better to go. Anything your rules don't cover goes to a person with what's been gathered so far.

Today, and with qualification

Today

  1. 01Inquiries wait until someone has time to read them.
  2. 02The team answers the obvious yeses first.
  3. 03“Not yet” and “not us” are often never answered.
  4. 04Nobody records why an inquiry was turned down.

Poor fits take up sales time, and good fits for later are forgotten.

With qualification

  1. 01Every inquiry gets a verdict the day it arrives.
  2. 02Each verdict has a reason, on the CRM.
  3. 03“Not yet” gets a check-in when the time is right.
  4. 04“Not us” gets a polite reply and, where you can, a referral.
  5. 05Anything unusual goes to a person with the notes.

Everyone who asks hears back, even when the answer is no.

One “not yet”, end to end

G.H.'s boiler inquiry from the top of the page, from the form to a booked visit in March.

Events

Inquiry · G.H.

Status
received
Need
boiler replacement
Area
—
Verdict
—
Reason
—
Next
—

Event 1 of 7: inquiry.received

What it decides, and what it leaves to people

On its own

  • Gives a verdict when the rules are clear
  • Sends the reply that goes with it
  • Books routine work your rules allow
  • Records the reason on the CRM

Asks a person

  • Anything outside the rules
  • Commercial and unusual jobs
  • A customer who disagrees with the verdict
  • Messages it can't read with confidence

Never

  • ✕ Turns someone down without a reason
  • ✕ Leaves an inquiry unanswered
  • ✕ Decides on anything you haven't written down
  • ✕ Uses anything about who the person is, beyond the job

What changes from one business to the next

Fit rulesServices, areas, job sizes and anything else that makes a yes
TimingWhen “not yet” becomes a check-in, and how far ahead
RepliesThe wording for each verdict, and the referrals you're happy to give
BookingWhat can be booked without a person
ReviewWho sees the inquiries outside the rules, and how fast

A common starting point is the CRM you already use, n8n or Trigger.dev for the rules and replies, a language model to read free-text messages into fields with a person reviewing anything uncertain, and your scheduling tool for bookings. These are starting candidates, not requirements.

Is a qualification system the right fit?

Good fit

  • A good share of your inquiries aren't a fit, or aren't a fit yet.
  • Inquiries that aren't an obvious yes wait days for an answer.
  • You can write down most of what makes a good fit.

Avoid when

  • Nearly every inquiry is a yes.
  • Every job needs a conversation before anyone can tell.

How we'd approach it

Most of the early work is writing down your fit rules, your replies, and the cases a person should always see.

  1. 01

    Understand

    As much as the problem needs

    We map how the work runs today: who does what, which systems hold the records, and where it breaks.

  2. 02

    Design

    Decided before it's built

    Ownership, rules, integrations and exceptions, agreed with you and written down with acceptance criteria.

  3. 03

    Build

    Connected to what you use

    We build the scoped system, connect it to the tools you already run, and test it on the cases that matter.

Related systems

The capabilities underneath

Questions about lead qualification systems

Does AI decide who we turn down?

No. AI can read a message into fields, such as the need and the timing. The verdict comes from rules you've written, and anything the rules don't cover goes to a person.

Won't customers mind an automated “no”?

Most mind silence more. The reply is written by you, says why, and where you can, points them somewhere better. Anyone can reply and reach a person.

What if the verdict is wrong?

The reason is on the record, so it's easy to see why. Anyone on the team can overturn it, and repeated corrections show which rule needs changing.

Does it work for phone calls?

Yes. Call notes or an AI receptionist's record go through the same rules as forms and emails.

Answer every inquiry the same day

Tell us what a good lead looks like and what happens to the rest today. We'll show you how each one would get its answer.

Start a project