|
Sue
|
February 2, 2015 at 10:12 am
Hi there,
Can you advise whether Event Espresso will fit this requirement and which version we should purchase.
Yearly / Bi Yearly Sports Event for up to 1000 participants:
Registrant must indicate they have read Terms and Conditions (via a tick box or similar)
Ability for ‘Group Leader’ to book X tickets for a group
Ability for Group Leader to create attendee list at time of purchase
Ability for Group Leader to amend attendee list at later date
Integration with Mijireh (or similar) – we would prefer not to handle transactions on our own website if possible.
Many thanks for your help.
Susan
(I had signed up for an EE4 demo but no reply yet!)
|
|
Garth
|
February 2, 2015 at 8:10 pm
Hi Sue.
How are you today?
Someone (we call it the Primary Registrant) can purchase X number of tickets for a group at one time. The Primary Registrant will also be able to edit the registration details of the individuals in the group through a link in their confirmation email. They will not be able to change the tickets that were selected, nor add or remove individuals from the group registration. Does that make sense?
Did you get access to the EE4 Demo?
|
|
Sue
|
February 3, 2015 at 3:05 am
Hi Garth,
Many thanks for coming back to me so quickly.
The Event is for a ‘mud race’ so lots of people will logon in advance and purchase X number of tickets with a view to adding attendee info later / or even change this information as the race gets closer. (Whether or not this should be a feature is another story I suppose).
Going on your response it looks like this ability to modify the attendee list (once submitted) may not be possible?
Final question was integration with Mijireh – presume is easy enough to set up?
No access to EE4 yet – I am running EE3 decaf on a development site at the moment but I’m not sure I am getting full functionality with this version, and would really like access to the full demo!
Many thanks,
Susan
|
|
Dean
|
February 3, 2015 at 5:57 am
Hi Sue,
The modifications are partially possible. In EE the Primary Attendee (Group Leader) can buy tickets in two ways, depending on how you have set up the event.
1) They buy X tickets but only supply their name and details and answer appropriate questions based on them being the registrant. Additional attendee data is not gathered.
2) They buy X tickets´and answer their name and details and questions AND answer it for the Additional Attendees (Group Members).
Most people for your kind of setup would use option 2 as it allows you to gather all the pertinent info on each runner. If you don’t need much info on the runners, option one is viable – simply use one or two questions that the Primary Attendee needs to answer (e.g. a text box to list the group member names).
Using option 2, the attendee wants to change runner Bob’s surname, no problem he can do that.
He wants to replace Bob with Joan, that’s fine just edit Bob and change the details over to Joan
He wants to add a new attendee to the group. Nope, can’t be done, he would have to register again.
Same thing with attendee deduction.
So modifications are fine, but additions/subtractions not so much. The admin can of course delete and add in attendees.
Mijireh. EE4 supports it out of the box, EE3 does NOT support it.
Regarding the different EE versions, please check out this comparison table: https://eventespresso.com/differences-ee4-ee3/. You might find EE4 does most of what you need.
You can also test drive EE4 (for free) over at http://demoee.org
|
