← Back to library

Check every AI sales email against approved claims

u/mastafied on r/AI_Agents, a solo founder selling software to insulation contractors, runs about sixteen agents for research, outreach and CRM. The copywriting agent kept promising features the product lacks, so an allowlist gate now blocks unapproved claims before any email leaves.

  • OutcomeStop AI-written outreach from promising things your product doesn't do, and make do-not-contact rules impossible to skip.
  • SetupAn afternoon+
  • LevelAdvanced
  • Creditu/mastafied on r/AI_Agents
View original
Works with
Claude CodeClaudeCustom agent

Published Oct 20, 2026Updated Oct 20, 2026AI dry run on sample input: passed Oct 20, 2026Source verified Oct 24, 2026

When should you use it?

  • An agent drafts emails, posts or replies that customers will read
  • You've caught it overstating features, prices or results
  • You have rules (do-not-contact, regions, opt-outs) that must never be broken

Not for: Replacing human review of high-stakes messages such as contracts or pricing commitments

What do you need, and what do you get?

You need

  • A plain list of claims you're happy to make about your product, with exact wording where it matters
  • Your do-not-contact and opt-out lists
  • The drafts your writing agent produces

You get

  • Each draft marked pass or fail, with the sentence that broke a rule
  • Failed drafts sent back for rewriting instead of going out
  • Sends to blocked addresses refused by code, not by instruction

How does it work, step by step?

  1. Write the claims listList what the product does today, in short factual lines. Anything not on the list is treated as a claim you can't make.
  2. Add the checkerBefore any send, run our prompt on the draft with the claims list. Only drafts marked pass move on.
  3. Move hard rules into codePut do-not-contact and opt-out checks in the sending step itself so no prompt can override them.
  4. Review the rejects weeklyPatterns in failed drafts show where the writing instructions need changing.

The prompt

Our own prompt, inspired by u/mastafied on r/AI_Agents and written to work in Claude Code, Claude and Custom agent. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt2 variables
You are a strict reviewer. Below is our list of approved claims, then a draft message.
Approved claims:
{claims_list}
Draft:
{draft}
Check every sentence in the draft that says or implies what our product does, costs, integrates with or achieves. If it matches an approved claim, it's fine. If it goes beyond one, or you aren't sure, it fails.
Answer with: PASS, FAIL or REVIEW; then each problem sentence and the closest approved claim (or 'none'). Don't rewrite the draft.

Inspired by u/mastafied on r/AI_Agents: running ~16 agents for a one person business while employed full time: what actually broke and what actually worked. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • A second model judging the first can miss things too. Keep humans reviewing a sample, and send anything uncertain to review rather than letting it pass.
  • Claims lists go stale. Update them when features ship or are dropped.

Our take

This is one of the most useful lessons we've seen from someone running agents for real customer-facing work: rules written in a prompt are requests, and the ones that truly matter belong in code. The poster found the writing agent kept hinting at product capabilities that didn't exist. Prompt warnings helped but didn't solve it, so they added a separate checker holding a strict set of approved statements that rejects anything else, and moved do-not-contact into the sending step so blocked addresses simply can't be emailed. Both ideas apply well beyond sales email, to support replies, social posts and anything else an agent writes in your name. The founder is candid that a second model checking the first is crude, and we agree it isn't foolproof, so our prompt fails anything unclear rather than passing it. In our dry run we gave it a claims list of 9 lines for a made-up invoicing app and 6 drafts; it passed 3, failed 2 that mentioned an unlisted integration and a made-up time saving, and sent one back to review because a sentence about pricing was ambiguous.

Where the time goes back: You stop reading every draft line by line for invented promises, and you don't spend time apologizing for messages that should never have gone out.

FAQ

Why not just tell the writing agent not to exaggerate?
The founder tried that; instructions reduced the problem but never removed it. A separate check against a fixed list catches what slips through.
Did the outreach actually work?
The founder reports 214 emails sent, replies from 3.3% of recipients, and one qualified pilot customer found by the pipeline, and noted that a phone call beat a third email for one interested contact.

Source and credit

Inspired by u/mastafied on r/AI_Agents. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
running ~16 agents for a one person business while employed full time: what actually broke and what actually worked
Creator
u/mastafied on r/AI_Agents
Published on
Reddit
Original date
Jul 22, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Custom agent
AI dry run
Oct 20, 2026: passed. Dry-run tested by our AI test agent on sample input. Caught invented claims and sent the ambiguous case to review.
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
Oct 24, 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.

More in Sales

All 59 Sales playbooks →

Related playbooks

SalesWorkflow✓ AI dry run

Review a teammate's Clay build by questioning a coding agent

Before you review an automation a teammate built in Clay, ask them to explain the decisions and assumptions behind it, then point a coding agent at the build through Clay's command-line tool and question it about logic, edge cases and sample records, so you can give specific feedback in minutes instead of clicking through every column yourself.

Credit: Petra Hajal

Under an hour
SalesWorkflow✓ AI dry run

Have a browser agent build a public research list

Give a browsing agent a clear research goal on public pages, watch it collect a structured list with links, and stop it before logins or outreach.

Credit: u/No-Definition-2886 on r/ChatGPTPro

Minutes
SalesPrompt✓ AI dry run

Watch local Facebook groups for home-service lead posts

Have Meta Muse (or another agent with Facebook access) watch the community groups you already belong to, alert you when someone asks for your trade, and draft a reply you send yourself.

Credit: Josh Stevens

Minutes