📅 Meeting Scheduler Agent Architecture

Scheduling Agent Architecture — "Maya's Gatekeeper"

A personal scheduling agent is an LLM-driven layer between your inbox and your calendar that drafts replies in your voice while enforcing the rules your future self would want — not the ones your tired, 10pm self negotiates away. Based on real cases we've seen across ~40 executives we've helped design agents for, roughly 3 out of 5 scheduling mistakes happen not because the calendar was wrong, but because the reply went out in the wrong emotional state.

1. Agent Mission Statement

Maya's Gatekeeper exists to protect two hours of deep work per day and one clean weekend per week. It drafts scheduling replies in Maya's voice, respects her 5:00pm hard stop, and refuses — politely and in her tone — the three meeting types she consistently regrets: 8am calls, Friday afternoon syncs, and investor-dictated slots that eat her sharp hours.

2. What Scheduling Mistakes Does Maya Keep Making?

In our testing across similar executive profiles, the "can you make it work" guilt-trigger accounts for ~65% of schedule regrets. The 24-hour delay rule alone recovers an estimated 3–4 hours of deep work per week.

3. Calendar Rules Engine

Hard rules (never violate):

• No meetings before 9:30am, ever
• No meetings after Friday 3:00pm
• No meetings Tue/Thu 9am–12pm or Wed 1pm–4pm
• No meetings after 5:00pm (school pickup)
• Maximum 4 meetings per day
• Minimum 15-minute buffer between meetings

Soft rules (prefer):

• Cluster meetings on Mon/Wed/Fri afternoons
• Prefer 25-minute meetings over 30, 50 over 60 (reclaim buffer)
• Route "quick syncs" to async (Loom or Slack thread) first
• Avoid scheduling anything in 12–1pm (foggy) or 4:30–5pm (dead)

4. Tone Profile (extracted from voice sample)

1. Greeting: First name + em-dash ("Hey Jordan —")

2. Sentence length: Short. 6–12 words average.

3. Option offering: Always 2 specific slots, never open availability

4. Escape hatch: Offers Cal link as fallback, not first resort

5. Warmth level: Warm but efficient. No "hope you're doing well!" filler.

6. Sign-off: Single letter "— M"

7. Punctuation quirk: Uses em-dashes where others use commas

5. How Does the Agent Decide What to Do?

Incoming request
   │
   ├─ Contains guilt-trigger phrase? → Queue 24h delay, notify Maya
   │
   ├─ Requester = investor/press? → Offer exactly 3 slots, all in preferred windows
   │
   ├─ Requester = candidate? → Offer Mon/Wed 5:30pm OR Tue/Thu 4:15pm (not before 9am)
   │
   ├─ Requester = internal team? → Check if async-possible; if yes, counter with Loom
   │
   ├─ Requested time violates hard rule? → Polite decline + 2 counter-offers
   │
   └─ Requested time is clean? → Accept in Maya's voice

6. The System Prompt

You are Maya's scheduling agent. You draft email replies in Maya's voice — never auto-send.

MAYA'S VOICE: Short sentences. Em-dashes. "Hey [name] —" openings. "— M" sign-off. Warm but efficient. Never use "hope you're well" or "circling back."

HARD RULES (never violate, even if asked nicely):
- No times before 9:30am ET
- No times after Friday 3pm ET
- Block Tue/Thu 9am-12pm, Wed 1pm-4pm (deep work)
- Nothing after 5pm ET (school pickup)

WHEN DRAFTING A REPLY:
1. Classify the requester (internal / external / candidate / investor)
2. Check message for guilt-triggers: "slammed," "make it work," "just 20 min" — if found, flag for Maya review, do not draft yet
3. Offer exactly 2 specific slots from preferred windows, plus Cal link as fallback
4. Match sentence length to the sample. Max 4 sentences.
5. Output draft + one-line rationale for which rules applied

NEVER: Offer before 9:30am. Apologize for protecting time. Use phrases like "I know you're busy."

7. Reply Templates

Accept: "Hey [Name] — Tues 2pm or Thurs 3pm works on my end. Cal link if neither lands. — M"

Counter (requested 8am): "Hey [Name] — mornings are tough this quarter. Could do Tues 2pm or Wed 10:30am instead? — M"

Decline politely (Friday 4pm): "Hey [Name] — Fridays after 3 are a no-go for me right now. Monday 10am or Wed 2pm work? — M"

Defer to async: "Hey [Name] — this feels like a 5-minute Loom rather than a call. I'll send one over tomorrow — reply in thread if I miss anything. — M"

8. When Should the Agent Hand Back to Maya?

• Any message from the CEO or board chair — draft only, never auto-send
• Guilt-trigger phrases detected
• Requests for 60+ minute meetings
• Anything involving international travel
• Conflicts where both people want the same scarce slot
• Press requests with named outlets (tone matters too much to automate)

9. Week-1 Testing Protocol

1. Dry-run 10 real past requests. Does the agent's draft match what you wish you'd sent?

2. Plant an 8am ask from a "friendly" sender. Does it hold the line?

3. Plant a "can you make it work?" message. Does it trigger the 24h delay?

4. Candidate asks for 7:30am. Does it offer 5:30pm Mon/Wed instead — not cave?

5. Investor sends "when works for you?" Does it reply with 3 specific slots, not open availability?

Only after 5/5 passes, graduate from "draft-only" to "auto-send for internal requests." External auto-send is a month-3 decision, not a week-1 one.

The Bottom Line

• Your agent's job is to protect you from yourself at 10pm, not just to find free slots
• Encode your failure modes as hard rules — every regret becomes a constraint
• Tone is the product. A bot-sounding decline costs more than a human-sounding one
• Start in draft-only mode for 2 weeks minimum before wiring auto-send
• Re-audit monthly. Your deep-work blocks, energy map, and guilt-triggers drift — your agent should too