You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a new happy Alf.io user and I have a question. Is it possible to add a custom field to sold tickets from the backoffice after the registration period has ended, but before the event begins, and have that field displayed on the mobile app during check-in?
Here’s the scenario: after the registration period, we have an event with about 100 registered attendees (sold tickets), and we’d like to divide them into 4 groups of 25 people each based on some a posteriori criteria determined in the backoffice. During check-in, we want to quickly direct each attendee to their group. While we could use a printed list to match names, it would be much more convenient if the group information appeared directly on the mobile app screen as soon as the QR code is scanned. This way, the team member using the mobile app would instantly know which group to direct the attendee to.
Hi everyone,
I'm a new happy Alf.io user and I have a question. Is it possible to add a custom field to sold tickets from the backoffice after the registration period has ended, but before the event begins, and have that field displayed on the mobile app during check-in?
Here’s the scenario: after the registration period, we have an event with about 100 registered attendees (sold tickets), and we’d like to divide them into 4 groups of 25 people each based on some a posteriori criteria determined in the backoffice. During check-in, we want to quickly direct each attendee to their group. While we could use a printed list to match names, it would be much more convenient if the group information appeared directly on the mobile app screen as soon as the QR code is scanned. This way, the team member using the mobile app would instantly know which group to direct the attendee to.
Thank you, best regards,
-- Davide
Originally posted by @salvedgms in #1414
The text was updated successfully, but these errors were encountered: