Draft a Teams reply with Copilot that keeps the commitment accurate
The reply needs to sound clearer, but Thursday depends on the supplier replying first. Copilot can tidy the wording in seconds. Make sure it doesn’t tidy away the “if”.
What you'll make
a clearer Teams reply that keeps the deliverable, the person, the timing, the condition and the fallback you meant.
What you'll need
Teams on desktop or the web with Rewrite with Copilot under the compose box (availability depends on your organisation; ask your administrator if it’s missing), a message you’ve typed yourself, and about five minutes.
Example result.
Original: I can send the cost breakdown by 16:00 on Thursday 8 October
if the supplier confirms the missing rates by noon on Wednesday
7 October. If they do not, I'll update you by 14:00 on Wednesday with
a revised delivery estimate.
Concise rewrite: I can send the cost breakdown by 16:00 on Thursday
8 October, provided the supplier confirms the missing rates by noon on
Wednesday 7 October. Otherwise, I'll send a revised estimate by 14:00
on Wednesday.1. Write the complete commitment first
Type the whole commitment in the compose box: what you’ll deliver, by when, what it depends on, and what happens if that doesn’t happen. Rewrite works on the text you typed. It can’t put back a condition you never wrote, so read the thread yourself first and resolve anything you’re unsure about. If you don’t know whether Thursday was agreed, say you need to confirm it.
A private checklist helps:
Deliverable:
Person making the commitment:
Date and time (with time zone if needed):
Condition:
Fallback, or next update if the condition isn't met:Use it to check your own message, not as a form to post.
Why this works: clumsy and accurate is a good starting point. Polished and vague is not.
What you should see: a draft that answers all five lines, however awkward it reads.
2. Choose Rewrite or a careful Adjust
Select Rewrite with Copilot under the compose box. Rewrite offers another version with better grammar and style; use the arrows to compare versions. Adjust has two menus: Make it (concise or longer) and Make it sound (casual, professional, confident or enthusiastic).
Make it concise is usually the safer choice. Make it sound confident is the one to treat with suspicion: in writing, confidence is produced by removing hedges. “I should be able to” becomes “I will”, and “if the supplier confirms” becomes nothing at all.
Why this works: picking the option that fixes your real problem (length, usually) changes less of what you meant.
What you should see: one or two alternatives, with your original still available. Select X to keep the original.
3. Compare meaning before accepting
Read the original and the suggestion side by side and check four things:
- Scope: still the same deliverable, not something bigger?
- Timing: same date, time and time zone?
- Condition: is the dependency still there?
- Fallback: does the reader know what happens if it fails?
Watch “can”, “expect”, “will” and “subject to”. They carry real uncertainty, not disposable politeness.
Why this works: a better-reading message is the dangerous one, because it’s the one you’re most tempted to send without rereading.
What you should see: a version that passes all four, or a decision to keep the original and edit it yourself.
4. Replace, reread and send
Select Replace, then read the text now in the compose box, check the chat or channel, and select Send. Replace and Send are separate steps, so there’s always a moment to reread.
Why this works: the compose box is what gets sent, not the suggestion you remember.
What you should see: the right message, in the right place, with the same commitment as your original.
Check the result
- The deliverable is the one you meant, named the same way.
- The date and time are unchanged.
- The condition is still explicit (“if”, “provided”, “subject to”).
- There’s a fallback or an update time if the condition fails.
The usual failure: a rewrite that reads better and promises more. The condition disappears, “cost breakdown” becomes “final figures” and the update time vanishes. Spot it by finding the “if” in your original and looking for its equivalent in the suggestion. If it’s gone, reject the suggestion and fix the wording by hand. If you want an AI rewrite you can instruct precisely, use a separate work chat in Copilot, ChatGPT, Claude or Gemini, where you’re allowed to paste the message:
Rewrite this message for [recipient]. Keep its deliverable, owner,
date, time, condition and fallback unchanged. Keep real uncertainty.
Do not add agreement, reassurance or a stronger promise. Show the
revision and list any wording that could change the commitment.
MESSAGE: [your draft][recipient] is who it’s for; [your draft] is the message. Paste the result back and do the four checks again.
Worked example: a conditional Thursday deadline
Fictional example. The original is the one in the example result above. Make it sound confident produced:
“I’ll send the final figures by Thursday afternoon.”
It loses the condition, changes the deliverable from a cost breakdown to “final figures”, drops the fallback and blurs 16:00 into “afternoon”. The writer selected X, then tried Make it concise, which gave the version in the example result: shorter, with the trigger, the deadline and the update time all still there.
What mattered:
- The confident version read best. That’s why it needed the closest check.
- The deliverable changed name. “Final figures” sounds like a bigger promise than a cost breakdown, and the recipient will hold you to the bigger one.
- Concise kept the structure. Shortening rarely removes a condition; changing tone often does.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Correct a sent message visibly
To rewrite a message you’ve already sent, hover over it, select Edit, then Rewrite with Copilot from the compose box’s menu bar, and Done to save. But if people may have acted on a wrong deadline, say what changed (“Correction: Thursday depends on the supplier’s rates”). Editing the old wording silently can leave people working from the version they already read. On mobile, use Actions and apps next to Type a message, then Copilot.
Draft an Outlook reply with the same checks
In new Outlook or Outlook on the web, open a new message, select the Copilot icon, choose Draft, type a prompt and select the Generate arrow; Keep it inserts the draft. Some views offer Help me reply, which opens Chat. Supply your confirmed answer rather than asking it what you can promise:
Draft a reply to this enquiry: [enquiry text].
My confirmed answer: [facts and any conditions].
Use a clear, courteous tone. Do not promise a date unless I gave one.
Keep missing information explicit.[enquiry text] is the message you’re replying to; [facts and any conditions] is what you can actually confirm.
If a supplier asks “Can you confirm Friday delivery?” and all you know is that dispatch is checking, “Friday delivery is not confirmed yet; dispatch is checking availability” is right, and “We will deliver Friday” is a promise you didn’t make. Do the four checks before sending.
Messages to write yourself
Don’t use rewrite tools on messages about someone’s performance, conduct, health, pay or employment. The tone matters too much, and a smoothed sentence can say something you didn’t intend about a person. Write those yourself and, where it matters, ask a colleague or HR to read them.