A Simple Framework for AI Lead Response You Can Repeat

When replies to new leads depend on how your day is going, results swing. A good week has fast, warm answers. A busy week has a pile of enquiries and a guilty feeling on Friday. AI lead response works best when it follows a process you can repeat. This post gives you one, in five parts you can remember: Catch, Read, Answer, Step, Check.

It is a framework, not a study. It is built from the logic of how a reply works, and you should adjust it to your business. Lesson 5.4 turns it into a working setup: Reply to every new lead in five minutes.

Run every new lead through the same five parts: catch it, read it, answer it, give one next step, and check the reply before it goes.

Why a framework beats a good prompt

A clever prompt helps once. A process helps every time. With a framework, you know what each part of the system is for, so when something goes wrong you know where to look. A reply that missed the point is a Read problem. A reply that sent no one anywhere is a Step problem. A reply with a wrong fact is a Check problem.

The five parts

1. CatchEvery lead lands in one place, and something notices within a minute. No leads hiding in a side inbox or a messaging app you forget to open.
2. ReadThe message is understood before anything is written. What did they ask? What do they want to happen? Is this lead hot, routine or not a lead at all?
3. AnswerA short reply in your voice that deals with their actual question, using only facts you have approved.
4. StepExactly one next action for the lead: book a time, answer one question, confirm a detail. Make it small.
5. CheckA person reads the reply before it goes, until the error rate is low. After that, check a sample and all unusual cases.

Catch

Speed starts with notice. A 2011 Harvard Business Review study of 1.25 million leads found that firms contacting a lead within an hour were nearly seven times as likely to qualify it as firms waiting one more hour. It is a US study, mostly of larger firms, and it measures conversations, not sales, so use it as a reason to test your speed and not as a promise. Its audit of 2,241 companies also found 23% never replied to a test lead.

To catch well, pick one entry point. Forward the form, the contact address and the booking page into one inbox or list. The CRM lesson shows a simple way to do this. Then set a trigger: when a new lead arrives, start the process.

Read

Before AI writes anything, have it summarise the lead in three lines: what they asked, what they want, and how urgent it sounds. Ask it to label the lead as hot, routine or unclear. This costs a second and prevents the most common failure, a polite reply to a question nobody asked.

Give it a short list of hot signals you choose: a date, a quote request, a phone number, a phrase like "as soon as possible". Hot leads should alert you. Unclear leads should come to you instead of getting a guess.

Answer

Write the answer pattern once. A good pattern has four slots:

1. Their question, restated in their words.
2. One real answer, from facts you have approved.
3. What happens next, with a time.
4. Sign off, in your usual style.

Keep a small approved facts sheet: your areas, hours, what a typical job involves, what you do not offer. Tell AI to use only that sheet and to say a person will follow up when the answer is not there. This is the same idea as the standing brief in How to brief AI like a senior hire.

Step

End with one step. Compare the two endings:

• "Let me know if you have any questions." The reader has to invent the next move.
• "Pick a time that suits you here: [link]." The reader can act in ten seconds.

If your business needs a call or a visit before a quote, the step is booking it. If it is simple, the step may be a single question. Put the step at the end where the eye lands, and avoid offering three.

Check

This part keeps trust. Send every reply to yourself as a draft at first. For each draft ask three questions:

• Is every fact in it on my approved sheet?
• Does it sound like me?
• Does it make one clear ask?

Keep a tally of how often you change a draft. When most go unchanged for a few weeks, you may let routine cases send themselves and keep reviewing hot, unclear and high value ones.

The weekly run

A framework only helps if you repeat it. Once a week, take 20 minutes.

1. Catch: did any lead land somewhere unwatched?
2. Read: pick three replies and see whether the summary matched the lead.
3. Answer: note any fact AI got wrong and fix the approved sheet.
4. Step: how many leads took the next step? Which wording did better?
5. Check: how many drafts did you edit? Is it time to loosen or tighten review?

Change one thing per week. If you change five, you will not know which one helped.

Common ways the framework breaks

• Skipping Read. The reply is polite and wrong.
• Too many facts in Answer. It reads like a brochure.
• No Step. Leads read, nod, and drift.
• Dropping Check too soon. One bad message reaches a customer.
• Never reviewing. The approved sheet goes out of date.

Each failure points back to one part, and that makes fixing quick.

Questions people ask

Can I use this framework without any automation?

Yes. You can run the five parts by hand with a template. Automation just makes Catch and Answer faster.

How long should the reply be?

Short enough to read on a phone without scrolling much. Around 100 words is a common target, but your business may differ.

What if a lead does not fit any pattern?

Route it to yourself. The framework should send unclear leads to a person instead of guessing.

How often should I update the approved facts sheet?

Whenever hours, areas or offers change, and review it monthly.

Put it to work

Print the five words and stick them where you see them. Then build the simple version: one entry point, one pattern, one step, drafts first. Lesson 5.4, Reply to every new lead in five minutes, walks you through it, and the five email journey picks up where the first reply ends.