3.3Outlook email drafts
The essentials in 30 seconds
- From three words to an email: “Draft with Copilot” turns keywords into a complete message, with length (short/medium/long) and tone settings.
- The reply reads the thread: Copilot relies on the exchange context (people, subject, tone) for a coherent reply.
- Your voice, your proofreading: adjust the default smooth tone until it sounds like you — and never click Send without proofreading.
Running mini-case — Hicham sends three delicate emails
Hicham, administrative assistant in Algiers, starts his day with three emails to write: declining a Thursday meeting, chasing a late supplier, replying to a management thread. With “Draft with Copilot”, he generates each one from a few keywords (“politely decline, suggest Friday 2pm, warm tone”), sets length and tone, adds one personal sentence to each — then proofreads recipient, time slots and commitments before sending. Three emails sent in ten minutes, with no tone mistake.
This same case returns in the lesson, the diagram, the script and the 48h challenge.
1. From three words to an email: draft and settings
In Outlook, “Draft with Copilot” turns a few keywords into a complete email. “Politely decline the Thursday meeting, suggest Friday” becomes a polite, structured message. The time saving is immediate on Hicham's daily correspondence in Algiers.
Two settings come with generation: length (short/medium/long) and tone (formal, casual, direct). You frame in two clicks what would have taken five minutes to calibrate by hand — then refine by instruction (“warmer”, “more direct”).
2. Replying in context — and keeping your voice
Even more useful: the contextual reply. On a received email, “Reply accepting and asking for the agenda” — Copilot reads the thread and generates a coherent reply, without you rereading the whole history. It relies on context: people, subject, tone of the exchange.
Major watch point: email is your voice. Copilot's default tone is sometimes too smooth, too corporate — adjust it until it sounds like you, add a personal sentence. And the golden rule remains absolute: never click “Send” without proofreading — recipient, tone, commitments, promised attachments.
🔎 Concrete example — Declining an invitation without offending
Hicham must decline a meeting while staying open and courteous.
“Draft with Copilot: politely decline the Thursday meeting, explain a calendar constraint, suggest Friday 2pm or Monday morning. Warm but professional tone.”
Reading: a courteous email with a concrete alternative, in seconds.
Lesson: check the suggested slots, adjust the tone, proofread — then send.
Section vocabulary
- Draft with Copilot
- In Outlook, turns a few keywords into a complete email, with length and tone settings.
Simple example: Hicham's polite decline with alternative slots.
What it is not: automatic sending without proofreading.
Reflex: describe objective + tone + length in the prompt.
- Length and tone
- Short/medium/long and formal/casual/direct: two settings to frame the message in two clicks.
Simple example: Hicham's “warm but professional” in 5 lines.
What it is not: the smooth corporate tone left by default.
Reflex: set then refine to your voice.
- Contextual reply
- On a received email, Copilot reads the thread and generates a coherent reply without rereading the whole history.
Simple example: Hicham's reply to the management thread.
What it is not: a reply written in a vacuum, out of context.
Reflex: check that it captured the thread's request.
- Your voice
- Email commits in your name: adjust the default smooth tone until it sounds like you, and always proofread.
Simple example: The personal sentence Hicham adds to each draft.
What it is not: a generic recognizable “AI email”.
Reflex: at least one personal touch before sending.
In practice — Write and calibrate three real emails
- Take three emails to write today (one request, one decline, one reply to a thread).
- Generate each one with “Draft with Copilot” from a few keywords.
- Set length and tone, then adjust (“more direct”, “warmer”) to your voice.
- Proofread each draft — recipient, tone, commitments — before clicking “Send”.
Ready-to-say script — explaining your email method (30 s)
“I generate each email from three keywords: objective, tone, length. On a thread, I let Copilot read the context. I adjust to my voice with one personal sentence, then I proofread recipient and commitments before sending — never send directly.”
Say to a colleague; show the before/after of the tone setting.
Copy-paste template — email prompts
“Politely decline the Thursday meeting, suggest Friday 2pm or Monday morning, warm but professional tone, 5 lines max.”
“Reply to this thread: thank, answer the two questions asked and set a Friday deadline, direct tone.”
“Make this draft warmer, short sentences, without changing the commitments.”
Freelancer
One prompt with objective + tone + length is enough to send delicate client emails.
SME in Algiers
Hicham handles request, decline and thread reply in ten minutes, proofread one by one.
Support team
Keep a library of standard phrases to guide Copilot toward the house style.
Beginner
This week: three generated drafts, one compared tone setting, zero sends without proofreading.
✓ Best practices
- Set the tone at generation time, then refine: the default smooth corporate tone does not always sound like you.
- On a reply, let Copilot read the thread: you save rereading the whole history.
- Keep a library of your standard phrases to guide Copilot toward your usual style.
✗ Common pitfalls
- Clicking “Send” without proofreading: email commits a tone, a recipient, a promise.
- Leaving the tone too smooth and impersonal: adjust to your voice.
- Trusting a contextual reply without checking that it captured the thread's request.
Key takeaways
- “Draft with Copilot” turns a few keywords into a complete email, with adjustable length and tone.
- The contextual reply reads the thread and replies coherently, without rereading the whole history.
- Email is YOUR voice: adjust the default smooth tone until it sounds like you.
- Never click “Send” without proofreading: email commits in your name.
48h challenge — apply tomorrow
Generate 3 real emails (request, decline, thread reply) with set tone + 1 personal sentence each, all proofread before sending.
- I frame each draft (objective + tone + length).
- My thread replies are checked against the request.
- No email goes out without full proofreading.
Frequently asked questions
Does Copilot really read the thread to reply?
Yes, on a reply it relies on the exchange context (people, subject, tone). Still check that it understood the request before sending.
How to avoid the impersonal “corporate” tone?
Add your style to the prompt (“warm tone, short sentences”) or give an example of one of your emails. Your final touches — including one personal sentence — do the rest.
Which rule is absolute before sending a Copilot-written email?