How it works
Connect, ask, answer, record.
The four steps
01
Connect
A visitor scans a code at the entrance or opens the app. The venue decides which routes it offers.
An entrance with a code sign beside the door. 02
Ask
They ask the building whatever they came in wanting to know, in their own words, by typing or by speaking.
Interface design with example data. These are not results from a live site. 03
Answer
The building answers from the live occupancy and queue data, the operational updates staff entered that day, and the static knowledge base it holds about itself.
04
Record
The question is stored as a structured record, timestamped and located by zone. The operator owns it.
- Question
- Is there a pharmacy here?
- Zone
- North entrance
- Time
- 12:40
- Answered from
- Knowledge base
- Flag
- Asked for, not there
One of 2,410 times it was asked this quarter. Interface design with example data. These are not results from a live site.
Sources
What the building answers from
Three sources, and nothing else.
Sensors
Ceiling mounted people counting sensors report how many people are in each zone and how long the queue is. Queue length and free seating come from the sensors, not from staff.
Staff input
Staff enter what has changed that day: a menu item that has run out, a room closed at short notice, how many tills are open. The building answers with that from the moment it is entered.
Knowledge base
A static description of the building: what is where, when it opens, who it is for and what is allowed. It is set up once and changed when the building changes.
Access
Accessibility
Because the whole thing works by asking and listening, people who are blind or partially sighted can move through an unfamiliar building without needing to read a sign or find a screen.