Twelve people say they're in. Four days later you genuinely don't know who's actually coming. Somewhere in a fifty-message thread, three people said yes, two said maybe, one asked a question nobody answered, and the rest just went quiet. Figuring out who's left to chase means scrolling back through everything else that happened in the chat since.

So most people don't. They either re-ask the whole group, which annoys the people who already answered, or they just wait and hope it sorts itself out by the day of the event. Neither actually tells you who's coming.

This guide covers how to keep an actual running tally of RSVPs in a group chat, how long to wait before following up, and how to chase only the people who haven't answered instead of the whole group again.

Quick answer: Keep one running yes/no/maybe list that updates as replies come in, ask for a one-word answer instead of an open response, and follow up only with the names still missing after about 48 hours. folk can hold that list in shared group memory as responses arrive in the thread, so asking "who hasn't answered yet" gets a real answer instead of a scroll back through the chat.

Why is tracking RSVPs in a group chat so hard?

Group chats aren't built to hold state. iMessage and Telegram will show you every message in order, but neither will tell you, at a glance, who among twelve people has actually confirmed. That information exists, scattered across replies sent at different times, in different words ("yeah I'm in", "probably", a thumbs-up reaction, no reply at all), and it's on you to reconstruct it by scrolling.

The problem compounds with group size. At four people, you can hold the tally in your head. At twelve or twenty, you can't, and the chat itself becomes the bottleneck: the information you need is in there somewhere, but finding it costs more effort than just asking again, which is exactly the move that annoys the people who already replied.

How do you track RSVPs without a separate app or spreadsheet?

Two habits fix most of this without adding another tool to the plan:

1. Ask for a one-word answer. "Reply yes, no, or maybe" produces responses you can scan and count. An open-ended "let me know if you're coming" produces half-sentences and reactions that are harder to tally at a glance.
2. Keep one running list, updated as replies land. A pinned message with three columns, in, out, and still waiting, updated each time someone answers, means you're never reconstructing the tally from scratch. Whoever's organizing edits it live instead of scrolling back later.

For a group chat with an assistant already sitting in it, this is the exact kind of bookkeeping worth handing off. Instead of updating a pinned list by hand, you ask the assistant directly and it reads the thread for the answer.

How long should you wait before following up with someone who hasn't responded?

About 48 hours. RSVP timing data from QuikRSVP's 2026 analysis of invite responses found only 47.1% of invited guests submitted a response at all, and that the people who do reply mostly do it fast: a majority reply within the first day. The same analysis makes the practical point directly: a guest still silent after 48 hours "has not been mulling it over, they have lost the message." A reminder at that point is a recovery mechanism, not a nag.

That timing matters for the follow-up too. Ping too early and you catch people who were always going to reply, just not yet. Wait too long and the event is close enough that a late "yes" doesn't help anyone plan around it.

Does a guest seeing your message mean they're coming?

No, and this is the assumption that causes the most wasted waiting. A read receipt, a "seen" timestamp, or an emoji reaction confirms the message was opened, not that the person has decided anything. Evite's own guest list marks a separate "Viewed" status distinct from an actual RSVP, which is a tell: even a platform built entirely around collecting responses treats opening an invite and answering it as two different events.

Treat "seen, no reply" the same as "hasn't seen it yet" for follow-up purposes. Both need the same nudge, and neither one is a soft yes.

How folk tracks RSVPs in a group chat

folk, the personal AI assistant that lives in your texts (iMessage, Telegram, and WhatsApp), sits quietly in a group chat until someone talks to it, and RSVP tracking is one of the more direct things you can ask it to hold onto.

• It remembers responses as they come in. Because folk keeps shared group memory scoped to that thread, a reply like "we're in for Saturday" gets held the same way any other group decision does, no separate list to maintain.
• You can just ask. "Who hasn't answered yet" gets pulled from the actual conversation instead of you scrolling back through it, and the answer updates as more replies land.
• It can chase only the people still missing. Paired with a recurring reminder, folk can nudge just the names that haven't responded instead of re-pinging everyone, which is the exact habit that gets a group chat muted in the first place.
• It stays out of the way otherwise. folk doesn't jump in unprompted. It answers when asked and posts the reminders it's told to hold, and the rest of the thread carries on as normal.

Because the tracking lives in the same group everyone's already reading, there's no separate RSVP tool or spreadsheet link competing for attention, and no one person stuck holding the tally in their head.

The bottom line

Tracking RSVPs doesn't take a dedicated app, it takes one running list, a one-word reply format, and a follow-up aimed at the people who are actually still missing instead of the whole group again. A "seen" status isn't an answer, and 48 hours of silence is a signal to nudge, not a reason to wait longer.

Do it by hand with a pinned list, or get started with folk and let it hold the tally for you. It's the same assistant behind reminding a group about an event without spamming everyone and planning a trip with friends in a group chat.