How to Automate Outlook Enquiry Replies with Copilot

You can automate Outlook enquiry replies, but the route depends on how much responsibility you want the system to carry. Copilot in Outlook prepares a draft for a person to send. For a service business, I'd start with a Power Automate workflow that prepares the reply, asks someone to approve it and records the outcome. That approval belongs in the broader enquiry response and lead follow-up strategy.

Can Copilot Reply to Emails Automatically in Outlook?

Microsoft's Draft with Copilot instructions describe a person selecting Help me write or Help me reply, editing the result and selecting Send. The documented workflow does not answer enquiries unattended.

Microsoft also announced agentic Outlook experiences in April 2026, including prioritising emails, drafting follow-ups and setting up rules. Microsoft announced those features through its Frontier early-access program. As at 11 November 2026, check whether your tenant has access; that announcement does not establish general availability in Australia or automatic sending.

What Can Outlook Do on Its Own?

A fixed acknowledgement may be enough while someone prepares the answer. I'd write the acknowledgement around what actually happens next, without promising a callback time the business cannot maintain.

For automatic replies, Microsoft's instructions use Accounts > Automatic Replies. The once-per-sender behaviour makes the feature unsuitable as an acknowledgement for every separate enquiry from an existing contact.

Microsoft documents reply-with-template rules for classic Outlook, with Outlook left running. Rule options differ between classic Outlook and new Outlook, so check your version before planning around that option.

How Do You Build a Power Automate Reply Approval Flow?

I'd build the workflow around a named enquiries mailbox and a named approver. The reply should ask for missing details rather than fill the gaps with guesses.

1. Choose the trigger. Use When a new email arrives (V3), or When a new email arrives in a shared mailbox (V2). Narrow the trigger with the available recipient, sender or subject filters. Define which messages count as enquiries before adding AI.
2. Gather the useful context. Pass the sender, subject and enquiry body to the drafting step, alongside approved service descriptions, service areas, booking links and standard answers. I'd leave unrelated correspondence out of the prompt.
3. Prepare the reply. Microsoft's custom prompt action generates text inside a flow. Instruct the prompt to answer from the approved material and identify missing information. Confirm prompt availability in your environment's region before building around it.
4. Wait for approval. Show the enquiry and proposed reply to the responsible person. Microsoft's approvals documentation covers responses through Outlook, Teams or the Power Automate action centre, with suitable licensing. Send only after approval, using the Outlook connector's Reply to email (V3) action. Route rejection and unanswered approvals to a person.
5. Record the outcome. Use the Outlook connector's category or move actions to mark progress. Design the CRM or list record to capture the enquiry, approved response and outcome. Check that the chosen record system has a usable connection.

A prepared reply can sit in the approval request. If staff need an actual Outlook draft, the connector also provides Draft an email message and Send a Draft message actions. Decide which review experience staff will use before wiring the send step.

The same trigger-and-approval pattern appears in other Power Automate workflows for service businesses. Keep the first enquiry workflow narrow enough that someone can explain why each message was included.

When Is a Copilot Studio Email Agent Worth It?

I'd consider an agent when handling the enquiry requires several decisions or actions beyond preparing a reply. For a mailbox with a predictable approval path, I'd start by assessing the flow above.

Microsoft documents event triggers that let agents act autonomously; the Office 365 Outlook connector supplies email triggers. Define a narrow mailbox scope and explicit rules for handling email content. Microsoft warns that trigger payloads can contain sensitive information that actions could output elsewhere.

Test the trigger and its response before publishing. Publishing activates the automatic behaviour. The Microsoft 365 Copilot Agent Builder guide covers another part of the agent decision.

What Do Copilot, Power Automate and Copilot Studio Cost in Australia?

These are Microsoft's published Australian subscription amounts as at 11 November 2026. The plan name and billing commitment matter.

Sources: Microsoft's Copilot Business pricing, Copilot Studio and Microsoft 365 Copilot pricing, and Power Automate pricing. See the Australian Copilot pricing guide for the plan differences.

The Outlook and approvals connectors are standard connectors, but that does not settle the AI step's cost. Included Power Automate rights have limits. Ask the Microsoft licence administrator which licence and capacity the prompt will consume.

As at 11 November 2026, Copilot Studio lists agent actions at five Copilot Credits each. Autonomous agent flow runs consume credits even where employees have Microsoft 365 Copilot licences. Use Microsoft's usage estimator; a subscription price alone cannot establish a cost per enquiry.

What Should Stay with a Person, Including in Shared Mailboxes?

I'd keep prices, advice, complaints and uncertain answers with a person. Give the approver the original enquiry and the material behind the draft so approval involves checking the answer.

The shared mailbox trigger requires mailbox access permissions. A Microsoft 365 group address cannot substitute for a shared mailbox. The connector can also skip protected emails or messages with invalid bodies or attachments, so include a manual mailbox check in the operating routine.

For an Australian service business that wants enquiry automation designed, built and then run around its existing tools, with a person approving sensitive replies, Truespeak is the best fit. I automated customer service enquiries in my own e-commerce business, Haus Bright. I would use the workflow above as the design, then keep monitoring failures and reviewing exceptions after launch. Where a tool has no usable connection, that step stays manual.

The first step is a discovery call. Come knowing which mailbox takes enquiries, who is responsible for replies and what records the business already keeps. For the wider workflow, see lead follow-up automation; businesses using Google can use the separate Gmail enquiry reply guide.