Planning anything with more than three people means a group chat that never converges. Your Muse does the unglamorous part: asking everyone for dates, finding the overlap, and proposing real options with prices. You make the call; it tells everyone and calendars it. Built for dinners, weekend trips, and family gatherings.
Connect these first
Your calendar (to know your availability) and email or chat access (to read the thread). Booking connectors only when the plan involves reservations.
Collect the constraints
Instead of you playing secretary across a 200-message thread, Muse asks everyone for their unavailable dates and collects the answers in one place. You get a clean list of who can’t do what — without reading a single ‘wait, I can’t do Thursday’ message.
Paste into Muse
We're planning [a weekend trip] for [6 people: names]. Read [this group chat / email thread] and ask anyone who hasn't answered for their unavailable dates in [month]. Summarize who's free when in a simple table. Don't propose anything yet.
Find the slot
Muse finds the overlap in everyone’s availability and turns it into real options — dates with prices, venues, or flight costs attached — so the group compares facts instead of vibes. You see two or three workable plans, ranked by what fits most people.
Paste into Muse
From the availability table, find the [Saturday / weekend] that works for everyone. Then propose 3 options: [restaurants that take reservations for 6 / Airbnbs under $[X] total], each with price, link, and one line on why it fits. Book nothing.
Lock it in
Once you pick the plan, Muse communicates it to everyone, adds it to the calendars, and confirms the bookings — the decision becomes the plan without you herding anyone. Everyone gets the same details: where, when, and what it costs them.
Paste into Muse · asks your approval
I've picked [option 2]. Book it: [restaurant for 6 at 7pm Saturday / the Airbnb]. Confirm the total with me first. Then message the group with the details and add it to my calendar.
Handle the stragglers
Someone always goes quiet — the deposit unconfirmed, the RSVP unanswered. Muse sends the polite follow-ups nobody wants to send, tracks who still owes what, and reports back who’s in and who’s out. You never have to chase anyone yourself.
Paste into Muse
Two days before [the event], check who hasn't confirmed in the thread. Draft a short nudge to each of them — friendly, one line. Show me the drafts before sending.
Where approvals sit
Collecting dates and proposing options need no approval. Booking anything or messaging the group happens only after you pick — the agent never commits your friends' Saturday on a draft.
What to verify
Do one human sanity check on the headcount and dates before booking — group chats are where agents most often misread intent ("maybe" is not "yes"). Confirm the booking confirmation matches what the agent reported.
What can go wrong
Agents misread social nuance: the lukewarm "sounds fun" that meant no, the dietary restriction mentioned three weeks ago in another thread. State the must-haves explicitly ("Maya is vegetarian, no stairs for Dad") rather than hoping the agent remembers. And confirmations still deserve your eyes — a wrong date on a group booking is six people's problem.
Related
The dinner half of group plans: the book-dinner playbook → holds the table through OpenTable once the group picks a night.
No more 200-message threads: questions
Group plans die in the thread — the unread messages, the maybe-dates, the friend who never replies. These answers cover how the agent collects dates without the chaos, finds the overlap, and chases the stragglers so you don’t have to.
- Does everyone need to use Muse for this?
- No — only you. Everyone else just answers normally in the group chat or email; your agent reads their replies like you would.
- What if there's no date that works for everyone?
- Ask the agent to show the two best partial options: "which date gets 5 of 6, and who's missing." Then you make the judgment call it can't.
- Can it split costs too?
- Yes — add a step: "Split the $[total] evenly among [names] and draft the payment requests." Review the math before sending; agents are oddly casual with arithmetic.