To automate sending emails in Outlook, use Schedule send for a one-off email at a later time, a rule to reply automatically or delay delivery, and a Power Automate scheduled flow for emails that repeat. Quick Steps save clicks but do not run on their own. Outlook has no built-in recurring email scheduler, so repeating emails need Power Automate.
This article follows Microsoft’s own pages as read in November 2026. Menus differ between classic Outlook, new Outlook and Outlook on the web, so check which one you use before following the steps.
Which Outlook tool does which job
| Tool | What it does | Runs on its own? |
|---|---|---|
| Schedule send | Sends one message at a time you choose | Yes, once |
| Rules | Act on incoming mail, such as moving it, or send an automatic reply | Yes, when mail arrives |
| Quick Steps | Bundle several actions into one click | No, you click |
| Power Automate flow | Sends emails on a schedule or after a trigger | Yes |
How to automate sending emails in Outlook with Schedule send
Microsoft says that in the new Outlook, Outlook on the web and Outlook.com you open the dropdown next to Send, choose Schedule send, pick a default time or set your own, and select Send. The message waits in Drafts until then. To change your mind, open the draft, select Cancel send, then Send. Microsoft states the feature is not available for IMAP or POP accounts (Microsoft: delay or schedule sending).
In classic Outlook for Windows the equivalent is Do not deliver before, under Message Options. The message waits in the Outbox, and Microsoft says Outlook needs to be online and connected for it to go. If Outlook is not connected at the scheduled time, the email does not leave. For anything important, use the new Outlook route or a Power Automate flow, which runs in the cloud.
Classic Outlook can also delay all outgoing mail with a rule, by up to 120 minutes. That is useful as a safety net: a two-minute delay gives you a short window to catch a mistake.
Using rules to reply or hold email automatically
Rules act on incoming mail. Microsoft’s rules page says they can move or delete messages, change importance and flag messages for follow-up, and that you can set conditions, actions and exceptions. In new Outlook you find them under Settings, Mail, Rules. There are limits: new Outlook does not support rules for third-party accounts such as Gmail, Yahoo or iCloud, and Outlook.com rules apply only to mail received after you create them (Microsoft: manage email by using rules).
For an automatic reply on classic Outlook, Microsoft’s page describes writing the reply as a template, saving it as an .oft file and creating a rule that replies to incoming messages with it. If your account offers the built-in Automatic Replies button, use that instead. Rule-based replies only work while Outlook is running, so keep it open while you are away (Microsoft: use rules to create an out of office message).
Quick Steps: fewer clicks, not automation
Microsoft describes Quick Steps as bundles of actions you trigger yourself, from the ribbon or a keyboard shortcut. Examples include moving a message to a folder or forwarding to your manager. In new Outlook, go to Home, open the dropdown beside Quick steps, choose Manage quick steps, add a new one, name it and choose its actions. Microsoft says a Quick Step cannot be undone with Ctrl+Z, so avoid putting delete actions in one (Microsoft: Quick Steps).
A practical example: a Quick Step that replies with your standard “thanks, we have received your documents” text and moves the original to a Done folder. It saves clicks on every request, but a person still presses it.
Sending recurring emails with Power Automate
For emails that repeat, such as a Monday reminder to the team or a monthly note to customers, Microsoft’s route is a scheduled cloud flow in Power Automate. You create a flow with a Recurrence trigger, set the interval and frequency (Microsoft’s example for weekly is Interval 1 and Frequency Week), choose the days and times, then add the Microsoft 365 Outlook action Send an email (V2) with the recipient, subject and body. Test it before relying on it (Microsoft: run a cloud flow on a schedule, Microsoft: get started with cloud flows).
Two checks first. Power Automate and its Outlook connection depend on your Microsoft account type and what your organisation allows, so ask your administrator if the action is missing. And Microsoft’s own tutorial reminds readers to have a person check AI-generated content if Copilot builds the flow for you.
Here is a worked example with made-up numbers. A bookkeeper sends the same month-end reminder to 40 clients, which takes about 30 minutes each month. A scheduled flow sends it on the 25th, and the bookkeeper adds one line if something changes. That is six hours a year handed back, and it only works if the client list stays current.
Which business emails to automate first
Do not automate everything. Pick the emails where a delay or a forgotten send costs you, and the wording rarely changes.
- Acknowledgement of a request. A rule or Quick Step with a standard reply that says when the customer will hear from you.
- Month-end or deadline reminders. A scheduled flow that goes out on a fixed date to a fixed list.
- Out-of-office cover. Use the built-in Automatic Replies if your account has it, so enquiries during a holiday get a clear answer and a second contact.
- Emails written now to arrive tomorrow. Schedule send, so a message written at 9pm lands at 8am and does not look like you work all night.
- Internal routing. A rule that moves invoices, supplier mail or support requests into folders, so the right person sees them first.
Mistakes that catch people out
- Testing on a copy of the real list. Send the first run of any flow to yourself.
- Forgetting the exceptions. A reply rule with no exceptions replies to newsletters and system emails. Microsoft’s rules page lets you add exceptions, so use them.
- Using a personal mailbox for shared work. Name an owner for every flow and rule, so someone is responsible for checking it.
- Assuming it kept running. Microsoft’s tutorial shows a 28-day run history for each flow. Check it once a month and look for failed runs.
When the job belongs in the CRM or a custom set-up
Outlook is a mail client. It does not know whether a customer has paid, booked or replied. When an email depends on that, a CRM or a connected automation does the job better: a follow-up that stops when the customer replies, a reminder that reads the booking date, an email that goes out when an invoice is overdue. CentriWeb builds these, usually in n8n, and looks after them under its run with less admin service. We build custom work, so weigh our view with that in mind.
It does not suit a business that sends a couple of repeat emails a month. A scheduled flow or a saved template is enough. Related guides: quote follow-up emails, how to automate tasks with AI and HubSpot workflows. For wider set-up, see our automation page.