How to Use Copilot in Outlook for Email and Follow-Up

To use Copilot in Outlook, open a new email or reply, choose the Copilot drafting option, describe the message, and review the result before sending. For an existing conversation, use its summary option to get oriented, then check the messages behind any important claim.

Email often produces work that outlives the thread: a promised review, an approved change, or a communication rule. Tools like fenbs keep those agreed decisions and next steps outside the inbox, available to supported assistants you connect separately.

How do you draft your first email with Copilot?

1. Open Outlook using the account that has Copilot access, then start a new message or a reply. Check that you are composing from the intended mailbox.
2. Choose the Copilot icon and the drafting option available in your Outlook version. Give it the recipient, purpose, confirmed facts, preferred tone, and desired next action.
3. Generate the draft. Ask for a targeted change if needed, such as a shorter opening or a clearer question, then keep or insert the version you want.
4. Edit the email yourself, verify the recipients and attachments, and send only when its wording and commitments are correct.

Microsoft documents different controls for new Outlook, classic Outlook, Mac, and mobile in its email drafting guide↗ (opens in a new tab). Treat the steps above as the workflow, and use the guide for the exact controls in your app.

Start with a low-stakes message you understand well. A request to confirm a review date is easier to judge than an unfamiliar contract response. You should be able to explain why every factual sentence belongs in the finished email.

What should an email prompt include?

Give Copilot the substance before asking for style. A friendly tone cannot compensate for an invented delivery date. Separate what you know from what you need the recipient to confirm, and explicitly forbid new promises when the schedule is unresolved.

Draft a brief reply to a client about the website review.
Confirmed: the revised homepage is ready for review.
Unknown: whether the client can review it by Thursday.
Ask them to confirm a review date.
Use a warm, direct tone. Do not promise a launch date or imply approval.

If the first attempt sounds vague, change one requirement at a time. Ask for the question in the first paragraph, for example, instead of repeatedly requesting a better email. Preserve details that matter, including who owes the next response and whether a date is proposed or agreed.

For reusable instruction patterns, see Copilot instructions examples. Record team-approved communication rules in Decisions and rules so another connected assistant can read the same instructions before helping with related work.

How do you summarize a long Outlook thread?

Open the conversation and choose Summary by Copilot or Summarize, depending on your Outlook version. Microsoft says a summary may include numbered references that take you back to the corresponding email; its thread-summary instructions↗ (opens in a new tab) show the supported controls.

Use the summary to locate the relevant messages. Read the latest reply and any message that contains a commitment, changed requirement, or approval. A summary saying that the team discussed Friday is not evidence that someone agreed to deliver on Friday.

• Check chronology: did a later reply replace an earlier proposal?
• Check authority: did the person making the choice have responsibility for it?
• Check ownership: was a task actually accepted, or was someone only suggested?
• Check missing material: does the answer depend on a separate attachment or conversation?

In a hypothetical client thread, the summary might group two design options together. Your next action may depend on the short reply choosing one of them. Find that reply before writing a confirmation that closes off the other option.

What should you check before pressing Send?

Review the draft in three passes: facts, commitments, and delivery. Check names, dates, quantities, and links against the source. Then look for language such as approved, guaranteed, or will deliver that changes the strength of what anyone actually agreed.

Read the message from the recipient’s perspective. Could they reasonably treat it as permission to start work? Could a polite summary sound like acceptance of a change you still need to review? Rewrite that sentence directly rather than hoping the recipient understands the intended qualification.

Finally check To, Cc, the subject, attachments, and quoted content. Remove internal discussion that does not belong with an external recipient. Keep any sensitive material within your organization’s approved handling process rather than moving it into another tool for convenience.

If the drafting controls are missing or fail, use the focused Copilot in Outlook troubleshooting guide. The broader Copilot versus ChatGPT comparison explains the choice of assistant; neither question changes the need to review an email before it leaves your mailbox.

How do you keep email follow-ups from disappearing?

After sending a meaningful confirmation, capture the resulting work in a short record. Include what was agreed, the source message or its location, the person responsible, and the next check. Keep a proposed change open until the relevant person confirms it.

For example, save “Client approved homepage option B; internal accessibility review still pending.” That statement keeps the approval distinct from the unfinished review. Copying the entire thread would make the next person reconstruct this distinction again.

Before stopping, say what was sent and what reply or review is still needed. fenbs keeps that next starting point in Where we left off; the AI handoff workflow explains how a supported connected assistant can continue from it.

How to do this with fenbs

1. Create a free account and add the project whose email follow-ups you want to keep.
2. Record the communication rules people have approved, such as asking before promising a new delivery date. Use Decisions and rules for the agreement, with the person who made it.
3. After reviewing the email, add tasks for the confirmed follow-ups and describe who needs to act. Include only the context that the project’s members should see.
4. Use a supported assistant connection, such as those in the integration guides, to read the project context and save progress before the next session.

fenbs does not connect to Outlook or automatically import email threads. If all you need is help drafting a single reply, Outlook is enough; fenbs becomes useful when the resulting decisions and work need to survive the conversation.

Try it with one real follow-up rather than your whole inbox. Save the agreed action, then check that you can find the next step without reopening every message. Browse the AI at work hub for other focused workflows.