Wedding RSVP tracking and reminders

An RSVP list is more than a yes/no column. Real tracking means households (not just individual names), plus-ones, meal choices per guest, dietary tags and notes, mailing addresses, invite delivery status, and current RSVP state — attending, pending, or declined. Missing any one of those means someone ends up cross-referencing a second list later, usually close to a deadline.

Mira's guest list keeps all of that in one polished table instead of splitting it across a spreadsheet, a paper stack of RSVP cards, and a separate meal-count tally for the caterer.

Tracking RSVP state only helps if it is easy to act on. Mira's guest communications turn the guest list into a queue: filter to exactly the households that have not responded yet, then send, resend, or review follow-ups without leaving that filtered view. Delivery and message history stay attached to each household, so a follow-up does not depend on remembering who was already reminded.

Because the reminder queue and the guest list are the same data, an RSVP that comes in updates the same row a reminder was about to go out to — there is no separate list to reconcile afterward.

Not every step happens inside the workspace. Caterers and venues usually want a plain guest or meal-count export, and Mira supports a CSV export of the guest list for exactly that case, so the operational workspace does not become a dead end when a vendor needs a simple file instead of a login.