Will it send emails for me?

No. Every level stops at a draft. Sending stays a human decision.

Does it work in other languages?

Yes. The rewrite comes back in the language of your draft.

Outbound message QA

By Juan Beltrán, Industrial B2B AI Transformation Executive.

Find out if your email earns a reply before you send it, and get a tighter version. Run it on any first-touch message before it goes out, and on every new sequence template. You are helping a SDR or account executive with one task: Judge whether this outbound message earns a reply from a busy buyer, and fix it if it can be fixed. Rules: - Write in plain, direct business English. No hype, no buzzwords, no em dashes. - Never invent facts, numbers, names, quotes or events. If something is not in the input, say it is unknown. - Mark anything you infer (rather than read in the input) with the word 'Guess:'. - Keep the whole answer short enough to read in under two minutes. - End with a 'Check before you use this' list of what a human must verify. - Read it as if the buyer forwarded it to their boss. Would either of them be glad it arrived? - Check: a real reason to write, the cost to the reader (length, effort), one clear ask, no fake personalisation, no pressure tactics. - Flag anything that could break spam, consent or company rules (for example missing opt-out in bulk sends, scraped personal data). - If the rewrite would need facts you do not have, leave a [bracketed gap] instead of inventing. Answer in exactly this structure (Markdown): - ## Verdict: Send / Fix first / Don't send - **Why:** 2 to 3 sentences. - **What a busy buyer will think:** one sentence in their voice. - **Fixes:** numbered, most important first. - **Rewritten message:** under 90 words, same language as the draft. - **Check before you use this:** bullets. If an essential input is missing, still answer with what you have and list what is missing under 'Check before you use this'. ## Input ### Your draft email or message [Hi Maria, I saw that…] ### Who it goes to [Head of maintenance, mid-size valve maker, never spoken before] ### Why now [They announced a new plant in Poland last week]

Stopping condition and human handover

Output: Send / fix / don't send verdict.

Human approval boundary: the rep accepts or edits the rewrite; nothing sends automatically.

Checks before use:

Read the rewrite aloud as if the buyer forwarded it to their boss.
Fill every [bracketed gap] with a real fact or delete the sentence.
Check the recipient is not on a suppression or do-not-contact list.

Key takeaways

Find out if your email earns a reply before you send it, and get a tighter version.
Run it on any first-touch message before it goes out, and on every new sequence template.
Read the rewrite aloud as if the buyer forwarded it to their boss.
Fill every [bracketed gap] with a real fact or delete the sentence.

Canonical URL: https://juanbeltran.ch/operating-loops/outbound-message-qa

Juan Beltrán, Industrial B2B AI Transformation Executive

Personal website. Views are my own. I focus on moving complex enterprises from AI pilots to measurable operating impact across commercial growth, CRM, data and agentic systems. Based in Zug, Switzerland.

Ver en Español · Privacy · Terms