How to Use Muse to Schedule a Meeting

Muse, Meta's personal AI agent, sits at the intersection of several confirmed abilities here: it connects to calendars and email, it can work through its own browser where no direct integration exists (per TechCrunch's reporting), and it drafts and sends messages — with a check-in before anything goes out, since Meta says Muse checks with the person before sensitive actions like sending an email. The realistic flow: Muse reads your connected calendar for openings, ranks slots against your constraints and time zones, drafts the invite message, and waits for your go-ahead. What it can't do is read other people's private calendars — unless they've explicitly shared availability with you — so cross-scheduling still runs through proposed times rather than magic visibility. Because Muse works asynchronously, it can also keep an eye on the thread and come back to you when someone counters with a different time.

• Attendee availability is invisible unless shared with you; expect proposals, not guaranteed consensus, for groups.
• The invite email and the calendar event are two actions — review both, since sending is the sensitive one.
• Time-zone handling is exactly where launch-week mistakes would bite; eyeball the converted times before approving.

1. 1

   Frame the meeting like a brief

   Duration, attendees, purpose, and the deadline week: '45-minute kickoff with Ana, Priya, and Tom, sometime the week of the 12th, before the sprint starts.'

2. 2

   State your windows and anti-windows

   When you're available and when you're absolutely not — including buffers. 'Never back-to-back with client calls' is the constraint Muse can't guess.

3. 3

   Handle time zones explicitly

   Name each attendee's zone and their working bounds: 'Berlin folks no earlier than 9:00 their time.' Never leave conversion implied.

4. 4

   Ask for ranked options, not one pick

   Three ranked slots with reasons beat a single choice; if the group counters, you have fallbacks ready without another round trip.

5. 5

   Approve the invite as two artifacts

   Review the email text and the event details (time, zone, video link) separately, then approve both. Muse holds the send until you do.

A book club organizer trying to sync six members spread between Denver and Lisbon for the fall kickoff.

I need to schedule our book club kickoff, 60 minutes, sometime in the week of September 21. We're split between Denver and Lisbon, so late afternoons my time work best. Check my calendar for open slots and rank the top three. Then draft a short email to the group proposing those options with a two-line agenda: pick the fall books and split hosting duties. Keep it before 20:00 for the Lisbon members. Show me the email before anything is sent — don't send it without my OK — and hold off on creating the event until people confirm.

• Attendees and how they'll receive the invite

  It determines whether Muse drafts an email, proposes times in a message, or both — and who needs which version.

• Duration and purpose

  An agenda line in the invite raises acceptance rates, and duration drives which slots even qualify.

• Everyone's time zones and working hours

  The single most common scheduling failure; explicit bounds keep proposals humane.

• Your real availability, including buffers

  Your connected calendar shows bookings, not fatigue — travel time and recovery gaps have to be stated.

• Priority if nobody's ideal slot overlaps

  Decide in advance whose convenience wins, so the fallback rule is set before the thread gets tense.

For this task, it is smart to make Muse check with you before it takes certain actions. Decide your rules up front and include them in the prompt.

• Sending the invite or proposal email — Sending email is the canonical sensitive action Muse checks first — read the wording and recipients before approving.

• Creating the calendar event — The event commits your time and notifies attendees; it should only be created for the slot you actually chose.

• Counter-proposals when attendees push back — Concessions on timing are social currency; you should decide what you're willing to give up, not the agent.

• Rescheduling after the invite is accepted — Moving an accepted meeting costs goodwill — that decision and its apology draft deserve your full read.

• ✓Put your constraints in a reusable block and prepend it to every scheduling ask; consistency across meetings is what makes the ranked slots trustworthy.
• ✓For groups, ask Muse to propose times that all zones hit within working hours first, then flag the best compromise if none exist.
• ✓Include the agenda in the invite from the start — it shortens the accept loop and gives Muse something concrete to reference if people ask questions.
• ✓Let Muse watch the reply thread afterward; it comes back to you when someone counters, which is where scheduling threads usually stall.
• ✓Double-check daylight-saving edge cases yourself for now — a launch-week agent and a DST transition is not a bet worth taking.