Running AWS Community Day Davao 2026 with Offline Check-in and Flexible Ticketing
A real event story by AWS User Group Davao
Intermittent venue wifi never stalled the door, so a large participant list kept moving through check-in.
Separate ticket types and coupons per sales campaign, with each type visible at the door so inclusions went to the right people.
Requests and bug reports were answered within the day through the build-up to the event.
Introduction
“Amazing ticket platform with a great team behind it. Thank you for working with us, and we hope to use Typid for future events.”
We're AWS User Group Davao, the community behind AWS Community Day Davao 2026. Community events live and die by the details: how easily people can get a ticket, and how quickly they can get through the door once they arrive.
This is what our ticketing looked like before Typid, what pushed us to change, and how AWS Community Day Davao 2026 actually ran.
Before Typid
1. How We Ran Registrations
Before Typid, we managed event registrations and ticketing through Ticketnation, or through a combination of Google Forms and Google Sheets. It worked well enough to get by, but nothing about it was joined up. The ticket list, the payments, and the door were three separate things we had to reconcile ourselves.
2. The Biggest Challenges With That Process
Four things came up again and again:
- Processing refunds
- Slow response time
- Lots of bugs
- A tedious process overall
3. What Made Us Decide to Try Typid
They built their platform for the community, and that seemed really promising. Since our last ticket platform didn't yield a great experience for us, we wanted to try something new, and we found Typid.
4. We Couldn't Risk Check-in Going Down
Venue wifi is never guaranteed. With the number of participants we expected, we couldn't afford issues at check-in. A connection drop at the door would have meant a queue we had no way to clear.
The Solution: Typid for Ticketing and Check-in
1. Setup Was Straightforward
Setting up our event in Typid was super easy. More importantly, when we needed anything, the team would respond within the day, so nothing sat blocked for long.
2. Tickets and Coupons Per Campaign
The feature that helped us the most was creating tickets and coupons. We could set up different tickets per type, or even for different sales campaigns, which gave us room to run early-bird and partner pricing without maintaining a separate spreadsheet for each.
That carried through to the door. When we scanned someone in, we could see their ticket type straight away, so we knew exactly which inclusions to hand them.
3. Offline Check-in Saved the Door
The moment Typid made a real difference was offline check-in. The wifi at the venue was intermittent, and with the number of participants we had, any issue at check-in would have been a problem. Offline check-in meant the door kept moving regardless of the connection.
For attendees it stayed very simple: they showed their QR code, and we checked them in.
4. Built for Community Events
What we liked most was the fast response time (both on the platform and from the team) and how easy it was to use for us and for participants. We could tell the platform was made for community events by small details like offline check-in, the planning checklist, requesting withdrawals, and coupons.
Results
Typid helped AWS Community Day Davao 2026 run with less overhead and fewer things to worry about on the day. For our team, the biggest wins were:
- Faster registration process
- Faster attendee check-in
- Better attendee management
- Reduced manual work
- Easier ticketing
- Better event organization overall
Instead of maintaining forms and sheets and chasing support, we could put that time back into the community day itself.
Final Thoughts from AWS User Group Davao
Typid is a great platform for community events. It's easy to use for organizers and participants, we can choose how tickets are displayed, payment options, create coupons, track inventory, manage attendees, and more. What made the experience better was how responsive their team was to any requests or bugs we reported, to ensure the experience was seamless.
There are still things we think could be improved. The event dashboard participants use to buy tickets could have more customization, especially in showing the ticket description and inclusions. Being able to edit the confirmation email content would have helped too. Our event ran across two days, and participants got confused by the dates on the emails.
Even so, it was an amazing ticket platform with a great team behind it. Thank you for working with us. We hope to use Typid for future events.
