Practical customer feedback guide
Design a terminal touchpoint map that operations can use
An airport terminal touchpoint map turns a set of feedback devices into a defined operating plan. For each point, record the terminal stage, exact area, responsible owner, safe pause condition, alternative channel, and question the signal is meant to inform. ThumbsUp supplies device, location, and time context for authorized managers; the airport's own map, approvals, and operational systems remain the source for the wider terminal plan.
For Airport terminal-operations or passenger-experience program manager coordinating facilities, security, accessibility, concessions, and service owners.
Decision frame
Start with one physical service moment.
ThumbsUp helps an authorized team review a configured location and time signal. The setup still needs a site test for distance, lighting, reach, accessibility, privacy, and safe use.
Ask the question that matters to your team
Authorized managers can create or change the short question shown on assigned feedback devices. After Question Mode is enabled on those devices, customers answer the active question with a supported hand gesture—for example, “How good was the cleaning service?”—so each location can collect a signal about the service moment it wants to improve.
Map a moment, not just a pin on a floor plan
A useful point has a passenger moment and an operational owner, not only a coordinate. “Terminal 1” is too broad for a review; “Terminal 1 departures, after security exit, beside the wayfinding decision point” tells the team what the signal represents and where to start looking.
Build the map around fixed points where a passenger can pause safely. Include public and controlled-area boundaries, accessibility routes, luggage space, sight lines, power and connectivity, cleaning access, and the airport-approved alternative for people who do not participate.
- Give every point a stable name that matches the physical sign or asset record.
- Record the journey stage without implying that the device links a person across stages.
- Name the owner of the surrounding service and the person who receives a follow-up.
- Mark points that are unsuitable during busy periods or require a temporary operating rule.
| Map field | Illustrative value | Why it matters |
|---|---|---|
| Point name | T1 Departures / post-security transition / north exit | Prevents results from different gates or exits being mixed |
| Represented moment | Passenger orientation after screening | Defines the question before a result is interpreted |
| Operational owner | Terminal operations with wayfinding liaison | Gives a pattern a destination for investigation |
| Alternative channel | Airport assistance desk or established survey route | Keeps gesture participation optional and inclusive |
Use a consistent airport touchpoint vocabulary
Airports contain overlapping responsibilities: the airport operator may own the terminal environment, while airlines, security authorities, concessionaires, cleaners, border agencies, and transport providers own other parts of the journey. A map should preserve those boundaries rather than turn every passenger issue into an airport-owned score.
Use a small vocabulary that the operations team will actually maintain. For example, separate departures and arrivals, public and controlled areas, service stage, terminal or concourse, exact point, and owner. Do not create a separate page or device label for every synonym; the purpose of the map is clarity and repeatable review.
- Keep airport-operated touchpoints distinct from carrier-operated ground services.
- Use the same terminal, concourse, stage, and owner names in the map and dashboard labels.
- Document a boundary handoff when a point is near a shared desk or contracted service.
- Review the map after construction, route changes, ownership changes, or device relocation.
| Stage label | Example airport question | Keep outside this label |
|---|---|---|
| Post-security transition | Can a passenger orient and regroup after the controlled process? | The security decision or screening result |
| Arrivals and baggage hall | Is the airport-owned transition out of baggage claim clear? | Bag tracing or airline case resolution |
| Public restroom exit | Was the public facility experience suitable at this point? | Automatic cleanliness or compliance certification |
Turn the map into a review workflow
The map should answer what happens after a signal arrives. Authorized managers can filter or review the device and time context, then take the result to the owner named in the map. The owner checks the airport's existing observations, logs, complaints, inspections, or stakeholder records and records the next action.
Illustrative example: a terminal map shows two post-security points with different owners. A lower signal at one point sends the weekly review to terminal operations and wayfinding; a lower restroom-exit signal sends it to facilities. The separation prevents a broad “airport score” from hiding two unrelated questions.
- Define a review cadence that fits the airport's operating rhythm; do not promise a response time the airport has not agreed to.
- Compare points only when the represented moment and conditions are sufficiently similar.
- Capture the observation, action, and owner outside or alongside the airport's normal operating record.
- Retire or relabel a point when its physical context or owner changes.
Start with a map the airport can govern
A pilot does not need every terminal point on day one. Start with a small set of approved points whose passenger moment is clear and whose owners will review the signal. Test the interaction with real routes, lighting, luggage, accessibility needs, and busy periods before repeating the pattern elsewhere.
ThumbsUp can be part of this map as a point-of-experience signal. It does not provide a GIS, asset-management, flight-operations, or passenger-identity layer in this content contract. If the airport already has a facilities or terminal map, mirror its stable naming in the feedback configuration and keep the authoritative spatial record where the airport manages it.
- Approve the map owner and change process before adding devices.
- Use a placement checklist for safe pause, route clearance, accessibility, privacy, power, and connectivity.
- Define the alternative feedback path for each point.
- Review whether the data answers the chosen operational question before expanding the footprint.
Questions operators ask
Design a terminal touchpoint map that operations can use questions, answered clearly.
What is an airport terminal touchpoint map?
It is an operating map that connects a fixed passenger moment to its terminal area, device label, responsible owner, safe pause condition, alternative channel, and review question. It is more useful than a list of device locations without ownership or context.
Can ThumbsUp integrate with our airport GIS or asset system?
This page does not claim a GIS or asset-system integration. An airport can keep its authoritative map in its existing system and use matching, stable names for ThumbsUp device and location configuration, subject to the actual technical scope agreed for a deployment.
Does a touchpoint map track a passenger through the airport?
No. It organizes separate fixed points for operational review. A ThumbsUp point signal should not be presented as an individual journey trace or as proof that the same passenger interacted at multiple locations.
How many airport touchpoints should a pilot include?
There is no universal number. Begin with a small set of approved points whose interaction is safe, whose question is clear, and whose owners agree to review the signal. Expand only after the airport has tested placement and governance locally.
Continue the research
Plan the right feedback point with ThumbsUp.
Bring the service journey, site constraints, and reporting questions. The contact form can help define what a responsible pilot should test before launch.
Book an airport terminal-touchpoint demo