# Which Managed IT Clients Are Due a Quarterly Business Review? Read It From Outlook Calendar

An IT managed service provider's agent reads its account manager's Microsoft calendar each month and lists clients with no review in 90 days and none booked.

[Run this on Rush](https://cloud.getrush.ai/run/find-clients-due-a-business-review/microsoft-calendar/). Opens the console with this prompt ready to send. Connect Microsoft Calendar there first.

## What the agent does

This is for an IT managed service provider that looks after the computers, networks and Microsoft 365 tenants of a few dozen small businesses. Its contracts promise each client a quarterly business review, a meeting to go over tickets, risks and next year's hardware, and the account manager books them in their own Outlook calendar. Each month someone has to work out which clients are overdue, which nobody does until a client asks. The run names one connection, `microsoft-calendar`, signed in as the account manager, which asks Microsoft for `Calendars.ReadWrite` on that person's own calendars.

The agent reads two windows from Microsoft Graph's `GET /me/calendarView`, the last 120 days and the next 45, each with `startDateTime` and `endDateTime`, `$select` for `subject`, `start`, `end`, `attendees`, `organizer`, `isCancelled` and `categories`, and follows `@odata.nextLink` until each window is read. calendarView returns each occurrence of a repeating meeting, so a monthly check-in counts once per month, not once per series.

It ties each meeting to a client by the domain of the attendees' email addresses, using the client list in the input (client name and email domain), and ignores cancelled meetings. A meeting counts as a business review when its subject or category matches the words the input gives, such as "QBR" or "business review"; other meetings with the client, such as a project call, are listed but do not count. For each client it finds the date of the last review and any review already booked.

Every client with no review in the last 90 days and none booked in the next 45 is due. For each one, the agent finds a free 60-minute slot in the account manager's working hours in the weeks the input names and creates a hold with `POST /me/events`: subject "Hold: QBR with <client>", `showAs` set to `tentative`, and no attendees, so no invitation goes to anyone. It returns the list of clients due, the last review date, the hold it made, and clients it could not match to any meeting.

## Start it with one API call

`POST https://api.phoenix.so/o/{org}/sessions`

```json
{
  "agent": "claude",
  "input": "Use the Microsoft Calendar connection. Read my calendar with calendarView from 2026-07-17 to 2026-11-14 and from 2026-11-14 to 2026-12-29, following nextLink; ignore cancelled events. Clients (name, email domain): Brightwater Dental Group, brightwaterdental.example; Kessler Freight, kesslerfreight.example; Orchard Lane Law, orchardlanelaw.example; Pike & Sons Builders, pikesons.example. Match a meeting to a client by attendee email domain. It is a business review when the subject or categories contain QBR or business review. For each client, give the last review date and any booked review. For each client with no review since 2026-08-16 and none booked by 2026-12-29, create one event in my calendar: subject 'Hold: QBR with <client>', 60 minutes, in a free slot Tuesday to Thursday 10:00-16:00 America/Chicago during the weeks of 2026-11-30 or 2026-12-07, showAs tentative, no attendees, no online meeting. Do not change or delete any existing event and invite no one. Write qbr-due.md and return the same as JSON.",
  "connections": [
    "microsoft-calendar"
  ]
}
```

1. **Get an API key.** In the console, open Settings, then API keys, and create a key for your org. Send it in the Authorization header as a Bearer token.
2. **Send the request.** POST the body in request.json to https://api.phoenix.so/o/{org}/sessions, with your repository as the resources URL. The run starts in its own cloud sandbox.
3. **Read what came back.** Follow the run on its live stream or wait for the run.completed webhook, then read the result and its trajectory.

## What comes back

The session returns `qbr-due.md` as an artifact and the same list as JSON in `result`, and the account manager finds tentative holds in their calendar for each client that is due. They open each hold, invite the client's contact and add the meeting link, or delete the hold if the client has already agreed another date by email. No client hears anything until the account manager sends the invitation.

What the account manager checks: clients whose staff use another email domain from the one on the list, who will show as due when they are not; reviews held on a client's site and booked under another subject; and the clients listed as unmatched, which had no meeting at all in 120 days. The transcript shows every Graph call, including each event the run created, so a hold in the wrong week is easy to find.

## Run it on every start of the month

In the console, a Project automation with a `schedule` trigger, `cron` `0 8 1 * *` in the provider's `timezone`, runs a saved agent that names `microsoft-calendar` on the 1st of each month. Its instructions hold the client list and the review rules and state the windows relative to the day it runs (the last 120 days, the next 45, holds in the second and third weeks), so the automation's prompt never needs new dates.

When a new client signs, adding their name and domain to the saved agent's instructions puts them in the next month's check. Each month's run is its own session, so the provider can show a client when every review in the contract was held.

## Why run it on Rush?

The review dates already sit in the account manager's calendar; what is missing is someone reading them against the client list every month. A Graph script can count events, but meeting subjects are written by people, and a script cannot tell a QBR called "Q3 check-in w/ Kessler" from a project call. The agent reads the subjects and categories, lists what it counted, and leaves the client invitation to the account manager.

The sign-in stays in Rush's connection, used from outside the agent's computer, instead of a Microsoft app registration and a client secret the provider has to maintain. Each run keeps a record of every event it read and created, and the session lists what its model calls cost.

## Frequently asked questions

### Will the agent invite our clients?

No. It creates holds with no attendees, so Microsoft sends no invitation, and the prompt forbids changing existing events. The account manager invites the client from the hold.

### Can it read other staff members' calendars?

No. The connection asks for `Calendars.ReadWrite`, which covers the signed-in person's own calendars. If two account managers split the clients, each signs in and runs the check on their own calendar.

### What if a client had a review last month that was booked by the client?

It counts if the account manager accepted the invitation, since a meeting they were invited to shows in their calendar like any other. It needs the right subject or category, which is why unmatched meetings are listed.

### Can it write the review agenda too?

Not from the calendar alone. The agenda needs the client's tickets and assets, which live in the provider's own tools; a second step with access to those could draft it.

## More Microsoft Calendar jobs

- [Propose Interview Times From Each Recruiter's Microsoft 365 Calendar](https://getrush.ai/run/propose-interview-times/microsoft-calendar/)
- [Are Next Week's Viewings Ready to Go? A Property Management App's Check of Each Leasing Agent's Outlook Calendar](https://getrush.ai/run/check-next-weeks-property-viewings/microsoft-calendar/)
- [How Does Time-Tracking Software Draft Each Consultant's Weekly Timesheet From Their Microsoft Calendar?](https://getrush.ai/run/draft-weekly-timesheet-from-calendar/microsoft-calendar/)

## More jobs like this: Produce a report or file, no repo

- [Find Dead Code in an Angular App](https://getrush.ai/run/find-dead-code/angular/)
- [Find Dead Code in a Next.js Project](https://getrush.ai/run/find-dead-code/nextjs/)
- [Find Dead Code in a Python Library](https://getrush.ai/run/find-dead-code/python/)

## Keep reading

- [Connect Microsoft Calendar to Rush once, then name it on any run](https://getrush.ai/integrations/microsoft-calendar/)
- [Start your first run from the developer API quickstart](https://getrush.ai/docs/quickstart/)
- [Rush pricing: Free, Pro and Max](https://getrush.ai/pricing/)
