I'd like to put in a vote for this feature and offer another example as illustration for its purpose. We have an annual trip that involves renting 2 BR condos for 2 couples to share. Note: Every attendee must be a member.

So a member registers and pays the $100 deposit. The spouse would also like to be counted and receive email updates. We tried offering a registration type of "Spouse" at cost of $0 but we had couples who both registered to pay the $100 and we had other couples who both registered to pay $0. There was a lot of emailing, deleting, and re-registering by me to fix things. Plus couples complained about having to register twice (that is, once each.)

This year I tried the "Guest" option instead. It worked well except that, because the system was unaware that the guests were members, I ended up with two problems.

1) Some members registered guests who were not members. I had to email them to tell them to register their guests as members (pay the $25 membership fee). I would have loved (a) to specify that guests had to be members or (b) to just charge member guests $0 and non-member guests $25.

(Solution b would also address that, for our monthly events, we would like to allow member guests to be $0 and non-member guests are permitted but charged $15.)

2) The automatic Registration Reminder notification that goes out to all members who had not registered ALSO went out to member guests who HAD registered. I got a slew of emails from people that said they were registered but had received the reminder to register. Maybe you can fix this earlier as it seems closer to a bug than an enhancement. Registration reminders should not go out to emails that are already registered for an event.

Meanwhile, these two issues are preventing me from making wider use of the Guest feature. It is so close to being usable for us but it's not quite there.

Thanks for the details, this does illustrate your case quite well.

Unfortunately for now this kind of setup does not seem to common among Wild Apricot clients so it does not look like we can promote this to our roadmap and do anything about this for at least the next 12 months, sorry. So you need to evaluate whether current Wild Apricot functionality with the manual workarounds it requires for you is a satisfactory fit for your registration needs - or consider alternative registration solutions.

OK. We're running an event right now I think provides a good example of what I'm talking about.

We have a golf event that is a team event, two members per team.

I would like to have the ability to have one member sign himself up, and then choose his playing partner from a drop down box or some other control that I provide the range of possible selections.

The current system (using the Guest feature) would work fine, if every member followed my instructions 100% literally and filled out the registration accordingly, but the reality is really quite far from that.

I searched through the registrations for this event today and found 20% had not filled out the form correctly. Here's what happened.

1) My instructions were to fill in the member's own information and then register the playing partner (also a member) as a guest by entering the 2nd member's e-mail address.

2) Some members did this, others did not. Some registered as a Guest "Need a Playing Partner" or "????????', not valid e-mail addresses for existing members.

This is a problem for me because I am now left with two options. Either I continue to allow multiple registrations using the guest workaround above, in which case I have to actively police every registration to make sure it is valid, or I have to have each member sign up individually for every event, which is what I did last year, and I received about a dozen complaints a week about it.

What I would love to see is an enhancement or set of enhancements to the system, where a single member can sign up multiple members (the number of members is most likely going to be unique for each event, I should be able to control this when setting up the registration form) for any single event.

Each member registered for an event in this way should appear on the list of registrants and should receive e-mail about the event in accordance with their own individual e-mail settings. Also the event should appear on their profile as it would if they registered themselves.

Thanks!

John,

Sorry but most likely we will not be able to change anything in this regard before the of 2010.

Also, we are still trying to figure out the core issue here. We do have the ability now to register multiple people in one transaction:

https://help.wildapricot.com/display/DOC/Setting+up+events

But apparently this is not addressing all cases.

I would highly appreciate as much detail /examples as possible to help us understand the key issue we need to address.

Dmitry,

This is really my biggest problem with running our events right now. If you can come up with some kind of solution or even a workaround, that would really help me so much.

We are talking about some big events in the fall that would really be made much simpler with some form of multiple member or group registration.

Thanks for considering it!

John W.

We have a very similar situation with our organization. We have individual memberships; however, groups of individual members work at the same company. We have monthly events at which members will coordinate the event registration for all individual members at his/her company.

Right now, we are having members email us their group registrations. However, it would be nice if members could register both non-members and other members for events. Particularly since their employers are usually picking up the tab for the registration fees. One registration invoice for all including members and non-members would be very helpful.

Thank you.

We have the same request.

We have an annual event for which we sell both individual tickets or tables of 8 for a discounted price. Currently we have the registrant enter all names and dinner choices in a text field for the tables, but as you can imagine, it causes some overhead on the back end to get an accurate count. It also limits our ability to send updates to the other 7 attendees, as John mentioned.

John, thanks for posting.

Everyone - I would appreciate your feedback on this.