How to Use Muse to Draft Emails
Use Muse, Meta's AI agent, to draft emails in your tone for clients, job applications, or tricky conversations. Muse checks before anything is sent. Prompts inside.
Can Muse Do This?
Muse, Meta's personal AI agent, treats email as a headline ability: Meta's announcement explicitly lists sending emails among what it does, and writing happens before sending. You give Muse the context — who it's going to, what you need, how you sound — and it can pull background facts from connected threads so the draft isn't generic. The critical control is that Meta says Muse checks with the person before sensitive actions like sending an email, and in settings you can go further by granting read-only access, which makes every send a copy-paste job you do yourself. Voice is the part to invest in: the more you tell it about your phrasing habits, the less editing you'll do. And since this is a launch-week product, budget for drafts that miss the tone on the first pass — the fix is better context, not more retries.
- Muse only sounds like you if you describe how you write; expect a few rounds of tone-tuning on a new account.
- It can only see context in the services you connected — if the backstory lives in a document or another app, paste the relevant bits into the prompt.
- Press reporting on launch week describes tasks that sometimes fail or need restarting, so keep your own copy of anything time-sensitive.
How to Ask Muse
- 1
Give the recipient and the goal, not just the topic
'Email the client' is weak. 'Email Marcus to move the launch to the 18th without alarming him — he's anxious about deadlines' gives Muse the outcome and the human read.
- 2
Describe your voice with examples
Three traits beat one adjective: 'short sentences, no exclamation marks, I open with the ask and close with a thank-you.' You can also point Muse at sent mail in the connected account.
- 3
Tell it where the facts live
Ask it to pull specifics — dates, figures, names — from the relevant threads so the draft quotes reality instead of inventing placeholders you might miss.
- 4
State length and constraints
Word caps, forbidden words, and whether to CC anyone. Constraints early save a rewrite cycle later.
- 5
Decide the send path before you start
If your access level allows sending, add an explicit 'show me the draft and wait for my OK.' With read-only access, sending stays yours no matter what.
Copyable Muse Prompt
Replace the bracketed details with your own, then paste it into Muse.
Goal: Draft [NUMBER, e.g. three] emails I need to send this week from [ACCOUNT OR FOLDER]. Context: I'm [YOUR ROLE, e.g. a freelance illustrator]. My voice: [TONE NOTES, e.g. warm, short sentences, no corporate filler, I open with the point]. Requirements: - Email 1: [PURPOSE, e.g. project update to a client] — cover [KEY POINTS] and stay under [WORD COUNT]. - Email 2: [PURPOSE, e.g. polite price-increase notice] — firm but warm, no apologizing twice. - Email 3: [PURPOSE, e.g. nudge to a supplier] — reference [SPECIFIC DETAIL] so it's clear I checked. Actions: - Pull names, dates, and figures from [SOURCE THREADS] in my connected mail so nothing is invented. - Draft each one, then hold for my edits before preparing a final version. Approval: Show me every draft before it is sent. Sending email is a sensitive action — send nothing until I explicitly say "send" for each individual email. Output: All drafts with subject lines, plus one-line notes flagging anything you were unsure about.
Example
A job seeker who needs a thank-you note after a final-round interview and a graceful decline of a different offer.
Two drafts, please. First, a thank-you email to Jordan Chen after yesterday's final-round interview for the data analyst role — reference the pricing-dashboard project we discussed, keep it under 150 words, warm but not gushing. Second, a gracious decline to Brightline Media for their offer: genuine thanks, name one thing that made the decision hard, keep the door open, under 100 words. Pull names and details from the actual threads in my inbox so nothing is wrong. Show me both drafts for edits. Neither email gets sent until I've read it and said send.
What Information Should You Provide?
Recipient and your read on them
Tone calibration — formal, breezy, careful — comes from who's receiving it and what they're feeling.
Your voice in concrete terms
Sentence length, greetings, words you never use: this is the difference between a draft you send and one you rewrite.
Source threads for facts
Muse should quote real dates and figures from the connected account instead of filling gaps with plausible guesses.
Hard constraints
Word limits, required or banned phrases, CC list — all cheaper to state upfront than to fix after.
Your access level
Read-only versus can-send determines whether the draft goes to you or straight out the door; check it before the task starts.
Approval and Safety
For this task, it is smart to make Muse check with you before it takes certain actions. Decide your rules up front and include them in the prompt.
Every send, without exception — Meta is explicit that Muse checks before sensitive actions like sending an email — review each draft and approve each send individually.
First contact with a new recipient — A wrong address or a misjudged tone does the most damage on a first impression; never let an unsupervised first email fly.
Emails involving money, offers, or commitments — Accepting terms, quoting prices, or declining an offer should have your eyes on every line before it leaves.
Tips for Better Results
- Save your tone description somewhere reusable — paste it at the top of every drafting prompt and the outputs get consistent.
- Ask for two tone variants ('one warmer, one blunter') in a single request; comparing drafts is faster than iterating on one.
- For difficult emails, tell Muse the outcome you want ('relationship intact, decision unchanged') — it frames the message better than 'write a no.'
- Have Muse check its own draft against the source thread for dates and amounts before showing it to you; catches most factual slips.
- Read-only access plus manual sending is a perfectly good setup while you learn how reliable the drafts are.
Draft Email FAQ
Can Muse send emails for me?
Yes — sending email is listed among Meta's own examples of what Muse does — but only if you grant send access, and Meta says Muse checks with you before sensitive actions like sending an email. You can also stay read-only and handle every send yourself.
Will Muse send an email without asking me?
Meta's approval model says it checks before sending, and the audit trail shows everything it has done and plans to do. Still, verify your access settings when you connect the account — read-only access makes unauthorized sending impossible rather than just unlikely.
Can Muse write emails in my voice?
It can approximate your voice if you describe it concretely, or point it at sent mail in the connected account. Expect a tuning period: the first drafts skew generic, and your feedback ('shorter, no exclamation points') is what sharpens them.
Can Muse reply to emails automatically?
Technically possible with send access, but inadvisable in week one. A better pattern is Muse drafting replies for review — you approve the wording, it handles the mechanics. For threads involving money or commitments, keep the final read yours.
Can I edit a draft before it goes out?
Yes — ask Muse to hold drafts for review and edit by conversation until the wording is right, then approve the send. The back-and-forth editing loop is exactly what the agent is built for, and each revision is faster than starting over.
Create Your Own Muse Prompt
Adapt this template to your exact situation with the free MuseTask prompt generator — set your goal, constraints and approval rules, then copy the result into Muse.
Open Prompt Generator →