Illustrative cabin interaction. Tap the passenger call button to hear the chime and see what the call does—and does not—communicate.
A call needs context
DingDong
Human-Centered Approach to In-Flight Assistance
The light is on.
What does the passenger need?
A chime tells the crew that someone has called. It leaves the request, urgency and next useful action unresolved.
THE IDEAMake the request
Make the request
part of the call.
How might we make calls carry context of a passenger's request or priority?
DingDong explores a passenger interface and shared crew dashboard for cabin help requests. The research asks whether that additional context supports coordination and passenger experience, and what new workload it might introduce.
THE ENVIRONMENTFrom the passenger seat
From the passenger seat
to the crew's shared view.
The proposed simulation pairs an in-flight entertainment interface with a crew dashboard. A conventional passenger call button provides the comparison, while request handling is initially scripted or operated by a researcher.
The website preview starts from the passenger's seat. Tap the call button: the chime sounds, the call is active and the crew is notified, but the request remains unknown. That missing context is the starting point for the design.
Passenger request
Explore how someone expresses what they need without making asking for help difficult.
Shared crew context
Make request information available to support coordination and ownership.
A call-button comparison
Compare the added interaction with the simplicity of a conventional cabin call.
RESEARCH VARIABLESDoes more context
Does more context
make help easier?
Candidate measures connect the passenger interaction with what the crew must understand and coordinate.
THE QUESTION
The crew needs more than a seat number.
Compare a contextual request interface with a call button to examine how clearly the request and its priority are communicated.
- What changes
- Passenger request interface and scenario demands
- What we observe
- Request interpretation, clarification and response timing
Does context help the crew understand the request earlier?
Trace the request
across the cabin.
Request events
Follow the request from its creation through clarification and response.
Crew activity
Observe coordination and workload around the information available to the team.
Passenger perspective
Evaluate how the interaction feels to the person asking for assistance.
DingDong currently has a research plan. The website cabin is an illustrative interaction; it sends no real crew notification. The proposed study uses simulated interfaces and scripted behaviour, not an aircraft-integrated AI service.
A chime is a start.
What should come with it?
DingDong asks how a small interaction can carry useful context between a passenger and the people ready to help.
Talk to the lab Next project: Meet Herror