How to run a wedding RSVP that actually works in the Philippines

If you’re planning a Filipino wedding, you’ve probably noticed that most wedding-RSVP advice online assumes a Western model: one invitation per household, a simple yes/no, maybe a meal pick. In practice, our weddings are more layered. Tito sends regrets for himself but RSVPs for his three adult kids who haven’t replied. Your ninong asks if he can bring his apo. Plus-ones are sometimes a surprise on the day itself.

After running RSVPs for our first cohort of EverAfter weddings, here’s what works.

1. Set max-seats per group, not per guest

Most platforms ask “how many seats?” per individual invitation. That breaks the moment Tita Carmen RSVPs on behalf of her whole house. The cleaner model: group your invitations into households. Each household gets a max_seats cap.

For example: “The Cruz Family” gets max-seats 5 — covering Tito Boy, Tita Carmen, and their three children. The first person to RSVP sees their whole family pre-populated; they confirm one by one. Anyone added beyond the cap throws an explicit error.

2. Plus-ones are an opt-in, not a default

Two truths can be true at once: you want to leave room for partners who aren’t on the original list, and you don’t want to budget for guests who won’t show up. The middle ground:

• Pre-populate the invited people. They’re always allowed.
• Offer a clearly-labelled “Add a plus-one” button — but cap the total at the household’s max-seats. If the household has 4 invited + 2 plus-one slots available, that’s 6 total max.
• Require the plus-one’s name at RSVP time. Anonymous plus-ones are how you end up with seating-chart problems on the day.

3. Collect meal preferences only if you have a plated dinner

If your reception is buffet-style or family-style (which is most Filipino weddings), the meal-preference question creates more friction than information. Guests stress about picking, you get data you don’t need. Hide it.

If you do have plated service, list the options clearly — Beef, Fish, Chicken, Vegan, and Kids’ meal. The Kids option is critical: in Filipino weddings, kids are often part of the celebration, and they need their own portion sized differently. Don’t make their parents pick “Beef but small” from the adult menu.

4. Collect a dietary note even if you don’t collect meal pref

“No meal pref needed, but is there anything our caterer should know?” — a single text field is enough. You’ll get useful responses: shellfish allergies, vegetarian by choice, gluten intolerance, and the occasional “my dad is on a strict halal diet.” Your caterer can plan; your guests feel seen.

5. Run the RSVP wizard on the wedding subdomain itself

Don’t send guests to a separate page like rsvp.everafter.rsvp/your-wedding. That feels detached and impersonal. Keep the RSVP inside the wedding site — {slug}.everafter.rsvp/rsvp — so the moment a guest finishes their reply, they’re right back in the site, scrolling through your story, seeing the venues, watching the photo wall.

That continuity converts more guests to attending. They came to RSVP and stayed for the whole experience. The actual data shows it: on EverAfter sites, ~28% of guests visit a second page after submitting their RSVP.

The PH-specific things to add

Once the basics work, these small touches make Filipino guests feel the wedding is theirs:

• Ninong / Ninang badge on the invitation card — guests should know whether they’re a sponsor or a general guest (different attire, different timing).
• Hashtag on the confirmation page — Filipinos love our wedding hashtags and they drive incredible photo wall engagement.
• Group chat link for Viber / Messenger — separate from the wedding website. Casual updates land there, not in your inbox.
• Pamamanhikan-style backstory on the “Our Story” section. Filipino guests read these. Long lost titas will absolutely scroll your timeline.

What to skip

A few things Western templates push that don’t map to PH weddings:

• Bachelor / bachelorette party RSVPs. Almost no PH couples track these on the wedding site itself. Keep them in group chats.
• Rehearsal dinner as a public sub-event. If you have one, invite directly via Viber. Adding it as a public sub-event confuses extended family who weren’t invited.
• Dress code colour-matching tools. Cute on Pinterest, not used in real weddings. Just write the dress code clearly.

Quick checklist

Before you send the link to your first guest, make sure:

1. Households are grouped with realistic max-seats (count your invited adults + reasonable plus-one allowance)
2. The RSVP wizard is on the wedding subdomain, not a separate page
3. Meal preference is off unless plated; dietary notes are always on
4. The confirmation email includes the wedding hashtag, venue maps, and group chat link
5. You’ve done a test RSVP yourself to feel the flow as a guest

If you build it well, the wedding day feels effortless on the catering + seating side, because every guest already told you everything you need. That’s the whole goal.