UI/UX for wedding RSVPs!
September 21, 2012 11:17 AM Subscribe
We’re doing online RSVPs for our wedding. Help me design the best-possible online RSVP system!
For our wedding, we’re going to send fancy paper invitations, but all RSVPs will be through an online form – the invitations will have the URL and instructions. The decision to go online-only is already set in stone and we have made arrangements to personally help the few invitees who are not computer-savvy, so any response questioning the wisdom of online RSVPs will be flagged with extreme prejudice!
I would hate to send out our invitations and then realize I’ve designed a bad RSVP system, left out key information, or created confusion among our users (ahem, “guests”), so I’m looking to the hive mind to help me with a) what system we should use, b) what fields should go on the RSVP, c) how it should flow, d) how to handle families who might RSVP for kids, and e) anything else.
a) What system should I use? Currently my plan is to use a Google Form, because then we’ll have a spreadsheet of the data that we can then control, sort, and do some data scrubbing in. The wedding website will have an RSVP link that will pop up the Google Form. I’m uncertain about the paid online RSVP service like http://www.weddingwindow.com - they look nice on the front end, but I’m worried that I won’t have all the options I want or that our information will be trapped in their system instead of exportable to a spreadsheet we can manipulate. But if there’s a hands-down awesome system that allows flexible input (radio buttons, drop-downs, and free text) and will allow me to extract the data to a common format (excel, CSV, Google Doc, whatever), I’d be willing to consider it.
b) What fields should go on the RSVP? Here’s what I have so far; do I seem to be missing anything?
-Your first name
-Your last name
-Coming / not coming
--Branch: Coming leads to Page 2
--Branch: Not coming leads to Page 3
-Standard “We’re sorry can’t make it blah blah” language
-Dinner choice fields
-(optional) Guest first name
-(optional) Guest last name
-(optional) Guest dinner choice fields
c) How should it flow? As you can see above, there’s basically 3 pages: the “Enter your name and yes/no” page, the “sorry you can’t make it page” that it branches to for No, and the “Enter your meal choice and optionally your guest’s name” page. Everyone who is invited is allowed 1 guest, so including a place for 1 guest’s name won’t confuse anyone. (Google Forms forces a final Submit page, but there’s nothing I can do about that.) Any suggestions to improve the flow?
d) Families with kids: we’re inviting 4 families with kids young enough (i.e., grade school through high school) that we’re going to invite them as a family unit. College-age kids will receive their own invitations, but for these families with not-yet-college-age kids it seems more normal for the parents to RSVP for everyone. I have 2 ideas:
-In the Instructions, direct them to RSVP for 2 people then go back and re-RSVP for their family members until they have included everyone who’s coming. So for a family of 2 parents and 3 kids, that’s 3 RSVPs: 2 parents + 2 kids + 1 kid. This is confusing and would essentially result in several lines in the spreadsheet, but keeps the website simple for everyone else.
-Instead of a Yes/No for a guest, include 3 options: “RSVP for myself only, RSVP for myself and my spouse/guest, RSVP for myself and my whole family (3 or more attendees).” Then I’ll create a fourth page in the Google Form that’s similar to Page 3, but allows them to enter up to 5 “Guest” names and meal choices: Spouse/Guest, Child 1, Child 2, Child 3, Child 4. No one invited has more than 4 kids, so we know the maximum number of fields required. This seems like a nice user experience, but I’m worried it could create confusion. Will someone abuse it to try to invite more than 1 non-family guest? Are there other ways it might confuse people?
e) Anything else we should consider?