A customer’s email conversation contains an early delivery estimate, a revised requirement and a final question about timing. A hurried reply can repeat the estimate while missing the change that made it unreliable. Copilot can help you read and draft, but someone still needs to decide what the business is authorised to promise.
This small pilot is designed for Malaysian SME account managers and IT decision-makers using Outlook. It takes one customer thread through summary, source checking and a reviewed reply. It does not automate sending or replace an approval process.
Check the account and the experience first
Use an approved work account and a supported Outlook client. For a predictable initial pilot, ask your administrator to confirm the user has a qualifying base subscription, an assigned commercial Microsoft Copilot licence for the licensed features being tested, and an Exchange Online mailbox. Microsoft’s requirements documentation distinguishes licensed Copilot capabilities from Copilot Chat and explains that availability depends on the app, licence and tenant configuration.
Do not infer entitlement from a visible Copilot icon. Microsoft also documents limited Outlook Copilot Chat capabilities without an add-on licence for eligible work or school accounts. Have IT verify the exact summary and drafting controls in your environment before purchasing licences or promising identical behaviour to everyone.
Start in your own authorised mailbox with a non-sensitive test conversation. Ordinary summarising and drafting does not require making the user a tenant administrator. Keep existing access boundaries: do not forward confidential customer mail into another account simply to obtain an AI feature.
1. Summarise the selected conversation
In Outlook on the web or new Outlook, select the conversation and choose Summary by Copilot or Summarize at the top of the thread. Microsoft’s summary guide says the result may include numbered citations that take you to the corresponding messages.
Read the result as a navigation aid. Open the cited messages and the latest customer email. Check who made each statement and whether it was a request, an estimate, a rejected option or an approved decision. Do not assume the summary covers a separate conversation, a phone call or a document you have not checked.
Hypothetical example: a services company is arranging an office network upgrade. An earlier message proposes Friday evening, but the customer later adds another floor and asks whether Friday is still feasible. The correct next step is to confirm the revised scope with delivery, rather than repeat Friday as a commitment.
2. Write a short verified brief
Before generating a reply, make a working note with three headings: confirmed facts, open questions and proposed next action. In the hypothetical upgrade, the additional floor is a customer request; the installation date is unresolved; the next action belongs to the delivery lead.
Record the source message and date beside any important fact. If the conversation contradicts a signed scope or current quotation, resolve that with the responsible person. Copilot cannot grant approval on their behalf. Keep internal commentary out of material that could accidentally enter a customer-facing draft.
3. Generate a bounded reply
Open a reply to the intended customer message. Microsoft’s drafting instructions describe entry points such as Help me reply and Copilot drafting controls; labels vary by client and rollout. In new Outlook and the web, the documented drafting experience does not support plain-text composition, so check the HTML setting under Mail → Compose and reply if necessary.
After supplying your verified brief, try this original prompt:
Draft a concise, professional reply using the verified facts below. Acknowledge the customer’s revised requirement. Explain that the delivery date needs confirmation from our delivery lead. Do not invent a deadline, price, technical finding or approval. Keep internal working notes out of the reply. Where essential information is missing, ask a clear question instead of making an assumption.
Replace the example facts with approved information from your own conversation. Prompt boundaries help express your intent; they do not guarantee the result follows it.
4. Review the message that will actually leave
Inspect the generated draft directly. Check scope, dates, quantities and any wording that creates an obligation. “We will confirm availability” must not become “we confirm the installation.” Edit or discard the result when it changes the meaning.
Check To, Cc, attachments, quoted history and the sending account separately. A factually correct paragraph can still go to the wrong audience. Keep unresolved placeholders in your working notes, resolve them before release and obtain any required commercial or delivery approval. Send only after a human has checked the final message.
For a useful pilot review, record whether the summary missed a decision and whether the draft added an unsupported commitment. Those observations give your team something concrete to improve. To discuss a practical AI workflow for customer communication, contact AXO Technologies.
Sources and dates
Published 3 November 2026. Microsoft documentation accessed on 3 November 2026; these are access dates, not claims that the pages were published today. The example and pilot prompt are original and hypothetical. Feature availability and interface labels can change.
- Microsoft Copilot requirements — licensing, identity, mailbox and app prerequisites.
- How Copilot Chat works in Microsoft 365 apps — differences with and without an add-on.
- Summarise an email thread in Outlook — summary controls and citations.
- Draft an email message in Outlook — drafting, review and HTML composition.