The dinner is Saturday. Seven people have said yes, two have said no, and five are sitting on maybe. You need to know how much food to buy, and the only way to find out seems to be texting each of them a version of "so, are you coming?" that you can't make sound casual.
The usual options are sending five separate nudges that each feel slightly needy, or saying nothing and cooking for fourteen. Neither is necessary.
In brief: a maybe is usually a polite no, an unresolved scheduling question, or someone waiting to see who else is going. Send one check-in to the whole event with a date and an easy out. Then plan for your firm yeses plus a few of the maybes, and treat anyone extra as a bonus.
What a Maybe Usually Means
A maybe is rarely indecision about your dinner in particular. In practice it tends to be one of three things.
Sometimes it's a no that felt rude to say. The person doesn't want to turn down a friend in writing, so they leave the door technically open and hope the question goes away.
Sometimes it's a real conflict that hasn't resolved: a work trip that might move, a kid's game that might run late. These people want to come and genuinely can't say yet.
And sometimes it's someone waiting to see who else is going. They'll come if the people they know best are coming, and they're watching the list before committing.
Only the second group is helped by more time. A clear date helps all three, because it gives the polite no permission to land and gives the person watching the list something to react to.
Send One Check-In, Not Five
The instinct is to message each maybe privately. It feels more personal, but it's the most pressure you can put on someone, because a direct "are you coming?" is much harder to decline than a general note.
A single message to the whole event does the job with less weight. Something like: "Planning food for Saturday, so I'll go with whoever's confirmed by Thursday. No worries at all if it doesn't work this time." It gives a date, it explains why you need one, and it makes saying no easy.
A no that costs nothing arrives quickly. A no that feels like letting the host down gets postponed, which is how maybes stay maybes until Saturday afternoon. It's genuinely fine if not everyone can make it, and saying so in the check-in tends to get you a clearer yes from everyone else as well.
Plan for the Likely Number
Once the date passes, plan with what you have. Firm yeses get a seat and a plate. Maybes get a small allowance: a couple of extra servings, a spare chair, nothing that has to be thrown away if nobody comes.
Anyone who turns up beyond that is a bonus, and an easy one to absorb if the food was planned around the people who committed. Cooking for the full guest list every time is how hosts end up resenting the maybes.
For bigger or repeating events, a headcount cap with a waitlist does a lot of this work for you. The Friendsgiving guide walks through how to set one up.
Doing This in TRIPTI.ai
For events in TRIPTI.ai, the host sees a likely turnout range and how many people haven't given a firm yes, as counts. It never names who.
When some invitees are still undecided, TRIPTI.ai can draft a calm check-in with an easy out, once the host has turned on "AI-Powered Features" in settings. The host can edit it and then post it to the event chat with "Send to chat". It goes to the whole chat as one message from TRIPTI.ai, only when the host sends it. It doesn't message individuals, and nothing is sent automatically.
None of this depends on the app. One message to the whole group, a date, an easy out and a food plan built around the firm yeses works the same in any group chat.
Further Reading
- Friendsgiving Made Easy: Plan a Group Dinner Without the Drama, for headcounts, caps and waitlists
- It's OK If Not Everyone Can Make It (And Your Trip Will Be Better For It), on why a clear no beats a hopeful maybe
- How to Coordinate a Weekly Hiking Group Without Endless Chats, for events that repeat
- Organizing a Running Club: Sunday Long Runs That Actually Happen, on getting regulars to commit