Graduation operation · Tickets
Graduates have a ticket quota, invite family, want to buy more, and someone has to keep track of all of it without a paper list. The tickets module handles the quota per graduate, sales of extra tickets, guest registration, the waitlist and validation at the entrance, including facial identification.
The problem and the fix
If any of these situations sounds familiar, it is because they happen in almost every graduation company, until the right system comes in.
The ticket quota turns into an argument because nobody knows how many tickets each graduate has already taken.
A per-graduate quota controlled by the system, with the balance visible in the app and issuing blocked above the limit.
Extra tickets are sold over WhatsApp, with loose payment receipts and no seat control.
Extra tickets sold in the app, paid on the spot and issued automatically, within the event's capacity.
At the door, names are checked against a printed list and the line doesn't move.
Validation by scan in seconds, with optional facial identification and an entry log.
A graduate drops out and their ticket sits unused while people are waiting in line.
A waitlist with automatic invitations when a seat opens up, with a deadline to accept.
Nobody knows how many guests will actually show up.
A live dashboard of issued, confirmed and present guests, with comparisons across events.
In practice
Everyday situations at graduation companies, from the problem to the result, using the modules on this page.
A graduate canceled two tickets a week before the ball, and the company had no process to reuse them.
The waitlist kicked in automatically, inviting the next people in line with a deadline to accept.
Both seats were filled the same day, paid in the app, without anyone calling anyone.
One event required holder identification to prevent tickets from being passed on.
The company turned on mandatory facial identification: each holder registered a photo and validation checked it at the entrance.
Entry was fast and ticket passing stopped, with no ID checks at the door.
The organizers didn't know who the guests were until the day of the event.
Graduates began registering each guest in the app, linked to the issued ticket.
The entrance staff worked with complete information, and the organizers knew the expected attendance ahead of time.
How it works
Every step is a real module, and what comes out of one goes into the next without anyone typing it again.
Module by module
6 modules and 31 features on this page, all running on the same class, graduate and event records.
How many tickets each graduate has, and how they use them.
Anyone who wants more tickets buys them in the app, within capacity.
Who will use each ticket, registered before they reach the door.
The leftover seat finds whoever was waiting.
The door moving at the pace of the line.
Who can do what, and what happened in the end.
Compare the modules and choose the setup that fits your operation.