Wedding RSVP: the mini-site that updates your list on its own

There's a precise moment in planning a wedding when you realise the guests' replies aren't a formality but a small project of their own. It's usually around D-60, when you have to give final numbers to the caterer, close the seating plan, and you realise you don't actually know who's coming. There are the firm "yeses", the "we'll try", the silences, the people you chased once who still haven't replied, and those you no longer dare chase. All of it lives in one head, a few texts and an approximate spreadsheet.

The online RSVP exists to turn this chaos into a system. Not just an "I'm coming / I'm not" form, but a mini-site that collects the replies, updates your list on its own, and chases the stragglers for you. This article explains what a good RSVP system actually changes, what to put in it, and why the real value isn't the form but what happens after.

The problem with the "old-school" RSVP

Collecting replies by hand is invisible work that stretches over weeks. A reply comes by text, you note it. Another by phone, you have to remember it until you're at the computer. A great-aunt replies to your mother who tells you three days later. You transcribe all of it into a spreadsheet, when you think of it, and you discover at D-30 that thirty people never replied.

Then the chasing begins, and that's where it gets tedious. You have to identify who's missing (so cross your list with your replies), write a message that's neither curt nor pleading, send it individually (a group message where everyone sees who hasn't replied is a no), and start again for those who still don't answer. Multiplied by the number of stragglers, that's several evenings. And this load, as often, falls on one person in the couple.

The online RSVP doesn't just "save a bit of time". It removes the data entry (the guest replies, the list updates) and it automates the chasing (reminders go out on their own to the right people, at the right times). It's a change in nature, not in degree.

A mini-site, not just a form

A good modern RSVP isn't a field lost at the bottom of an invitation. It's a small web page dedicated to your wedding, in the image of your wedding, where the guest arrives and finds everything they need.

In ÆTHERNA, this mini-site is customisable: you choose a colour palette (or a dark theme), and the page takes on the look of your event rather than that of an administrative form. You activate the useful sections: your story, the dress code, transport and access info, an FAQ for recurring questions ("is there parking?", "are children welcome?"), a gift registry, a tribute to those no longer here. Each couple activates what concerns them and leaves the rest.

The point goes beyond aesthetics. This mini-site answers questions before they're asked. The "what time exactly?", "where do I park?", "what's the theme again?" that would otherwise arrive one by one on your phone in the final weeks are there, self-service. A well-made page is that many messages you won't receive.

Reply per person and per event

Here's a detail that changes everything and that simple forms miss: in real life, a "yes" isn't a global "yes".

An invitation often concerns several people (a couple, a family), and a wedding often has several moments (ceremony, drinks reception, dinner, next-day brunch). The right question isn't "are you coming?" but "who's coming, and to what?". The parents come to the ceremony and dinner but not the brunch. A friend comes to everything. A couple comes to dinner but one of them misses the drinks reception.

An RSVP that handles presence per person and per event captures this reality. You know precisely how many covers at dinner, how many people at the brunch, who to count for the ceremony. These numbers directly feed the rest: the caterer's budget, the seating plan, the logistics. It's exactly the data crossing that a spreadsheet doesn't do and that we detailed elsewhere: an RSVP reply isn't a ticked box, it's a piece of information that propagates everywhere it matters.

Automatic reminders: the real value

If I had to keep one function of the online RSVP, it would be this one. Because it's the one that gives you back the most time and spares you the most discomfort.

The principle: you set a reminder schedule once (for example D-15, D-7, D-3 before the reply deadline), and the system automatically sends a reminder only to the people who haven't yet replied. You write nothing, you tally no one, you don't wonder "did I chase Aunt Michèle or not". People who've already replied receive nothing. Those who drag get a courteous reminder, on your behalf.

The effect is twofold. You recover the evenings you'd have spent on manual tallying. And above all, the response rate goes up, because most non-replies aren't refusals: they're people who opened your message on a Tuesday evening, thought "I'll reply tomorrow", and forgot. A well-placed automatic reminder recovers those replies without you having to play the enforcer.

A clean front, a back-office for you

Technically, the mini-site lives on a dedicated, clean address, like rsvp.aetherna.fr followed by a unique identifier for your wedding. Your guests receive a link, they click, they reply. No account to create, no app to download, no friction. The simpler the RSVP is for the guest, the faster they reply.

On your side, you keep the back-office: who replied, who's coming to what, which custom questions you asked (and you can ask some, in both languages if your guests are bilingual: "allergies?", "need accommodation?", "song to play?"). The replies arrive structured, ready to use, not scattered across your inbox.

That's the whole gap between enduring the replies and steering them. On one side a disorderly flow you catch up by hand; on the other a system that collects, structures, chases and feeds the rest of your organisation.

FAQ

How does an online wedding RSVP work?

You create a page dedicated to your wedding, activate the useful sections (practical info, dress code, FAQ…) and your questions, then send the link to your guests. They reply online, without creating an account. Their replies update your list automatically and feed the rest of your organisation (caterer, seating plan).

When to send reply requests and close the RSVPs?

Send the invitations with RSVP about 8 weeks before the wedding, and set the close around 3 to 4 weeks before, to have time to give numbers to the caterer and do the seating plan. A system of automatic reminders at intermediate deadlines (for example D-15, D-7, D-3 before close) clearly improves the response rate.

How do you chase guests who haven't replied without being pushy?

The simplest is to automate: a system that sends a courteous reminder only to people who haven't yet replied, on dates you set once. Those who've replied receive nothing, you tally no one, and the reminder stays polite because it's neutral. Most non-replies are oversights, not refusals: a well-placed reminder recovers them.

Can you manage presence per event (ceremony, dinner, brunch)?

Yes, and it's important: a guest can come to the ceremony and dinner but not the next-day brunch. An RSVP that handles presence per person and per event gives you exact numbers for each moment, which is essential for the caterer and logistics. That's what ÆTHERNA offers.

Do you need a wedding website or is a simple form enough?

A well-made mini-site saves both parties time: it answers recurring questions (access, parking, dress code, times) before they reach your phone, and it gives a pleasant frame to the reply. It's not essential, but it's a real comfort, especially if many guests travel from far or ask the same questions.

Do guests have to create an account to reply?

No, and it's an important point for the response rate. In ÆTHERNA, the guest receives a link to a dedicated page, clicks, replies, that's all. No account, no app. The simpler the reply, the faster it is.

ÆTHERNA gives you an RSVP mini-site in the image of your wedding, with reply per person and per event, automatic reminders and real-time list updates. Free up to 50 guests, no time limit, no credit card. aetherna.fr/en