🐛Attendees placing an order for multiple tickets under their own name only recieve one ticket email

[phtaylor]

Describe the bug We recently hosted an event using Hi.Events, and this bug was a plague. I have reproed this several times on various deployments of Hi.Events, so I am sure its current.

Let me explain... An attendee may be purchasing tickets for themselves and several friends. They go through the ticket purchase process, but they use thier own email for all the different tickets. They probably plan to forward the tickets to friends later... This happens all the time. People are in a hurry, maybe have been delegated the task of aquiring tickets for a group and don't have the details for the group members.

I just reproed again the issue.

I ordered 7 tickets for myself. See the emails I recieved.

The order cofirmation email. *Note: there is a link in that email to view all the tickets.

There is an email for the first ticket, but no other tickets. The only way to get to the other 6 tickets is via the link in the 'Order Confirmation' email.

guests were constantly mailing us to ask where the other tickets were, and if I manually resent the ticket emails, they were recieved.

To Reproduce Steps to reproduce the behavior:

1. Purchase multiple tickets under the same email address
2. See only 1 ticket email revieved.

Expected behavior A clear and concise description of what you expected to happen.

I would expect one email for each ticket, that can then be manually forwarded to other people.

Hi.Events Version and platform Please state the version of Hi.Events you are using and what platform it is hosted on. Local, Docker etc.

Tested on both our own deployment of Hi.Events and the SAAS version.

Additional context Add any other context about the problem here.

[daveearley]

Thanks for reporting this. The behaviour you saw is actually by design. When someone buys multiple tickets using the same email address, Hi.Events only sends:

One order confirmation email with a link to all tickets

One ticket email for the first ticket

This was done to avoid flooding people with several nearly identical emails when they intentionally use the same email for every attendee.

That said, your feedback is helpful, and this situation does come up often at real events. I’d like to understand what you’d prefer to happen.

Would you want:

1. An email for every ticket

2. A single email that includes all tickets

3. The current behaviour, but with a setting to choose which approach to use

4. Something else

Let me know what you think is the most practical approach.

[phtaylor]

the scenario where a person buys multiple tickets using their own email address, means they plan to re-distribute those tickets to frinds themselves later. We had this many many times.

1. An email for every ticket

Give control to the user to redistribute thier tickets.

2. A single email that includes all tickets

This makes redistribution diffcult. I believe this option only cause issues. e.g. People arriving at the event without tickets because thier friends with the tickets is late. Teams doing checkin need to provide tech support to guests. Also, I beleive a way to transfer tickets to other email adresses should be available (maybe because of resale), and that link to re-assign a ticket to another user would be in that email associated with the ticket.

3. The current behaviour, but with a setting to choose which approach to use

Lets say the purchaser picks option 2. but then realizes they want to send the tickets to guests. They closed that door, maybe without realizing.

As you can see, my preference is always send all ticket emails to the provided email address and let the purchaser manage re-distirbution. The current behavior is the worst of both cases, as they don't even know why they didn't see other ticket emails.

[ethbkk1]

Perhaps the single ticket with a link would be good BUT the page with the list of tickets has a button to forward tickets to users with a ticket ID.

I think this would allow the organizer to manage who the tickets are sent to in the Hi.events UI. If there’s a typo in the address or it isn’t received, they could correct it and resend.