Support

Home Forums Pre-Sales Waiting lists – please clarify

Waiting lists – please clarify

Posted: October 8, 2013 at 4:03 am


Roberto Cornacchia

October 8, 2013 at 4:03 am

Hi there, I have a question about waiting lists.
I think I had found the answer in the forum already, but because I haven’t purchased the product yet, the answer looked like:

Support staff content cannot be viewed without the necessary product purchases

So you’ll have to answer this again if you want me to buy 😉

Suppose I have an event with multiple tickets, named A,B,C. I also read that I can setup a secondary event that works as a waiting list when the primary event is full.
Now, suppose there is a cancellation from an attendee with ticked B. What happens? Is the first in line for ticket B contacted? Are waiting lists still divided by ticket type? Is the now available spot for ticket B kept on hold for this person in line? If so, for how long? Or is it just made available on the primary site so that anyone can come and grab it?
Please, let me know in detail how this works. I’ve read many comments about the possibility of a waiting list, but no detailed explanation so far.

This is crucial for me. I can’t buy the product without a good explanation.
Best regards


Dean

October 8, 2013 at 5:08 am

Hi,

Waitlists require manual processing from the admin.

If Attendee A desires to cancel, the admin can copy/move over the next eligible attendee from the waitlist event to the actual event and then cancel Attendee A.

Cancelling before hand will make the spot available to all.

We have a Beta tool that can be used to clone or move attendees making it easier.

It is up to the admin to select a user with the correct ticket type.

We do offer a way for the attendee to cancel the registration themselves (via the WP User Integration addon), I would advise not allowing this if you are using waitlists.

I hope that helps but if you have more questions or need further clarification, please just ask.


Roberto Cornacchia

October 13, 2013 at 8:20 am

Hi Dean,

Thank you for your answer. I have a followup question:

If Attendee A desires to cancel, the admin can copy/move over the next eligible attendee from the waitlist event to the actual event and then cancel Attendee A.

In this case, how will the copied attendee (from waiting list event to main event) be informed? Manually? And how will the online payment work then? Can he then go through the standard payment procedure?
Also: when the admin cancels an attendee, can the payment be refunded sort-of smoothly? Or is it completely manual, outside the scope of eventespresso?

Thanks for your help,
Roberto


Dean

October 14, 2013 at 1:07 am

Hi,

In this case, how will the copied attendee (from waiting list event to main event) be informed? Manually? And how will the online payment work then? Can he then go through the standard payment procedure?

Yes manually. It is just a duplication so you would have to set them as “incomplete” so they are not marked as paid and then send them a registration email (we have a button to send that). The default email has a link to the payment page where the user can go and pay.

Also: when the admin cancels an attendee, can the payment be refunded sort-of smoothly? Or is it completely manual, outside the scope of eventespresso?

Unfortunately, refunds need to be handled via the payment processor, Event Espresso doe not handle this.

The support post ‘Waiting lists – please clarify’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Considering Event Espresso for a new project? Tell us more through our contact page.

Status: closed

Updated by  Dean 6 years, 1 month ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Do NOT follow this link or you will be banned from the site!
[for="input_96_5_3"]
[for="input_96_5_3"]
[gravityform id=96 title=false description=false]
  • This field is for validation purposes and should be left unchanged.
[i]
[i]
[gravityform id=69 title=false description=false]
  • This field is for validation purposes and should be left unchanged.