The AgentivUse cases

An agent in Outlook that sorts the unread inbox into what needs you, drafts the replies it can handle and writes a one page brief before each meeting

Function: OperationsEffort: An afternoonPublished: 2026-10-17

The problem

A manager on Microsoft 365 starts the day with eighty unread emails, half of them calendar responses and newsletters, and the three that need a decision are buried. Meeting prep means scrolling back through threads with each attendee, so people walk in without knowing what was last agreed.

How the agent works

The manager opens Outlook, pins the Claude for Outlook pane and asks what needs me. Claude reads unread mail and attachments and sorts them into three groups: action items with a one line reason each, items it can handle (scheduling asks, acknowledgements, standard documents) which arrive pre drafted, and noise that can be archived in one click. Drafts land unsent in Outlook's compose pane in the manager's own tone, learned from the sent folder, and Claude warns before adding anyone who was not on the thread. For a long thread it summarises what was decided, what is open and who owes what, with a citation to the specific email for each claim. Before the next event it pulls the last thread with each attendee and any attached documents into a one page brief. The add in does not hold the Mail.Send permission, so nothing goes out until the manager reads the draft and clicks Send.

Worked example

Anthropic's Claude for Outlook documentation describes exactly this flow, with prompts such as 'What needs me?', 'Draft replies for everything you can handle', 'Who owes what on this thread?' and 'Prep me for my 2pm'. It reads .docx and .xlsx attachments inline, finds meeting times across attendees and drafts the invite into Outlook's native appointment form. The add in is in beta on Pro, Max, Team and Enterprise plans, installs from Microsoft AppSource, needs Exchange Online and a one time Microsoft Graph admin consent, and Anthropic advises reviewing every draft because inbound email can carry prompt injection.

PDPA note. Inbox content read by Claude, including customer names and attachments, is sent to Anthropic's API (or to your own Bedrock, Vertex AI or Microsoft Foundry endpoint if you route it there) and deleted within 30 days per Anthropic's documentation. Keep it off mailboxes that hold HR, payroll or health matters, apply Conditional Access policies, and read recipient lists before sending.

Get a new agent use case every week

Join the Agent OS Club: every week a new use case with the exact prompts, skill files and setup steps, so you can build your own team of AI agents to run the work for you. It is how The Agentiv runs, on a team of 40 agents and growing. USD 15 a month, cancel any time.

Join the Agent OS Club

Building this for an organization? Learn more at theagentiv.com

Sources

Related use cases

An agent that pulls yesterday's Shopee and Lazada orders into one Google Sheet and flags what has not shipped

OperationsEffort: About a weekShopee · Lazada · Google Sheets

The owner opens two seller centres every morning, exports two spreadsheets and adds them up by hand to learn what sold, which SKUs are running low and which orders are still waiting to ship. On a busy day the check is skipped and a ready to ship order sits past the deadline.

An agent that reads your monday.com project boards every Friday and drafts the client status report

OperationsEffort: An afternoonmonday.com · Claude

Project managers spend Friday afternoon copying statuses and dates out of monday.com into an email or slide for each client. The report goes out late, looks different from one PM to the next, and the overdue items that matter most are buried in a list of everything else.

An agent that sorts the shared Gmail inbox into reply, action and FYI, drafts the replies and logs every decision in a Sheet

OperationsEffort: An afternoonGmail · Google Sheets · Gemini

A shared info@ or ops@ inbox gets a hundred emails a day and the person on duty reads all of them to find the twenty that need something. Replies go out late, tasks hide in threads, and nobody can say afterwards what was handled or why.