Power Platform Cloud Solutions Architect @ Microsoft | Microsoft BizApps MVP 2023 | Power Platform | SharePoint | Teams
Copilot Cowork can prepare customer email replies from inbox enquiries and relevant business files, then save them as drafts for review rather than sending them automatically. The workflow is aimed at Microsoft 365 users who handle customer correspondence and want help with the research and preparation behind a reply. Damien Bird demonstrates the process using a fictional distillery, sample customer emails and example business files.
Copilot Cowork takes a task expressed in plain English and works through the requested steps. In this example, the task is not simply to write one email: Cowork is asked to find unread trade enquiries in a shared inbox, respond with details and pricing for a new whisky, attach a launch presentation and save the messages as drafts.
The distinction matters for customer-facing work. A generated paragraph still leaves the user to locate the right enquiry, check supporting information, prepare the attachment and create the draft. The demonstrated Cowork task brings those actions together, while leaving the final decision to a person.
For its replies, Cowork uses the price list and distributor policy in the example. It follows a 120-bottle limit and does not mistake an unrelated email about a Highland cow soft toy for a trade order. The drafts appear alongside the customer emails they answer and the files used to support their figures, giving the reviewer context for checking the response.
The described requirement is Microsoft 365 Copilot with Cowork. The task uses Copilot Credits. It is relevant to people who manage a shared customer inbox and have business information, such as pricing and policies, available for Cowork to use.
The scenario is a practical example rather than a real customer-service deployment: Glen Damo, its staff and customers are fictional, and the emails and files are sample data. Treat the workflow as a way to understand draft preparation and review, not as evidence that a particular organization has adopted it or that every customer scenario will work the same way.
The example also makes clear that a request needs to specify the intended work and relevant boundaries. Here, those include which enquiries to handle, what information to include, which file to attach and the customer limit. The user still needs to check whether the selected messages and source documents are appropriate for the task.
The demonstrated approach is to delegate the whole bounded job, then inspect the approval cards and drafts rather than relying on a brief chat summary. The request identifies the target messages and the work Cowork should perform.
In the example, Cowork asks before each draft and each attachment. That makes approval part of the workflow, rather than treating a completed task as permission to send customer messages. The publisher’s tips are to read the approval card, retain the “Sent by Copilot Cowork” line, and use /cost to inspect the task’s credit use.
The described run used 71 credits, which the publisher equates to about 71 cents. That figure belongs to this particular demonstration; it is not a general estimate for other tasks. Checking the cost command after a task can help users understand the credit use of their own run.
The workflow stops at drafts for human review. That is a useful boundary for messages involving prices, order limits or customer-specific details: the user can catch an incorrect figure, unsuitable attachment or mismatched enquiry before anything is sent. The approval prompt is not a substitute for checking the underlying email and business files.
The example depends on the quality and relevance of the information Cowork can consult. Reviewers should verify that the price list and policy actually apply to the customer, that the draft reflects the correct limit, and that the attachment belongs with the reply. They should also make sure unrelated inbox messages remain outside the task, as the example’s soft-toy email does.
For a small number of messages, a person can continue to read each enquiry and compose a reply manually. Cowork’s demonstrated value is combining inbox triage, reference checking, drafting and attachment preparation into one delegated job. The human review step remains central: the question is not whether to approve every generated message automatically, but whether each draft is accurate and appropriate to send.
The described setup requires Microsoft 365 Copilot with Cowork and uses Copilot Credits.
No. In the demonstrated workflow, Cowork saves replies as drafts and asks before each draft and attachment. A person reviews the messages before sending.
The example asks Cowork to attach a launch deck to the prepared customer replies. It requests approval before each attachment.
The publisher recommends typing /cost. The demonstrated task used 71 credits, about 71 cents.