🌟Generate Ticket only after email verification
Is your feature request related to a problem? Please describe. We have lots of users who enter a wrong email address during the checkout and therefore don't receive the tickets via email but see them only after checkout and then close the browser window. This produces a high load on phone calls, where we need to find the tickets in the system, change the email address, and resend the tickets.
Describe the solution you'd like We'd like to have a workflow where the buyer needs to verify their email address, e.g. by clicking a link sent via email, before getting redirected to the payment methods. The checkout process should continue only after being verified.
We thought of a screen/step between https://foo.bar/checkout/XXX//details and https://foo.bar/checkout/XXX//payment with something like: "We sent a verification to >>your address<<. Please confirm within the next >>timer<< minutes."
Additional context We found that the session of a checkout is 15 minutes. However, it's not possible to continue the checkout from another device. So if a user verifies the email address on another device, the checkout can't be continued on that "new" device.
Hi @stilnox255,
I'd be reluctant to include any extra steps in the checkout process as any additional friction can lead to an increase in abandoned carts. I
However, I agree it's not ideal that the user can't change their email. A possible solution is to allow them to correct their email on the order confirmation page.
Hi @daveearley,
I wouldn't go so far into solution space just yet to assume there has to be an extra forced step for everyone, impacting their customer conversion. Let me first reinforce the point that my friend made: We are having significant support issues with people entering wrong mail addresses on accident or purpose, and we would like to have a technical flow that addresses this. Let me also add that this is about people losing access to their tickets (incl. their checkout link), so not only wouldn't changing mail addresses not resolve our issue, but I would also consider it a security risk making it harder to validate legitimate ticket owners.
The good news is: We are not beggars for development capacity but capable and willing to implement and deliver the features by ourselves, but would much prefer do so in alignment with you, hoping that it could be made available to the community.
In terms of a more "ecosystem-friendly" solution that addresses your concerns, I was thinking of an opt-in "email validation" feature that admins can turn on if they are willing to add a checkout flow step. What we need from you is input on how we could best implement this in terms of best practices Hi.Events already uses.