How to Automate Outlook

Outlook carries the mail the company is governed by

Outlook is the mail and calendar client bundled with Microsoft 365, and in a company of any size it carries a heavier load than personal email ever does.

It is where the audit trail lives. Approvals arrive in it. Contracts are attached to it. When a dispute happens two years later, the thread in somebody's Outlook is the evidence.

It also runs on shared mailboxes, and that is where the volume sits. The accounts inbox, the support address, the bookings mailbox, the one the whole team can see. Those have service levels attached, formally or otherwise, and somebody notices when they slip.

All of it sits inside a governed estate with an IT department, a tenant and an approval queue for anything new, which shapes what is realistic more than any technical limit.

The mailbox is a queue with a clock on it

A shared mailbox is a queue where every item needs looking up before it can be closed.

A customer asks for a delivery date, which is in the industry system nobody outside operations has open. A supplier queries an invoice, and the answer is in the accounts package. Somebody asks whether their order shipped, and it is on a courier site behind a reference in an earlier email in the same thread.

The pattern repeats all day. Read, open two or three other systems, find one fact, type a short reply, close it.

When the queue backs up it is almost never because the answers are difficult. It is because each one costs four minutes of looking, and there are ninety of them.

The queue is also visible in a way most work is not. Everyone can see how many are unread, which means a backlog turns into a conversation about the team rather than about the four minutes of looking each message costs.

Outlook

Shared mailboxes that keep pace The queue triaged and the routine answers prepared before the team starts, so the service level survives Monday.

Facts from outside the tenant The portal, the industry package and the customer extranet Power Automate has no connector for, read and quoted.

Drafted, never sent Replies wait in the folder. Nothing leaves the company without somebody having read it.

Rules and Power Automate stay inside the tenant

Outlook has serious automation, and inside Microsoft it is better than most alternatives.

Rules move, flag, categorise and forward on conditions. Quick Steps bundle several actions behind one click. Automatic replies handle absence. Shared mailboxes and delegation let a team work one address properly. Power Automate connects Outlook to hundreds of products, so an email can create a task, file an attachment or start an approval.

The reach of all of it is the connector list. Where Microsoft or a vendor built a connector this is excellent, and you should use it before anything else.

The systems that hold the answers people email about are frequently not on that list. The industry package the business runs on. The regional supplier portal. The customer's own extranet. The internal tool built years ago by somebody who has left. Those never had a connector and never will.

The reply can carry a fact from outside Microsoft

Which emails can be answered without a person should depend on the question, not on who once built a connector. Anything with a login can be opened and read.

The delivery date question answered from the industry system, with the real date in the sentence. The invoice query answered with what the accounts package actually shows. The shipping question answered from the courier site, using the reference already sitting in the thread.

The triage is worth as much as the answers. A shared mailbox sorted before anyone arrives, with the items that need a specialist flagged, the routine ones already drafted, and anything ageing past its service level pushed to the top.

The rule that does not bend: drafted, not sent. This is company email, quoted back in disputes and read by regulators. A draft costs two seconds to approve and keeps a person accountable for every sentence that leaves the building.

Looking things up is the part to hand over

Judging what to say to a customer is the job. Opening four systems to find one date is not.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It reads the message, opens whatever holds the answer including the systems with no connector, and leaves a reply in the drafts folder with the real detail in it.

It runs on your schedule in your own private environment, nothing is installed into the tenant, and a workflow can be restricted to a named list of domains.

The workflows below are already built, and each one names the systems it opens.