The problem
A university running its own event and conference programs on Swoogo needed three things Swoogo’s stock setup doesn’t hand over: a real way to browse sessions and speakers, a way to catch attendees who register but never actually pick a session, and a way for staff to get bulk registrant data out without opening a support ticket.
The approach / solution
- Built an event-directory widget as a Twig template inside Swoogo, listing sessions and speakers as a browsable directory in place of the platform’s flat default list.
- Built a registration-status check snippet that looks at whether a given attendee has selected any sessions yet. If not, it shows a message — “you are not registered for any sessions yet” — with a link straight to the session planner.
- Built a bulk-registrant CSV export tool inside the same account, so staff can pull the full registrant list to a CSV file on demand rather than requesting one from Swoogo support.
Outcome / result
All three run in production on this client’s Swoogo account. Attendees get a directory worth browsing and a nudge if their schedule is empty; staff get their own data export path.
Why it matters for enterprise event-tech
A conference program lives or dies on details like these. A directory people actually browse, a nudge that catches an empty schedule before the event starts, and export access that doesn’t run through a ticket queue — none of it is glamorous, and all of it is what keeps a real event program self-service instead of dependent on outside support.
