Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: create unpersonalized tickets - is it possible? #1448

Open
titi1125 opened this issue Jan 23, 2025 · 5 comments
Open

Question: create unpersonalized tickets - is it possible? #1448

titi1125 opened this issue Jan 23, 2025 · 5 comments
Labels

Comments

@titi1125
Copy link

I can't figure out if it's possible to create unpersonalized tickets? In other words, tickets with a QR code for the event, but without the names of the people. So that the ticket can simply be passed on.

@syjer syjer added the question label Jan 23, 2025
@syjer
Copy link
Member

syjer commented Jan 23, 2025

hi @titi1125 , currently not. A reservation and a ticket must have a "owner" (with firstname/lastname and email).

Could you specify your use case, as it's not something that we have encountered.

Thank you :)

@titi1125
Copy link
Author

hi @syjer ,
thx for fast replay :)

sure; For example, I would need it for an event where it is not mandatory to provide your first and last name...

  1. Create Ticket Type: Create a ticket type that does not require first and last names. You can make these fields optional, so only the email address is required.

  2. Customize Form Fields: In the ticket settings, you can set the first and last name fields to be "optional" or even remove them entirely if they're not necessary. The email address field should be the only mandatory one.

  3. QR Code Generation: Once the ticket purchase is complete, automatically generate a QR code for the ticket. This QR code can then be sent to the buyer via email or can be accessed directly in the user profile for the event.

  4. Email Verification: To ensure that the ticket buyer is properly identified, you should use the email address as the key identifier. You can also set up an email confirmation to verify the email address before the ticket is issued.

  5. Ticket Transfer (Optional): If you want to allow ticket transfers, you could enable the option for the ticket to be transferred to someone else. In this case, the email address would act as the key for transferring the ticket.

Summary:
-Ticket Type with no first and last name, only email address as a mandatory field.
-Automatic QR code generation after the purchase.
-Email verification to confirm the address.
-Optionally, allow ticket transfer via email address.

@syjer
Copy link
Member

syjer commented Jan 23, 2025

ok I see, an email would still be needed.

@titi1125
Copy link
Author

@syjer ,
what do you think, is it possible to implement this as an option so that you can choose with or without a first and last name?

@syjer
Copy link
Member

syjer commented Jan 24, 2025

It would not be a simple change, it's not on our roadmap but a PR would be appreciated as a starting point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants