Online wedding RSVP and guest list, per ceremony.

Generic RSVP tools ask the same question once: are you coming? A South Asian wedding asks five different questions across one weekend. Anvaya tracks a guest's answer for each ceremony you define — mehndi, sangeet, haldi, baraat, ceremony, reception, welcome dinner, brunch — and rolls them into a single dashboard that shows attendance by event. The data model treats each ceremony as its own first-class object, with its own date, venue, capacity, and guest set. Nothing is collapsed into a single yes-or-no.

Your guest sees one page with toggles for the events on their invitation. You see counts per ceremony. Your caterer sees the right number for the food they are actually cooking. When a guest changes their mind two weeks out, the dashboard updates in real time and the affected vendor counts move with it. The week-before reconciliation that used to take a Saturday afternoon now takes a glance. The activity log records every change with a timestamp, so when your uncle insists he never said no to the haldi, you can show him exactly when he tapped the button.

The states are richer than yes / no. A guest can mark "maybe" when their flight is not yet booked. A guest can mark "regrets" with a one-line note that goes straight to your dashboard, not lost in the email pile. The page saves automatically as the guest taps, so the partner filling out their half of the form on the couch does not lose progress when the kids interrupt. Same form, mobile-first layout, multiple languages on the roadmap for the cousins in Bangalore and London.

Most guest lists already exist. They live in the Google Sheet your mom started in 2024, the Notion table your sister keeps updating, the WhatsApp PDF your future mother-in-law forwarded last week. Anvaya reads them. Upload a CSV, Excel file, or paste a list, and the AI maps the columns automatically — name, phone, email, side of family, family group, plus-ones, dietary, address. Confidence scores show which mappings the AI is sure about and which need a second look.

You preview the parse before committing. If a column is wrong — "Phone #" pulled into the address field, or "Aunty's side" not matched to bride / groom — you fix the mapping with a dropdown. The import handles phone-number normalization to E.164, deduplication on email, and ceremony tags if your sheet already lists them. Names with multiple spellings (Priya / Priyaa / प्रिया) are merged on phone match, not silently overwritten. No strict template. No three-hour data-cleaning session before you can even start tracking RSVPs.

The import is incremental. Add a new column to the same spreadsheet a month later and re-upload — Anvaya merges the new fields onto the existing guest records without creating duplicates. The mapping you confirmed the first time is remembered, so the second import is essentially a one-click refresh. The same flow accepts vendor lists, ceremony schedules, and address books — every place a wedding accrues spreadsheets faster than anyone can clean them up.

The same guest can need a Jain meal at the mehndi, halal at the reception, and step-free access for the ceremony. Anvaya stores dietary, allergen, and accessibility notes per guest per ceremony, then aggregates them into clean counts for the people who need them: caterer, venue, transportation lead, panditji. The exports are tagged per ceremony, so the mehndi caterer does not see the reception bar order and the venue team for the haldi gets only what they need.

Common diets are pre-tagged (vegetarian, vegan, Jain, halal, kosher, gluten-free, nut-free, dairy-free) so the guest sees a familiar checkbox instead of a free-text box that nobody fills out the same way. Allergens get a separate field with severity, and the export flags severe allergens at the top of the caterer's CSV. Accessibility needs (wheelchair, hearing, dietary escalation) ride on the same record so your day-of coordinator does not have to chase three spreadsheets to figure out who needs what. When a guest updates their dietary preference two weeks before the wedding, the next export reflects it — no manual reconciliation.

The seating chart reads the same dietary tags, so the day-of table arrangement can keep the Jain guests near the vegetarian buffet station and the kids' tables close to the accessible exit. The transportation lead sees who needs a wheelchair-friendly shuttle. The bar lead sees the dry-event counts. Every vendor gets the slice they need, ceremony by ceremony, and your wedding planner does not become the single point of failure for "wait, who was the gluten-free guest again?"