|
vml
|
July 17, 2017 at 2:23 pm
I am submitting a ticket about this – I purchased some support to see if I could have someone walk through some things with me to see if there is a better way to create this event than what we have done so far. Client has just asked for more ticket options- and now I am finding the registration a bit overwhelming!
They have multiple ticket options combines with member/non member and guests – and now it is all becoming too busy and confusing so I wanted to see if there is a better way to handle this than what we have done.
|
|
Josh
|
July 17, 2017 at 2:39 pm
Hi Jill,
I can get working on modifying the hosts file so I can see the site. Can you give us more information about the customer’s last minute request? For example what are the new ticket options going to be used for?
|
|
vml
|
July 17, 2017 at 2:47 pm
Thanks Josh — this is the URL of the event I am questioning…and you will see there is already several tickets….but not they realize they need non-member ticket prices (which I think is not a huge issue) — but they also need guest tickets with guest event options and I am thinking the registration process which is already too busy…is going to be a nightmare….hoping there is a resolve to make it all less confusing that I might be missing. http://vml.org/events/2017-annual-vml-conference/
|
|
Josh
|
July 17, 2017 at 2:48 pm
Also can you send the URL(s) of the page in question along with screenshots that show what you’re looking to change? You can post them here or send with the support token form.
|
|
vml
|
July 17, 2017 at 2:50 pm
Sent the link above…will add screenshots to the support token….
|
|
vml
|
July 17, 2017 at 2:56 pm
I will just post it here..not sure where to send with the form. You can see there are already a ton of options and they want more….just want to talk through some options for making this easier….
|
|
Josh
|
July 17, 2017 at 3:13 pm
My first suggestion is to drop the Registration Submitter ticket entirely. It’s not necessary if the Primary Registrant’s registration form is set up to include this. More on that later.
Second suggestion: Instead of allowing up to a maximum of 255 attendees for each transaction, try thinking of a maximum that will fit. This way each ticket option will not have 255 select options.
Third suggestion: Use the ticket selector to capture the number of attendees only. You may end up with only two options this way:
1) Annual Conference – Member
2) Annual Conference – Non-member
The breakfast, luncheons, and spouse activities can likely be broken out from the ticket selector and instead by included as optional registration form questions.
It’s not clear what the Mayors Institute ticket is for, so that can either be clarified there or possibly entered as a option on the registration form.
The key to making this simple is the ticket selector works best if you can capture the actual number of people attending from the first step. The way you have the forms set up now it’s requiring attendee information for every ticket option. So if someone wants to attendee the conference and attend a luncheon there’s a form for each. We want to get that down to one form per person attending.
Fourth suggestion: structure the registration form so you capture the “Registration Submitter” only within the questions for the primary attendee.
Fifth suggestion: If this conference is the only event they’ll be registering for in one transaction, it will work best to deactivate the Multi Event Registration add-on.
|
|
vml
|
July 17, 2017 at 3:19 pm
I have to wrap my head around this — can the time I purchased be done via Skype so I can ask questions?
|
|
Josh
|
July 17, 2017 at 3:22 pm
I can send you a chat link where you can send questions.
|
|
vml
|
July 17, 2017 at 3:33 pm
OK thanks — just trying to avoid the typing — my wrist is killing me, but I get it. Appreciate your help.
|
