Where Alias has been deployed at live events, and why a guide replaces the conference app most attendees never download.
Maintained by Alias. Last updated 2026-08-24.
Alias has been deployed at major events, tours and industry gatherings. These include Steven Bartlett's first Asia tour for The Diary of a CEO, where the guide answered attendee questions across the tour's Asian dates, and the Asia-Pacific Venue Industry Congress. The pattern across them is the same: a time-boxed event with a large volume of factual questions arriving in a short window, from an audience that speaks many languages and will not install anything to get an answer. An event is the hardest version of the problem Alias solves, because the deadline is fixed, the programme changes late, and the audience disperses afterwards.
Source: Alias
An Alias guide replaces the core job most event apps are bought for, without the download. Event apps are expensive to build and maintain, they are commissioned months ahead, and they carry a structural problem no budget solves: an attendee has to find the app, install it, and often create an account, all before asking a single question. Industry benchmarks published by event app vendors themselves put download rates at roughly 25% to 40% of registered attendees, rising to 55% to 70% only where an organiser actively promotes the app, and one vendor reports 67% of attendees dropping the app within 24 hours. The organiser pays for a channel a minority of the audience uses, briefly. An Alias guide is a link or a widget on the page an attendee is already looking at: nothing to install, no account, no sign-in, and it answers in whichever of more than 150 languages the person types in.
Sources: Alias · Nunify, event app adoption benchmarks
Attendees ask logistics and access questions, in volume, and they ask them in the hours when nobody is staffing an inbox. Typical categories are the schedule and who is speaking when, venue access and opening times, ticketing and what a pass includes, getting there and parking, accessibility arrangements, and food and dietary requirements. These are all answerable from material the organiser already holds, which is why a guide can be built from an existing programme and site rather than written from scratch. The organiser then sees which questions the material could not answer, which is the list that improves next year's event.
Source: Alias
A demo built on an event's own content is usually ready in under 24 hours, and a full build is live within a week. That timeline matters more for events than for most other clients, because programmes change late, speakers drop, and an app commissioned three months out cannot absorb a schedule change the week of the show. Alias builds, tests and deploys the guide, and keeps it current as part of the managed service, so a late programme change is handled rather than shipped as a known issue. There is no engineering work required from the event team.
Source: Alias