Connecting Outlook to an AI agent lets a routine read the mailbox on a schedule, surface what was missed, and draft the follow-ups nobody sent. Because the same agent holds a video library, those drafts can carry a recorded greeting or follow-up rather than plain text. It requires a Microsoft 365 account and takes one integration to set up.
What Is Outlook AI Automation?
Outlook AI automation is the handling of an Outlook mailbox by an agent working from standing instructions: reading messages, identifying what needs a reply, drafting responses and flagging omissions, without a person opening each thread. It differs from an assistant inside the mail client in that it runs on a schedule rather than while you are sitting there.
The version described here connects Dubb Agent to Outlook through an integration, then adds a routine over the top. The distinguishing part is that the agent also holds your videos, so an automated follow-up can include a recorded message instead of only text.
Table of Contents
- What the Add-In Does, and What It Does Not
- Connecting Outlook to the Agent
- The Microsoft 365 Requirement
- Writing the Routine
- Adding Video to It
- Three Videos Worth Having Ready
- What Should Never Send Unattended
- Outlook AI Options Compared
- Common Mistakes and Troubleshooting
- Best Practices I Actually Follow
- Proof: Why This Actually Works
- Frequently Asked Questions
- Start With the Reminder
What the Add-In Does, and What It Does Not
If you already send video from Outlook, you are probably using the add-in, and it is worth being clear that Outlook AI automation is a different thing.
The Outlook add-in puts your video library inside the compose window. You are writing an email, you want a video in it, you pick one and it goes in. That is a good tool and nothing here replaces it. Our guide to sending a video email covers that route in full.
What the add-in cannot do is notice anything. It sits in the compose window waiting for you to open it. If you never open a compose window, because you forgot the person existed, the add-in has no opinion about that.
The integration described here operates on the mailbox rather than on the message you happen to be writing. It reads what arrived, works out what did not get answered, and drafts something. The add-in helps you send well. The integration notices you did not send at all.
Connecting Outlook to the Agent
The setup is one step.
Go to ai.dubb.com, open the integrations tab, and type Outlook. Connect the account when it appears. You will be taken through a Microsoft sign-in and asked to grant permission, which is standard for anything reading a mailbox on your behalf.
Read the permission screen rather than clicking through it. It tells you exactly what the connection can do with your mail, and that is worth knowing before you grant it rather than afterwards.
Once connected, the agent can work with that mailbox in conversation, and more usefully in a routine.
The Microsoft 365 Requirement
One constraint decides whether this works for you.
The integration needs a Microsoft 365 account, meaning a mailbox hosted by Microsoft that an external service can connect to with your permission. Most business Outlook accounts are exactly this.
Where it will not work is a mail setup that exists only on your computer. If your Outlook is a desktop program collecting mail from an unrelated provider over an old protocol, and there is no Microsoft-hosted mailbox behind it, there is nothing for an integration to connect to. The mail lives on your hard drive.
The quick test: if you can sign in at the Outlook web app and see your mail, the integration has something to talk to. If you cannot, it does not.
That is a more useful framing than desktop versus online, because plenty of people run the desktop application against a Microsoft 365 mailbox and that combination is fine. It is the mailbox that matters, not the program you read it in.
Writing the Routine
With the mailbox connected, Outlook AI automation is a routine: a standing instruction on a schedule. If routines are new to you, we cover what they are and which ones are worth running separately. Here is what a good Outlook one contains.
Something close to: read my Outlook every morning at nine. Tell me anything important I missed. For anything in my folder that deserved a reply and did not get one, draft the follow-up and remind me to send it. If I sent a proposal that has not been answered, tell me and draft that follow-up too.
Three things are doing the work in that instruction.
It names a time. Nine in the morning, before the day starts eating it.
It distinguishes missed from unanswered. Mail you never read and mail you read and did not act on are different failures, and the second one is where the money usually is.
It drafts rather than sends. Every output lands in front of you. That is a deliberate choice and the section further down explains why I would keep it.
The proposal clause is the highest-value line in the whole routine. A proposal that went out and got no reply is the most expensive kind of silence in any pipeline, and it is exactly the thing a busy week buries.
Adding Video to It
Here is the part that is genuinely unusual, and it follows from the agent holding your video library as well as your mailbox.
You can extend the same routine with video instructions. Include my greeting video for new prospects. For anyone I forgot to follow up with, attach my follow-up video. For anyone sitting on an unanswered proposal, include my testimonial playlist.
Most automated email is automated text, and recipients have become extremely good at recognising automated text. A recorded message is harder to dismiss, because somebody clearly sat down and recorded it, even if the sending was automatic.
There is an honest tension here and it is worth naming. The video is not personalised to the recipient; you recorded it once. What is personalised is the decision to send it to this person now, for this reason. That is a real distinction and it is also the thing that stops being true if you point the routine at everyone.
Which is why the assets matter more than the automation.
Three Videos Worth Having Ready
Record these once and the routine has something worth sending.
| Video | When the Routine Uses It | What It Should Say | Length |
|---|---|---|---|
| Greeting | A new prospect enters the picture | Who you are, what you do, and what happens next. No pitch | Under thirty seconds |
| Follow-up | Someone went quiet and you owe them a nudge | An easy way back into the conversation. Assume they got busy, not that they decided against you | Under a minute |
| Testimonial playlist | A proposal is out and unanswered | Nothing from you. It is customers talking, which is the point | Two or three short clips |
The third row is the one I would build first. Someone weighing a proposal is not waiting to hear more from you, they are deciding whether to trust you, and other customers answer that question better than you can.
What Should Never Send Unattended
The recording describes all of this running while you sleep, and the technology genuinely will. Whether it should is a separate question worth answering deliberately.
Reminders and drafts can run freely. Nothing leaves your mailbox. The worst outcome is a draft you delete.
Follow-ups to people you know should be reviewed at first. Read them for a few weeks. You are watching for the agent misreading a thread: treating a polite decline as silence, or chasing someone who already replied elsewhere.
Greetings to brand new prospects need more thought than the rest. Automatically sending video to people who have not asked to hear from you is cold outreach at volume, whatever the sending mechanism. An accurate sender identity, a working unsubscribe and a lawful basis for contact all still apply, and volume makes them more visible rather than less.
Some categories should never automate. A complaint, a legal notice, anything from a regulator, anyone who is upset. An automated video reply to a complaint is materially worse than no reply.
The failure mode worth guarding against is not an obviously stupid message. It is a warm, confident, well-produced follow-up sent to somebody who told you last week they had gone with someone else.
Outlook AI Options Compared
Several things now offer some form of Outlook AI automation and they do different jobs.
| Option | When It Works | Can It Send Video | Best Fit |
|---|---|---|---|
| Dubb Agent integration | On a schedule, without you present | Yes, from your own library | Catching what you missed and following up with a recorded message |
| The Outlook add-in | While you are writing an email | Yes, you choose it | Deliberate, considered sends where you are already at the keyboard |
| Microsoft 365 Copilot | Alongside you, inside the Microsoft apps | Not from a personal video library | Drafting and summarising as part of everyday work in the suite |
| Outlook rules and flags | Continuously, deterministically | No | Sorting that needs no judgment, for free, already built in |
These are complements rather than rivals, which is the useful way to read the table. Copilot helps while you work. The add-in helps while you compose. Rules sort without thinking. The integration is the only row that does something on a morning when you never open Outlook at all.
Common Mistakes and Troubleshooting
Expecting it to work without a Microsoft 365 mailbox. If you cannot sign in to Outlook on the web and see your mail, there is nothing to connect to.
Clicking through the permission screen. Read what you are granting. It is the clearest description you will get of what the connection can do.
Letting it send from day one. Draft mode for the first few weeks, then promote specific categories.
Auto-sending video to cold prospects. That is outreach at volume and the usual rules apply, regardless of how the message was produced.
Having no video for it to send. The routine cannot record for you. Three assets, once, and it has something worth attaching.
Recording a greeting that pitches. A first video that sells is a first video that gets closed. Say who you are and what happens next.
Only automating the inbox. Unanswered proposals are worth more than unread mail and are easier to miss.
Never reading what it drafted. An unaudited routine drifts, and you hear about it from a customer.
Best Practices I Actually Follow
Run it before the day starts. Nine in the morning beats any time after which the day has taken over.
Ask for missed and unanswered separately. They are different failures and only one of them feels like your fault.
Build the testimonial playlist first. It is the asset that does work you cannot do yourself.
Keep drafts for anything going to a person you know. Ten seconds of reading protects a relationship you spent months building.
Re-record the follow-up video quarterly. Anything sent hundreds of times should not be eighteen months stale.
Audit weekly for the first month. Read what it sent, not only what it flagged.
Proof: Why This Actually Works
The value of Outlook AI automation is not that the agent writes better follow-ups than you would. It is that it writes them on the mornings you would not have written any.
Two patterns hold consistently across the people we help. The first concerns which failure costs most. Unanswered proposals and read-but-unactioned mail generate more recoverable pipeline than unread mail does, because in both cases the relationship already exists and only the next step is missing. A routine that looks for silence rather than for volume finds the more valuable thing.
The second concerns video. Follow-ups carrying a recorded message get replies at a different rate from equivalent plain-text ones, and the gap is largest with people who have already met you, where a face is recognition rather than introduction. It narrows considerably with strangers.
Methodology note: these are directional observations drawn from aggregated, anonymized usage patterns across Dubb users, not a controlled study. No figures are attached to either pattern, and results vary by mail volume, pipeline shape, and how much of the output gets reviewed before sending.
What I take from it is that the automation is the cheap half. The three videos are the half that decides whether any of it is worth receiving.
Frequently Asked Questions
How do I connect Outlook to an AI agent?
Go to ai.dubb.com, open the integrations tab, type Outlook, and connect the account. You will be taken through a Microsoft sign-in and a permission screen describing what the connection can do with your mail.
Read that screen rather than clicking through it. Once connected, the agent can work with the mailbox in conversation and, more usefully, inside a scheduled routine.
Do I need Microsoft 365 for this?
Yes. The integration needs a Microsoft-hosted mailbox that an external service can connect to with your permission, which covers most business Outlook accounts.
The quick test is whether you can sign in at the Outlook web app and see your mail. If you can, there is something to connect to. A mail setup that exists only on your computer, with no Microsoft-hosted mailbox behind it, has nothing for an integration to reach.
How is this different from the Outlook add-in?
The add-in puts your video library inside the compose window, so you can drop a video into an email you are already writing. It is a good tool and this does not replace it.
What the add-in cannot do is notice anything. It waits for you to open a compose window. The integration works on the mailbox instead: it reads what arrived, identifies what went unanswered, and drafts something. The add-in helps you send well; the integration notices you did not send at all.
Can an AI agent send video emails from Outlook automatically?
Yes, because the agent holds your video library as well as the mailbox connection. A routine can attach a recorded greeting for new prospects, a follow-up video for people who went quiet, or a testimonial playlist for unanswered proposals.
Worth being clear about what is personalised. The video is recorded once, so it is the same for everyone who receives it. What is specific to the recipient is the decision to send it now, for this reason, which stops being true if you point the routine at everybody.
Should it send automatically or just draft?
Draft, at first. Reminders and drafts can run freely because nothing leaves your mailbox and the worst outcome is something you delete.
Read the drafts for a few weeks before promoting any category to sending. You are watching for the agent misreading a thread, such as treating a polite decline as silence. Complaints, legal notices and anything from a regulator should never be answered automatically.
What videos should I record before setting this up?
Three. A greeting under thirty seconds saying who you are and what happens next, with no pitch in it. A follow-up under a minute that gives someone an easy way back into a conversation. And a testimonial playlist of two or three short customer clips with nothing from you in it.
Build the testimonial playlist first. Someone weighing a proposal is deciding whether to trust you, and other customers answer that better than you can.
Start With the Reminder
The order I would follow: connect Outlook, write a routine that reminds and drafts but does not send, and run it at nine in the morning for a fortnight. Read what it produces. You will learn quickly whether it understands your mail.
Then record the three videos, add them to the routine, and keep everything in draft for another few weeks before letting anything send by itself. The compounding part is the videos, not the schedule.
Dubb Agent handles both halves, which is the reason this combination exists at all: the mailbox connection and the video library are in the same place, so an automated follow-up can carry a recording rather than another paragraph.
If you change one thing after reading this, add the unanswered proposal clause to whatever routine you already run. A proposal sitting in silence is the most expensive thing in most pipelines and the easiest to lose in a busy week.
