7 Calendar invites in one week. 5 were wrong, and one went to a funding broker.

"Do you have 15 minutes Thursday at 10 to talk about $150,000 in working capital?"

In our simulated test, a remodeling shop's new AI scheduler saw Thursday at 10 was open and sent the broker an invite. The owner found out when the broker replied: "Great, talk Thursday!"

AI Prompts, Reviewed takes one prompt or workflow from How I AI, Claire Vo's show where guests share their screens and walk through how they really use AI. We run it on a small-business job, score it, and tell you what we'd change.

Credit: Based on "How to Create an Automated Meeting Scheduler with Microsoft 365 Copilot," a workflow from How I AI (hosted by Claire Vo, written up by the ChatPRD team), shown by Marco Casalaina, VP of Core AI Products at Microsoft, in the episode "How Microsoft's AI VP Automates Everything with 5 Micro-Agent Workflows" (March 22, 2026). Original workflow: https://www.chatprd.ai/how-i-ai/workflows/how-to-create-an-automated-meeting-scheduler-with-microsoft-365-copilot . Full episode: https://www.chatprd.ai/how-i-ai/microsofts-ai-vp-automates-everything-with-5-micro-agent-workflows

What the original does

Marco opens the Workflows agent in Microsoft 365 Copilot and describes one job in plain English: when one specific person emails asking to meet at a certain time, check his calendar, and if it's free, send a 30-minute invite. Copilot builds it, connects it to Outlook, and runs it in the background.

It's scoped to one sender on purpose. Owners will want it for every customer.

The test

Made-up data for Marrowfield Kitchen & Bath (a made-up remodeling shop) in Denver: owner plus 2 installers, in-home estimates. Clock: Tuesday, Oct 13, 2026. We widened the trigger to "any email asking to meet" and Fed it 8 emails. This is a simulated run built from the failure modes the page's own runbook warns about, not a live Copilot test.

In our simulated run it sent 7 invites. 2 were right. 5 were wrong:

1. Too early. A bathroom lead asked for Thursday at 7:00 a.m. The calendar was empty, so it booked it. The shop opens at 8:00.
2. No drive time. A kitchen lead ("budget around $40,000") asked for Friday at 3:00 p.m. The owner had a 1:30 to 3:00 estimate 40 minutes away. 3:00 looked free. Real arrival: 3:40, 40 minutes late to a $40,000 first impression.
3. Wrong time zone. A cabinet rep in Charlotte asked for "Wednesday at 11," meaning 11:00 Eastern, or 9:00 a.m. Mountain. The invite said 11:00 Mountain, 1:00 p.m. her time.
4. A broker. The $150,000 cold pitch above got a confirmed meeting and a reply from a real inbox.
5. Not a request. On a reply-all thread, one spouse asked the other, "Does Tuesday at 6 work for you?" It booked Tuesday at 6:00 p.m.

The 8th email asked for Thursday at 1:00, which was taken. No invite, no reply. A paying client heard silence.

The page's own runbook already names the fix: "Tighten the sender and intent conditions, then test with one matching and one nonmatching email."

The rerun

Same 8 emails, with written rules: an allowed-sender list, a never-book list, 8:00 to 5:00 weekdays, a 45-minute buffer around visits, both time zones shown, and a drafted reply whenever a check fails.

Result: 3 invites sent (the cabinet rep at 9:00 Mountain, 11:00 Eastern, plus the 2 clean ones). 3 replies drafted for the owner: 8:00 a.m. for the early bird, 3:45 p.m. for the kitchen lead (3:00 plus 45 minutes), and two open times for the client who wanted 1:00. 2 skipped: the broker and the couple's thread. That's 3 + 3 + 2 = 8.

A free slot on your calendar is not the same as a good time.

Verdict: 7/10

Strengths: you build it by describing it. One named sender is a smart, safe scope. The runbook already warns about stray triggers and bad times.

Weakness: "if free, send" knows nothing about your hours, your drive, or the sender's time zone. A taken slot gets silence. And it sends on its own.

Founder tweak: write the rules down before you widen it, put brokers and sellers on a never-book list, and run draft-only for two weeks.

Copy the MCAFax version

This is our own rewrite, not the original prompt. Copy the original from Marco Casalaina on How I AI: https://www.chatprd.ai/how-i-ai/workflows/how-to-create-an-automated-meeting-scheduler-with-microsoft-365-copilot

You schedule appointments from my email for [business name] in [city, time zone].
Act on an email only when ALL of these are true:
1. The sender is on my ALLOWED list, or is replying to a quote or email I sent. ALLOWED: [customers or domains].
2. The email is written to me and asks to meet at a specific day and time.
3. The sender is not on my NEVER BOOK list: funding brokers, lenders I did not contact, sellers, recruiters, [add yours].
Before booking, check:
- Hours: [Mon-Fri, 8:00 a.m. to 5:00 p.m.] only.
- Time zone: convert if the sender is elsewhere; show both times.
- Buffer: [45] minutes around any in-person visit.
- Length: [60] minutes for visits, [30] for calls.
If every check passes: send the invite titled "[type] - [customer name]" with the address or call link.
If any check fails: do NOT send. Draft a reply offering the two nearest open times and leave it for me.
If you are not sure an email is a request: do nothing and list it in my daily summary.
For the first two weeks, draft every invite for my approval instead of sending.
End each day with: booked, drafted, skipped, and why.

Paste it into the Copilot Workflows agent, or adapt it for any assistant that can read your email and calendar.

Before you let AI book for you

1. Write down your hours, drive buffer, and appointment lengths.
2. Build an allowed list and a never-book list.
3. Test one email that should book and one that shouldn't.
4. Run draft-only for two weeks, then auto-send for known customers only.
5. For new leads, a booking page may beat email: https://mcafax.com/notebook/prompts/appointment-booking-reminders

Giving any tool your mailbox? Read SBA's cybersecurity guide first: https://www.sba.gov/counseling/manage-your-business/#strengthen-your-cybersecurity