When should you use it?
- Inbound inquiries arrive through a web form and someone triages them by hand
- You tried AI lead scoring but could not tell why it rated a lead the way it did
- Replies to prospects must never go out without a person signing off
Not for: Outbound prospect lists, where there is no incoming message to check claims against; Teams with only a few inquiries a week, where reading them directly is faster; Setups without any chat or form step where a person can approve drafts
What do you need, and what do you get?
You need
- A form or webhook that delivers name, email and message
- Three to six written qualification rules, such as service area, budget range or project type
- CRM access for creating or updating contacts and deals
- A chat channel for approvals
You get
- A verdict per inquiry: good lead, ask for more information, or decline
- A per-rule assessment with the supporting quote, saved as a CRM note
- A short reply draft that asks only for the missing details
- A logged approval decision for every outgoing message
How does it work, step by step?
- Fingerprint each inquiryNormalize the email and message, hash them and skip any fingerprint you have already processed so double submissions never get two replies.
- Filter junk before AIDrop entries without a valid address or with a near-empty message before spending a model call on them.
- Score rule by ruleAsk the model to mark each rule as satisfied, failed or unclear, with the exact supporting words, using a structured output format.
- Check the quotes in codeSearch the original message for every quote. A positive claim whose quote is missing becomes unknown; an absence claim may stand without one.
- Draft, approve, then sendWrite a reply that asks only about unknown rules, post it for approval with send, edit or skip options, and record the choice.
The prompt
Our own prompt, inspired by Kingsley_Ken and written to work in n8n, Claude and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You assess one inbound inquiry for {business_name}. Rules to check: {rules} For each rule return JSON with: rule, status (satisfied, failed or unclear), and evidence, which must be copied character for character from the inquiry. Leave evidence empty when a rule failed because something is missing, or when it is unclear. Never infer budget, timing or location that the sender did not write. Then give an overall result: good lead, ask for more information, or decline. Inquiry: {message}
Inspired by Kingsley_Ken: n8n Community: an AI lead qualifier that is not allowed to trust itself. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Requiring a quote for every verdict wrongly penalizes 'not a fit' decisions, since you cannot quote something that is missing. Exempt absence claims.
- Exact string matching fails on small rewording. Normalize case and spacing, and log near misses for review.
- Keep prices and availability out of the drafted reply unless a person adds them.
- Store business rules in one settings step; reusing the build for another client then means changing a single node.
Our take
This is one of the cleanest answers we have seen to the question of how far to trust a model's judgment in a sales workflow. The answer here is: only as far as ordinary code can confirm it. Asking the model to justify each rule with words from the inquiry is common; checking those words against the message in a separate step is not, and it closes the door on invented reasons. The author's own testing story is the most useful part. The first version treated a missing quote as a failure everywhere, which pushed obvious sales pitches into the pile waiting for more information. The fix (positive claims need evidence, absence claims do not) is a rule worth copying into any evidence-checking workflow. Our caution is matching: real inquiries contain typos and pasted text, so loosen the comparison slightly and review near misses. In our dry run with six fictional inquiries for an electrical contractor, a fabricated budget quote was caught and downgraded.
Where the time goes back: Inquiries arrive in the CRM already sorted, with the reasons attached and a reply drafted, so the salesperson spends a minute approving instead of ten minutes reading, judging and typing.
FAQ
Why not just trust the model's score?
Which CRM did the author use?
How much of the workflow is AI?
Source and credit
Inspired by Kingsley_Ken. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- n8n Community: an AI lead qualifier that is not allowed to trust itself
- Creator
- Kingsley_Ken
- Published on
- n8n Community
- Original date
- Nov 7, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- n8n
- AI dry run
- Nov 7, 2026: passed. Dry-run tested by our AI test agent on sample input. Fabricated evidence caught by the code check, absence claims allowed without quotes, drafts ask only for missing details.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 8, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.