Multi-event wedding RSVP

What is a multi-event wedding RSVP?

Modern weddings are a weekend, not an evening. There is often a welcome dinner on Friday, the ceremony and reception on Saturday, and a send-off brunch on Sunday — plus rehearsal dinners, after-parties, and pre-wedding gatherings in between. Each of those events usually has a different guest list and a different capacity, so a single "will you attend?" question does not work.

A multi-event RSVP treats every event as its own question. A guest invited to all three days can accept the welcome dinner, decline the brunch, and confirm the reception in a single flow. The RSVP form asks a reception-only guest about the reception. That gives you an accurate headcount for each meal, each venue, and each vendor — instead of guessing how many of your "yes" guests will actually show up to the Friday dinner.

• Every event asks separately. Welcome dinner, ceremony, reception, brunch — each collects its own yes, no, or maybe.
• Different guests, different events. The whole crowd for the reception, a smaller circle for the rehearsal dinner and brunch.
• One master list. You manage a single guest list and assign each guest to the events they belong to.

Invite different guests to different events

The hardest part of a weekend wedding is that the guest lists overlap but never match. Two hundred people come to the reception, forty to the welcome dinner, sixty to the brunch — and plenty of guests appear on two of those lists but not the third. Managing that in a spreadsheet means color-coded columns and constant second-guessing.

When adding or editing a guest, select their event invitations. The RSVP form uses those invitations to show the events they can answer. Review invitation changes carefully once answers exist: an answered invitation is protected from removal, and conflicting changes require a fresh review.

• Assign per event. Check the events each guest is invited to; everything else follows from that.
• RSVP shows invited events. The RSVP form asks each guest about the events they are invited to.
• Review invitation changes. Add event invitations when plans change; existing answers are protected when you edit membership.

How do you manage RSVPs for multiple wedding events?

You manage them from one dashboard that keeps a separate tally for each event. Every submitted form response — opened from a text, WhatsApp invitation, or the website — flows into the same place, and Duva rolls it up into attending, pending, and declined counts per event. You never export three spreadsheets and reconcile them by hand.

Because the headcounts are independent, you can plan each part of the weekend on real numbers. Give the welcome-dinner restaurant a firm count without waiting on your reception RSVPs. Order brunch for the exact number of guests who said yes to Sunday, not for everyone who is coming Saturday. And when you need to chase stragglers, you can nudge only the guests who have not answered a specific event.

• Live counts per event. Attending, pending, and declined totals for each event, updated the moment a guest replies.
• Party & household RSVP. One guest can respond for their whole party per event — plus-ones and kids included.
• Chase only non-responders. Send a reminder to the guests who have not answered one specific event, not the whole list.
• Meals and details per event. Collect meal choices, dietary notes, or song requests scoped to the right event.

Worked example: a reception and a smaller brunch

Illustrative example, not a customer case study: Ava and Daniel invite Maya and Sam to the reception, but only Maya to brunch. Maya accepts both events for herself and declines the reception for Sam. The reception count is one attending and one declined; brunch is one attending. Sam is not a brunch non-responder.

Set up those two events, add the fictional party, and select each member’s invitations. Preview and submit their different responses. Check both event rosters before importing the full list. This catches the common mistake of treating every household member as invited to every event.

RSVPs by text, WhatsApp, or your website

Duva sends a personal RSVP link by SMS to +1 numbers and WhatsApp to supported numbers outside +1. The guest opens a browser form, answers for the invited party members and events, and submits. A reply in the message thread does not record attendance. No Duva account is required; the form needs internet access.

Each saved answer belongs to an invited party member and event. A phone code is used in the supported add-phone flow, not as a mandatory step for every RSVP. Hosts can review attendance and record an answer received directly from a guest.

• SMS for +1 numbers. A personalized text with a link to RSVP to each of their events.
• WhatsApp outside +1. The same per-event RSVP delivered in the app international guests use daily.
• Website name lookup. Guests can also find themselves on your site and RSVP without any messaging.

A website and schedule that keep up

Your wedding website builds a schedule from the events you publish, with times, locations, and attire notes. Review the public schedule separately from the invitation-specific RSVP form: a schedule entry is information, not an invitation. When details change, update the event and review the guest page before sending an announcement.

On the day itself, you can broadcast an announcement to a single event — a shuttle time for the welcome dinner, a room change for the reception, a "brunch starts at 10" reminder — and only that event’s guests get it. Large weekends are no problem: Duva handles guest lists from a few dozen to 800 and beyond.

• Auto-built schedule. Each event appears with its own time, venue, dress code, and add-to-calendar link.
• Day-of announcements. Message one event’s guests instantly when a detail changes.
• Directions per venue. Different locations across the weekend each get their own map and details.

What a multi-event RSVP with Duva costs

Collecting the RSVPs is free no matter how big the weekend gets: whether you run three events or seven, the website, the master guest list, and every response cost nothing — there is no plan to subscribe to, and no fee that scales with your guest count. Messaging runs on a one-time $10 unlock — each invitation and reminder Duva delivers over SMS or WhatsApp never uses credits — and credits enter the picture only for the announcements that come from you — that shuttle time, that "brunch starts at 10" note — priced at a single credit per person reached, regardless of message length. The unlock includes 100 credits; if the weekend calls for more, one-time packs come in three sizes — 500 credits for $40, 1,500 for $99, or 3,000 for $165 — with no expiry date, and nothing is ever auto-charged unless you opt into auto-refill. Responses guests submit on the website never cost you anything.