Email and Communication with Muse (Meta AI)

Draft from a brief, not from a blank page

The hardest part of writing an email is starting. Muse removes that problem. Give it a short brief instead of asking it to write from nothing: who the message is for, what you want them to do, the key facts, and the tone you want. A brief of three or four lines is usually enough to get a solid first draft.

Include the action you want. Many weak emails describe a situation but never say what the reader should do. End your brief with the ask: approve this, confirm a time, send a document, or reply by a date. When the ask is clear in the brief, it will be clear in the draft.

Read the draft as the recipient would. Does the first sentence say why you are writing? Is the request easy to find? Would a busy person understand it in one read? If not, tell Muse what to fix rather than rewriting it yourself from scratch.

Adjusting tone for the reader

The same message needs a different tone for a client, a colleague, and a stranger. Tell Muse who the reader is and how formal the relationship is, and ask it to adjust the draft. A message to a long-term client can be warm and direct. A first message to a new supplier should be polite and precise. A message about a problem should be calm and factual, never heated.

Tone adjustments work best on a draft you already have. Paste your draft and ask Muse to make it more polite, more direct, or shorter, and compare the versions. Keep the version that sounds like you on a good day, not the version that sounds most formal. Over-formal writing feels distant, and readers trust a natural voice more than a stiff one.

Be careful with tone in sensitive messages. If you are annoyed, write the draft, let it sit, and then ask Muse to make it calmer and more factual before you send anything. A message sent in anger is hard to undo, and a short delay costs nothing.

Draft a short email to a client. The situation: their project delivery will be three days late because a supplier shipment was delayed. The ask: confirm that the new date, Friday, works for them. Tone: honest, calm, and professional, no excuses and no excessive apology. Keep it under 120 words.

Shortening a long draft

Long emails often bury their point. Paste a draft and ask Muse to cut it to half the length while keeping the request, the deadline, and any facts the reader needs to act. Then read the shortened version and check that nothing essential was lost. Shortening is a judgement task, so the final call is always yours.

A useful structure for most business emails is three short parts: why you are writing, what you need, and what happens next. If your email does not fit that structure, something in it probably does not belong there. Move background detail to an attachment or a link instead of the body.

Subject lines deserve the same treatment. Ask Muse for three subject line options for an important email, and pick the one that tells the reader what the email is about and whether action is needed. Vague subjects such as update or quick question get ignored or opened late.

Difficult messages: delays, refusals, and apologies

Difficult messages are where Muse earns its keep. A delay, a refusal, or an apology needs to be honest without being defensive, and firm without being rude. Tell Muse the facts plainly, including the part you would rather soften, and ask for a draft that states the facts, takes responsibility where it belongs, and offers a clear next step.

For refusals, the next step matters as much as the no. A refusal with an alternative, a referral, or a later date is much easier to receive than a bare no. Ask Muse to suggest one or two constructive alternatives you can offer, and pick the one you can actually deliver.

For apologies, keep them short and specific. Name what went wrong, say what you are doing about it, and stop. Long apologies that repeat the problem or pile on excuses make the reader relive the failure instead of moving past it.

Replies and routine messages

Routine messages are a good place to build a habit. For common situations, such as confirming a meeting, thanking someone, following up on an unanswered email, or asking for a document, describe the situation once and ask Muse for a template you can reuse. Save the templates you like in your own notes, and adapt them each time rather than generating from scratch.

Follow-ups deserve care. A good follow-up is short, polite, and easy to answer: a reminder of the original request, a single question, and no guilt. Ask Muse to draft follow-ups that assume the other person is busy, not ignoring you, because that assumption is usually right and it keeps the relationship intact.

Always check before you send

Muse does not send email, and that is a strength. Every draft passes through your hands before it goes out, which gives you a final check. Use it: confirm names, dates, amounts, and attachments, and read the message once out loud. Errors in those details damage credibility far more than an imperfect sentence.

Never paste confidential information into a draft request that does not need it. Replace real names, figures, and private details with placeholders when you are only working on wording and structure, and fill in the real details yourself before sending.

Frequently asked questions