hey guys.  we had quite a bit of discussion about this.  and at this stage, it's going to be a no-go.  and it's cause we're looking out for you.

it's not that it's hard to do, it just makes things complicated in a couple of ways, and bloom sites are all about being low-maintenence and easy to setup.  another important "feature" is that it's actually zero-responsibility.  the mailing list is yours to keep.  the comments are completely unmoderated.  everything is an external link.   there is no mission-critical data that you are storing for your clients, or in the case of rsvp'ing, brides.

what happens if we create an rsvp thing?  you are now responsible for that data.  server goes down?  you just lost the guest list.  at this stage in the game, you don't needs that responsibility.  and even if we *did* build it -- is it email based?  what happens if an email gets lost in cyberspace -- it's gonna be your fault.  we could also save that information into a database, but then you need to either export it for them on a regular basis, or have some kind of way for them to access just that part of the site.  see where we're going?

and we havent even touched on the fact that everyone one wants something different in their rsvp.  steak and chicken?  gluten free options?  number of guests? etc, etc, etc.  the fact is, just the setup process alone is an application unto itself.

so we've left it as a contact form.  our advice to you is to give your clients the option to add rsvp "instructions" for the contact form, and tell them that they are responsible for managing it on their own since they are the only recipients of the form.  the instructions should say something like "if you are RSVP'ing via this form, please fill in your responses in the message box, thanks!"  simple, effective, and responsibility-free from your end.