Choose a realistic communication problem
Use a fictional customer asking when an order will arrive. The source confirms that dispatch is planned, but the carrier has not confirmed a delivery date. The employee needs to acknowledge the enquiry, explain what is known and state the next update. This simple situation tests whether a helpful-sounding response adds a promise the business cannot support.
Provide a brief that controls the message
Specify the audience, purpose, tone, permitted facts and desired next step. Include the source status and explicitly name what is unknown. Ask for a short draft without a new price, discount or delivery guarantee. In a workshop, keep sample recipients fictional and use a draft-only exercise so learners can evaluate messages without contacting real customers.
Use the participant’s Outlook environment
Confirm the Outlook version, account and Copilot access before the lab. Microsoft describes drafting and refinement across supported experiences, but the entry point and available controls can differ. Teach participants to recognize the draft, edit it and compare alternatives using their actual setup. Do not build the core lesson around preview-only actions that have not been approved for the cohort.
Review content and destination separately
First check the message against the source: current status, promised action and unknown date. Then review the destination, subject, names, attachments and any quoted thread content. Tone improvements should not soften a limitation into a commitment. The final human check is important even when the draft was generated from an existing conversation, because the source may be incomplete or the intended audience may have changed.
Build a repeatable team pattern
Save a brief template and a short review checklist, not a universal response that is reused without reading the situation. Ask a second participant to review an alternative draft containing a false confirmation. For workplace transfer, choose an approved low-risk message type and agree who reviews exceptions. Inbox automation, bulk actions and message sending require their own scope beyond this drafting exercise.
