The problem
On a conference with heavy air travel, on-site logistics depend on knowing when people actually land: airport transfers, badge-printing waves, session assignments timed around arrival. That data usually lives in a separate travel system, cut off from the registration record staff are actually working from.
The approach / solution
- Built a flight-sync feature that pulls attendee flight itinerary data into the same registration record used everywhere else in this client’s account.
- Added a flight-picker interface for staff or attendees to select and confirm the correct flight segment when a sync doesn’t resolve cleanly on its own.
- Logged every sync run, so a discrepancy in someone’s travel data can be traced back to when and how the record changed.
Outcome / result
Flight sync runs in production for this client’s events, with itinerary data flowing into the same record the account’s wallet-pass and messaging tools also read from.
Why it matters for enterprise event-tech
Transfers, badges, and session logistics all run smoother when arrival data is already sitting on the attendee’s record. For a heavy-travel conference, that’s planning around real arrival times instead of a spreadsheet someone has to cross-reference by hand.
