Work · Community report
Draft email replies in your voice
Muse checks one person's email and drafts email replies in their voice, according to their post on X. There is no example draft and no word on whether replies go out automatically or only after review, so this guide sets it up so nothing is sent until you approve it.
What you can get
What it is
Drafted email replies
Draft replies to your email, written in a voice intended to match your own, for you to review; one report describes this as a regular part of their email handling, with no specific example of a drafted reply or whether it is reviewed before sending.
It came back right when
- Every drafted reply is shown to you before being sent, not sent automatically.
- Drafts read like your own voice, not a generic assistant tone.
- No factual claim in a draft goes unchecked before sending.
- Messages that shouldn't get an automatic draft (sensitive or high-stakes ones) are flagged instead of drafted blindly.
The checks are editorial, not from the source.
- Provide voice samples
Share real past replies covering a range of tones and situations.
- Set drafting rulesStops for your approval
Decide which senders or topics get an automatic draft versus a flag for you.
- Draft replies
Have it check the inbox and draft a reply for each message needing one.
- Review before sendingStops for your approval
Check each draft for tone and factual accuracy before it goes out.
Editorial, not from the source
Works when
- You get enough routine email that drafting replies yourself is a time sink.
- You're comfortable giving inbox access and some writing samples to match your tone.
- You will review drafts before they go out, at least at first.
Does not work when
- Your email requires precise factual accuracy that a drafted guess could get wrong, such as legal or contractual replies.
- You want replies sent without review; the available report doesn't confirm this is safe to rely on.
- Your writing voice varies a lot by recipient, which the agent may not pick up on without being told.
Email replies in your voice: review template
| Draft basis | Status | |
|---|---|---|
| [Sender/subject] | [Voice sample used] | [Reviewed] |
| [Email needing commitment] | [Flagged for manual reply] | [Handled by you] |
| [Routine confirmation] | [Drafted automatically] | [Approved to send] |
The source case
On X, @Damien_Ducate lists several things Muse does for them, including that 'it checks my email, drafts replies in my voice, and keeps me organized.' The same post separately praises how well it understands intent on the first try. No detail is given on how many emails this covers, how closely the drafted replies actually match their voice, or whether drafts are sent automatically or only after review. This is one individual report, checked on 2026-10-09, describing the capability as used, not a specific example of a drafted reply or its outcome.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
It checks my email, drafts replies in my voice, and keeps me organized.
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring Examples of your own writing style, if you want the voice matched closely, Which senders or topics should never get an automatic reply drafted. Acts Reads incoming email to identify messages needing a reply. Drafts replies for your review; the report does not state whether any are sent without review. Source community report, checked 2026-10-09.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- Examples of your own writing style, if you want the voice matched closely
- Which senders or topics should never get an automatic reply drafted
Connected
- Your email inbox
Approved by you
- Your review before any drafted reply is actually sent
How to try it
Editorial, not from the source
- Give the agent access to your email inbox and, if possible, some examples of how you typically write.
- Have it check your inbox and identify which messages actually need a reply.
- Have it draft a reply for each, written to sound like you rather than a generic assistant response.
- Review every draft before it's sent; edit anything that doesn't sound right or gets a fact wrong, rather than sending drafts automatically.
Give it something real to sound like
Asking an agent to 'write like me' without examples usually produces a generic, overly formal draft that technically answers the email but doesn't read like something you'd actually send. The available report mentions replies drafted 'in my voice' as a working feature, but gives no detail on what made that work, so treat providing real writing samples as your own responsibility rather than assuming tone-matching happens automatically. Share a handful of actual past replies, ideally ones covering a range of situations: a quick casual reply, a more formal one, and one declining or pushing back on something. The more varied and real the samples, the less likely the agent is to default to a flat, assistant-sounding tone that technically resembles you but reads as obviously drafted by something else.
Decide what gets drafted automatically and what doesn't
Not every email in your inbox deserves the same treatment. Routine replies, like confirming a meeting time or acknowledging receipt of something, are lower-stakes to have drafted than anything involving a commitment, a sensitive relationship, or information you'd want to check carefully before sending. Set explicit rules for which senders, topics, or types of request should get an automatic draft and which should be flagged for you to write yourself from scratch. The available report doesn't describe this kind of filtering happening on its own, so build it in deliberately rather than assuming the agent will correctly judge which emails are safe to draft without guidance and which deserve more care.
Review drafts before they go out, every time at first
A reply that sounds like you is not automatically a reply that is accurate or appropriate; tone and correctness are two different things. Review every drafted reply before it's sent, checking specifically for factual claims, commitments, or tone that doesn't match the actual relationship with the sender, since a voice-matched draft can still get the substance wrong. As you build confidence that drafts are consistently accurate for certain low-stakes categories, such as scheduling confirmations, you might choose to loosen review there, but keep reviewing anything involving a commitment, a sensitive topic, or a sender you don't want to risk a wrong tone with. The available report gives no indication of how this review step is handled in practice, so set it up yourself rather than assuming it's built in.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- One individual report mentions this capability in a list of several things the agent does; it gives no specific example of a drafted reply, no count of how many emails this applies to, and no detail on how closely the tone actually matched.
- No detail is given on whether drafts are sent automatically or only after the user reviews and approves them.
- This directory has not run this task itself and cannot confirm how reliably it avoids factual errors or mismatched tone across a real inbox.
Stop and check
Editorial, not from the source
- Before it starts: confirm which inbox and which types of messages it should draft replies for.
- Before sending: review each draft for tone, accuracy, and whether it actually says what you'd say.
- Ongoing: periodically check that drafts still sound like you as your own writing or priorities shift.
If it goes wrong
Editorial, not from the source
- The drafted reply doesn't sound like you
- Give more examples of your actual past replies so the tone has something concrete to match, rather than a generic description of your style.
- A draft states something that isn't accurate
- Review every draft before sending; the available report doesn't confirm how reliably factual accuracy is checked.
- You're not sure which messages are being drafted for
- Set explicit rules for which senders or topics should get a draft and which should be left for you to handle directly.
Common questions
How does it learn to write in my voice?
This isn't detailed in the available report. Give it real examples of your own past replies, covering a range of tones, rather than assuming it will infer your style from nothing.
Are drafted replies sent automatically?
The available report doesn't say. Set up a review step yourself so you see each draft before it's sent, at least until you've built confidence in specific low-stakes categories.
Will it get facts wrong in a drafted reply?
This isn't confirmed either way by the available report. Review every draft for factual accuracy, since sounding like you and being correct are two different things.
Should every email get an automatically drafted reply?
No. Set rules for which senders or topics get a draft and which you'd rather handle yourself, especially anything involving a commitment or a sensitive relationship.
Can it match different tones for different people I email?
The available report doesn't describe this level of detail. If your voice varies by recipient, say so explicitly rather than assuming one tone fits every reply.
Next
Related to this task
More in Work
Get recurring task recommendations — ask your own agent to check for relevant updates.