Guides

How to collect RSVPs over WhatsApp

To collect RSVPs over WhatsApp, send each guest a single message addressed to them by name, ask one clear question they can answer in a tap, and record every reply against their name in one list. The sending is the easy half. The half that decides whether you get a usable headcount is how you handle the replies.

Last updated: 7 September 2026

Why WhatsApp beats email for a headcount

An emailed invitation competes with everything else in an inbox and is easy to postpone. A WhatsApp message arrives where people already talk to their friends, and answering it costs one tap rather than a reply-all.

That convenience cuts both ways. Because the channel is personal, a message that reads like marketing gets ignored harder than an email would. The invitations that work are the ones that look like they came from a person.

WhatsApp suits an event when:

  • You have mobile numbers for most of the guest list.
  • The headcount has to be right, because you are paying per head for catering or seating.
  • You need more than a yes or no, such as dietary needs or a plus-one count.
  • Your guests are spread across countries and email deliverability is unreliable.

It suits it less well when your list is mostly corporate email contacts with no mobile numbers, or when the invitation itself has to carry a lot of formal detail.

What you need before you send anything

Almost every failed RSVP round traces back to the list rather than the message. Get these right first.

Phone numbers in international format

Every number needs its country code, written without spaces, brackets or dashes. This is the E.164 format: a plus sign, the country code, then the number. A UK mobile written as 07700 900123 will not deliver. Written as +447700900123 it will.

This is the single most common reason invitations fail to arrive, and it is worth half an hour of cleaning before you send to two hundred people.

One row per invitation, not per person

A couple sharing a household usually wants one message, not two. Decide up front whether the Okonkwo family is one row with a party size of four, or four rows. Mixing the two is how a headcount ends up wrong.

A single question you actually need answered

Every extra question costs you completed replies. Ask whether they are coming. Ask how many are coming. Ask about dietary needs only if you are serving food you can change. Anything beyond that belongs in a follow-up to the people who said yes.

How to send the invitations

There are three ways to do this, and they differ mostly in how much of your own time they consume.

By hand, one message at a time

Fine up to about thirty guests. It is the most personal option and costs nothing but an evening. Past that, the tallying becomes the job.

A broadcast list

Free and quick, with one trap worth knowing: WhatsApp only delivers a broadcast to recipients who have saved your number in their contacts. Guests who have not will never see it, and you will not be told. Replies also arrive as ordinary one-to-one chats that you still have to read and record yourself.

A tool built for RSVPs

Sends each guest an individually addressed message, delivers to anyone with WhatsApp regardless of whether they have saved your number, and writes the replies into a list as they arrive. This is what Avently does.

What to write

A WhatsApp invitation has to do its work in the few lines visible in a notification. Lead with who is asking and what the event is. Put the date early. Make the ask unmistakable.

Hi Amara — you’re invited to the Riverside Benefit Dinner on Saturday 14 March, 7pm at the Riverside Rooms.

Can you make it? Just reply Yes or No and I’ll do the rest.

Four things that measurably help:

  • Use the guest’s name.A message opening with “Hi” and nothing else reads as a broadcast.
  • Give the date before the ask. People decide on availability first.
  • Ask exactly one question. Follow-ups can come after a yes.
  • Say how to answer. “Reply Yes or No” outperforms an open invitation to get in touch.

Avoid links in the first message where you can. A link turns a one-tap answer into a page load, and it makes the message look like marketing.

Tracking the replies

This is where informal approaches fall down. Replies arrive over days, out of order, and often not as the word you asked for. “Wouldn’t miss it” and “we’re in” both mean yes. Someone answers for their partner. Someone says yes and then changes their mind a week later.

Whatever you use, you need to be able to answer four questions at any moment:

  • Who has replied, and what did they say?
  • Who has not replied yet, so you know who to chase?
  • Whose message failed to deliver, so you can reach them another way?
  • What is the current confirmed headcount, including plus-ones?

If those four answers live in a chat thread rather than a list, you will end up rebuilding them by hand the night before. Keeping them in a spreadsheet is covered in tracking RSVPs in a Google Sheet.

How this works in Avently

Avently is built for exactly this loop. The short version, end to end:

  1. Step 01

    Connect a guest list

    Point Avently at a Google Sheet with a guest column and a phone number column, shared with the service account. Extra columns are yours to use.

  2. Step 02

    Set up the invitation and your follow-up questions

    Guests receive an invitation carrying your event name and date, with Yes and No buttons to tap. You write the message that greets everyone who says yes, and up to three follow-up questions, such as how many additional guests they are bringing and any dietary requirements.

  3. Step 03

    Send, and watch the replies land

    Each guest gets their own message addressed to them by name. Answers are written back to your sheet as they arrive, and the dashboard shows the running headcount alongside anything that failed to deliver.

Guests who change their mind can reply CHANGE at any time to update their answer, so a late cancellation corrects the count instead of hiding in a chat thread.

Five mistakes that cost you replies

  • Numbers without country codes. Silent delivery failures that look identical to guests ignoring you.
  • Asking three questions at once. Each one is another reason to answer later, which means never.
  • Sending from an unrecognised number. Say who you are in the first line if the number is not already in their phone.
  • No reminder. A single polite nudge to non-responders about a week out typically recovers a meaningful share of the list.
  • Counting silence as no. Check your delivery failures before you assume someone is not coming.

Common questions

Can you collect RSVPs through WhatsApp?

+

Yes. You can send each guest an invitation as a WhatsApp message and record their reply against their name. Doing it by hand works for a short list. Past roughly thirty guests, the chasing and transcribing is the part that takes the time, so most hosts use a tool that sends the messages and writes the replies down automatically.

Do my guests need to install anything to RSVP?

+

No. The invitation arrives in WhatsApp, which most guests already have, and they answer in the same conversation. There is no app to download, no account to create, and no link that can be lost in a thread.

Is a WhatsApp broadcast list good enough for RSVPs?

+

It is workable for a small, informal event, but it has two real problems. Broadcast messages only reach people who have saved your number, so some guests silently never receive them, and replies come back as ordinary chats you still have to read and tally by hand.

What response rate should I expect from a WhatsApp invitation?

+

Hosts generally see faster and more complete replies than with email, because the message lands in an app people already check and answering takes one tap. Your result depends far more on whether guests recognise the sender and whether the ask is a single clear question.

What if a guest does not have WhatsApp?

+

The message will fail to deliver for that guest. You need a tool or a process that shows you those failures so you can follow up by phone or email, rather than quietly counting them as non-responses.

When should I send a WhatsApp invitation?

+

For a private event, three to four weeks ahead is a reasonable default, with a reminder to non-responders about a week before you need final numbers. Send during waking hours in the guest’s own time zone.

Avently sends the invitations, handles the replies, and keeps your sheet current, so the headcount you quote the caterer is the headcount you have. It is free while in early access.

Start free