Draft Customer Support Replies with AI Safely: Setup and Review Rules

Posted on Oct 29 • Originally published at epifive.com

A support team can use AI to draft replies in a shared mailbox safely by keeping the AI at the drafting stage only: it proposes a reply from the customer's message and your approved information, and a person checks it and sends it. The setup that matters is not the prompt but the controls around it: correct mailbox permissions, a limit on the customer data you share, approved source material, and a written review checklist. This guide shows how to put those in place with Microsoft Copilot in Outlook or a general chat assistant.

It is for team leads and administrators of small support or sales-enquiry teams who use a Microsoft 365 shared mailbox. You will finish with a configured access model, a reusable prompt template, a review checklist, and a short pilot plan. Information on Microsoft products was checked on 28 October 2026; AI features change often, so confirm what your tenant offers.

Write down the boundary before you turn anything on. A workable policy for a small team has three levels:

Microsoft's own privacy documentation says Copilot output is not guaranteed to be factual and that users should use their judgement when reviewing it before sending it to others. Apply the same rule to any AI tool.

A shared mailbox is a good fit for support addresses, and Microsoft lists support email addresses as a typical use. Check these facts from the Microsoft 365 admin documentation before you add AI:

If the team is larger or needs a different model, see Shared Mailbox vs Microsoft 365 Group: Which to Use and When.

Review who has access. AI tools that work inside the mailbox use whatever the user can already see, so tidy permissions first. Remove people who left the team and make sure nobody has more access than their role needs.

Copilot in Outlook is licensed per user (a Microsoft 365 Copilot licence). A June 2026 report on Microsoft's update says Copilot in Outlook now works in shared and delegated mailboxes on Outlook on the web, new Outlook, Outlook for Mac and Outlook for iOS and Android, but not in classic Outlook. The same report says it processes mailbox content using the mailbox permissions assigned to the user, that each person's Copilot conversation history is private from colleagues, and that it appeared when the shared mailbox was added to the folder pane rather than opened through "Open another mailbox." The source is a third-party blog rather than a Microsoft page, and the folder-pane point is the author's own observation, so test all of this in your own tenant before you rely on it.

Microsoft's drafting support page, cited below, does not mention shared or delegated mailboxes.

Microsoft's support page describes the drafting steps. In new Outlook and Outlook on the web, select Home > New mail, select the Copilot icon and Draft, type a prompt, select Generate, then Keep it when you are satisfied. You can change tone and length from a dropdown, or retry the prompt. Selecting text in a message and then the Copilot button lets you modify that selection. On the web and new Outlook, drafting does not support plain text messages; switch to HTML under Settings > Mail > Compose.

Microsoft states that prompts, responses and data accessed through Microsoft Graph are not used to train foundation LLMs, that Copilot only surfaces organisational data the user has at least view permission to, and that it honours Microsoft Purview sensitivity label usage rights. For the readiness steps, see Microsoft 365 Copilot Readiness: Fix Oversharing Before Rollout.

If you do not use Copilot, a team can paste a customer message and approved facts into a chat assistant. That means customer data leaves Microsoft 365, so the rules matter more:

AI drafts are only as safe as the facts you give them. Create a short document of approved answers for the common questions: opening hours, how returns work, how to reset an account, what you can and cannot promise. Keep it in one place, such as a SharePoint page, and paste only the relevant part into the prompt, or reference it from a tool that can read it.

State what must never be promised. Examples: refunds, compensation, delivery dates, legal positions, medical or financial advice, and anything that needs a manager's approval. Put the escalation route in the document so the AI can recommend it in the draft.

Use a fixed template so the model returns a consistent, reviewable draft. Adapt this one:

You are drafting a reply for the Contoso Support team. A person will review it before sending. Rules: - Use only the facts in the APPROVED INFORMATION section.

If the answer is not there, say what is missing and suggest escalating to a colleague. - Do not promise refunds, compensation, delivery dates or policy exceptions. - Do not invent order numbers, names, links or prices. - Match the customer's language. Keep the reply under 150 words. Friendly, plain tone. - End with a one-line list "Check before sending:" naming any facts the reviewer must verify.

CUSTOMER MESSAGE: <paste the relevant message only> APPROVED INFORMATION: <paste the relevant approved answers> Enter fullscreen mode Exit fullscreen mode The "Check before sending" line makes the model flag what it relied on, which speeds up review. It is a prompt to the reviewer, not a guarantee, so the checklist below still applies.

A short checklist prevents the common failures. Print it or pin it in the team channel.

Also read the draft against the original message. Check that it answers what was asked rather than a similar question.

Keep the review rule even if drafts become reliable; the cost of one wrong promise to a customer is higher than the time saved by skipping a read.

This guide was researched and drafted with AI assistance and checked against the vendor documentation listed in its References. Read the maintained version and related guides on EpiFive.