Hey Michelle! We use Group Registration for a similar type feel.
- Create registration types. One for each table type, and one for guests. Example - table of 10, table of 5, etc.
- create admission items for each and assign them a cost. Leave the guest admission items as free.
- Now move on to your site. Create a path for your full table first. Add the group registration to the path and set it to a max of 9 additional members.
- next setup your path for guests. This is a "free ticket" path so make it as easy as possible.
now go back to the first path you created and assign the group members as that free ticket path for the guests.
- you'll just repeat these steps for each path.
because you will have different pricing for each is why I chose to do different paths, also for the groups you can only setup maximums per path.
on your first path, at the top of personal
information, if you put the registration type selector, then once they choose which path (leave your guest path off of this list by filtering) then once they select, it will move them to the correct registration path!
The reason we choose to use group vs guest is because of a limitation with guest registration profiles. If you utilize the app at all, guests don't have profiles they can update (I know, it's frustrating to me too!). So we use group so everyone can update their profiles. I hope this makes sense at all, if you need help, feel free to email me at mike.rummage@quility.com!
------------------------------
Michael Rummage
Senior Director of Events & Special Projects at Quility Insurance
Quility Events LLCUnited States
------------------------------