When should you use it?
- Several agents draft or send email for you and their quality varies
- Drafts ask questions the thread already answered or slip in commitments you never made
- You keep fixing the same things in agent drafts and want the fixes to stick
Not for: Giving agents new permission to send; the prompt keeps your current sending and approval settings; Bulk marketing campaigns, which need their own compliance and unsubscribe handling; Regulated messages, such as legal notices, that need specialist review
What do you need, and what do you get?
You need
- A lead agent that can read and propose changes to your other agents' instructions
- A few examples of emails you wrote yourself, to show your usual tone
- Your existing rules on who may send what without approval
You get
- One set of drafting standards applied to every email-handling agent
- A list of conflicting or duplicated email instructions found across agents, with proposed fixes
- After each edit you make, a short lesson and a proposed instruction update for your approval
- Unchanged sending permissions and approval steps
How does it work, step by step?
- Paste the promptGive Fenech's prompt to your lead agent and point it at every agent that drafts or sends mail.
- Review the auditRead its list of conflicting or repeated email instructions and approve the proposed cleanup.
- Share your voiceProvide a handful of emails you wrote so tone matching has something real to follow.
- Edit as usualKeep correcting drafts the way you normally would; each edit triggers a proposed lesson.
- Approve lessons selectivelyAccept the lessons that reflect a lasting preference and reject one-off changes.
The prompt
The original prompt by Michael Fenech (@Michael_Fenech_), word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Grok Bot, Claude Cowork, ChatGPT agent and others. Values in lime are placeholders.
Original prompt by Michael Fenech (@Michael_Fenech_)
Upgrade how my Grok Bot team handles outgoing emails. Apply these six standards to every Bot responsible for drafting or sending emails. 1: INTENT - Before drafting, identify what the email needs to achieve and what response or action we want from the recipient. 2: CONTEXT - Review the relevant email thread, previous conversations and available information. Don't ask questions that have already been answered. 3: TONE - Match my communication style and the relationship with the recipient. Write naturally, without unnecessary formality, filler or generic AI language. 4: ACCURACY - Verify facts, names, dates, prices and previous commitments. Never invent discounts, deadlines, guarantees or promises that I haven't authorised. 5: CLARITY - Make the email concise, easy to understand and actionable. Put the important information first. Make any requested next step obvious. 6: FINAL CHECK - Before sending, verify the recipient, subject, attachments, unanswered questions, commitments and whether the email actually achieves its purpose. LEARNING RULE: Whenever I edit or correct an email, compare my version with the original. Identify the underlying lesson and propose an improvement to the relevant Bot's instructions. Don't apply permanent instruction changes without my approval. Review the current email instructions across my Bots, identify conflicts or duplication, and show me your proposed changes before implementing them. Preserve my existing sending permissions and approval requirements.
Exactly as published by Michael Fenech (@Michael_Fenech_) in X post: a six-part email upgrade for Grok Bot teams, with a rule for learning from edits.
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
Set one standard for every agent on {platform} that writes or sends email for me. Before drafting: state the goal of the message and the reply or action I want. Read the full thread and related notes so you never re-ask something already answered. While drafting: sound like me, using these samples: {my_email_samples}. Keep it short, put the key point first and make the next step obvious. Facts: confirm names, dates, prices and earlier promises against {fact_sources}. Never offer a discount, deadline or guarantee I have not approved. Before sending: check the recipient, subject, attachments and any open questions. When I change a draft, tell me what you learned and suggest an instruction update, but apply nothing until I agree. First, list conflicting or repeated email rules across my agents and propose fixes. Keep all current send permissions and approvals unchanged.
What can go wrong?
- Approving every proposed lesson can bloat instructions. Accept only changes you would want applied to every future email.
- Accuracy checks need the facts somewhere the agent can see, such as the thread, CRM or price list. Without them it should ask, not guess.
- A final check cannot catch a wrong recipient pulled from a bad contact record. Keep contact data clean.
- If two agents keep different style notes, they will drift apart again. Store the shared standards in one place.
Our take
Telling an agent to write better emails rarely works because better is not an instruction. Fenech's version replaces it with a process an agent can actually follow: decide what the message is for, read the thread first, match the relationship, check every fact and promise, lead with what matters, and run a final check before sending. The accuracy standard is the one we would never drop, since an invented discount or deadline is the kind of mistake that costs real money. The learning rule is the clever part: your edits become proposed lessons, but nothing changes permanently without your approval, so preferences accumulate without instructions running wild. Our caution is restraint, because approving every small lesson will eventually make the instructions longer than the emails. In our dry run with three fictional agents and a customer asking for a delivery date and a discount, the drafting agent confirmed the Friday date already promised in the thread, flagged the discount as needing the owner's decision, and caught a missing attachment, while the audit found one agent told to write formally and another told to keep things casual, and proposed a single tone rule.
Where the time goes back: Drafts arrive closer to send-ready, the same fixes stop recurring, and the pre-send check catches missing attachments and unanswered questions before you do.
FAQ
Will this let my agents send email without me?
Does it work for agents other than Grok Bot?
How are lessons learned from my edits?
Source and credit
The original prompt on this page is by Michael Fenech (@Michael_Fenech_), shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- X post: a six-part email upgrade for Grok Bot teams, with a rule for learning from edits
- Creator
- Michael Fenech (@Michael_Fenech_)
- Published on
- X
- Original date
- Oct 28, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Grok Bot
- AI dry run
- Oct 29, 2026: passed. Dry-run tested by our AI test agent on sample input. No invented discount, facts checked against the thread, conflict found and fixed only on approval, lesson proposed not applied, permissions preserved.
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 29, 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.