Techbanq

Aviation · passenger experience

Terminal technology should remove effort, not relocate it

A kiosk that turns one trained agent’s task into ten confused passengers’ tasks has not automated anything; it has outsourced the work to the customer. The test we apply to every passenger-facing investment is whether total effort in the terminal actually falls — and for a Gulf airport, whether it falls for the Arabic-speaking passenger first, not last.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
Head of CX, Head of Digital, COO
Decision
Invest in passenger-facing technology that measurably reduces effort in the terminal rather than shifting it onto the passenger

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The journey

The moments where terminal technology touches a traveller under stress

A passenger in a terminal is often tired, late or in an unfamiliar country, which is the state every touchpoint should be designed for. Each stage shows what good technology does at that moment and which systems it needs behind it.

01

Finding the way in

The passenger arrives at a large terminal looking for the right entrance, counter or kiosk, possibly reading their second language.

Wayfinding that agrees with itself — signage, screens and mobile guidance drawing from one source of truth, in Arabic and English of equal quality, so the passenger is never told two different things.

  • Wayfinding content
  • FIDS
  • Mobile
02

The self-service decision

The passenger chooses, or is steered, between a kiosk and a staffed counter.

Self-service that completes the common cases quickly and hands the hard ones to a person without restarting — with the staffed option visible and unashamed, because a forced kiosk queue is a queue plus resentment.

  • Kiosks
  • PSS
  • Queue management
03

Waiting without information

The passenger stands in a security or immigration queue with no idea how long it will take.

Anonymous flow measurement that feeds honest waiting-time estimates to screens and staff, and warns operations early enough to open capacity before the hall fills.

  • Queue analytics
  • Resource management
04

The change of plan

A gate moves or a flight delays while the passenger is eating, praying or asleep in a lounge.

Notifications that reach the passenger in their own language on their own device, consistent with every screen — because a gate change that reaches the screens but not the person is information the passenger paid for and did not receive.

  • Notifications
  • FIDS
  • AODB feed

Language

What Arabic-first design changes inside a terminal interface

Most bilingual terminal interfaces are designed in English and translated afterwards, and it shows in ways an Arabic-reading passenger feels immediately: layouts that break when the text runs right to left, truncated labels because the translation was fitted into a box sized for English, mixed-direction strings where a flight number collides with an Arabic sentence, and a tone of translated formality no one would write naturally. For an airport in Saudi Arabia, where Arabic is the first language of most passengers, this quietly makes the majority experience the second-class one.

Arabic-first inverts the order: the interface is designed right-to-left with Arabic copy written natively, and the English version derives from it. Layout, type sizes, line lengths and iconography are proven against Arabic before anything else, numbers and codes are handled deliberately inside RTL text, and the voice is written by someone who writes Arabic rather than converts it. The English experience loses nothing — Latin text sits comfortably in a layout designed for Arabic far more often than the reverse — and the majority of passengers gain an interface that reads as if it were made for them, because it was.

The false economy

Four ways airport self-service quietly hands the work to the passenger

Each of these looks like automation on the business case and feels like unpaid labour in the terminal. Naming them is how an investment avoids them.

  1. 01

    The kiosk that needs a helper

    If a bank of kiosks requires roaming staff to shepherd passengers through it, the counter task has not been automated — it has been split into a machine and a person, and the queue has moved, not gone.

  2. 02

    The dead end that restarts the journey

    Self-service that fails on the hard case and sends the passenger to a counter to start again has charged them twice for one task. A handover must carry everything already entered with it.

  3. 03

    The interface that assumes the confident traveller

    Flows designed around the frequent flyer punish the first-time traveller, the elderly passenger and the family with children — the very people for whom the terminal is most stressful and the staffed alternative most needed.

  4. 04

    The metric that hides the shift

    Measuring agent transactions saved, without measuring passenger time spent, makes every one of the failures above look like a success. The honest metric is total effort in the terminal, on both sides of the counter.

Measurement and privacy

How a terminal measures its crowds without watching its people

Queue and flow analytics need to know how many, how fast and where — none of which requires knowing who. That distinction is an engineering choice, and we make it deliberately.

  1. 01

    Counting, not identifying

    Flow measurement is built on anonymous techniques — counting sensors, aggregate signals — chosen so the system cannot single out an individual even if asked to, which is a stronger guarantee than a policy promising it will not.

  2. 02

    Retention set by the operational question

    Flow data is kept at the aggregation and for the duration the operational question needs — capacity planning needs patterns, not journeys — so the dataset that could become a surveillance record is never accumulated in the first place.

  3. 03

    Personal data stays where the law puts it

    Where a touchpoint does handle personal data — a booking lookup, a notification opt-in — it is processed under the operator’s privacy governance and the applicable data protection law, consented, minimised and separate from the anonymous flow layer.

The privacy policy, the lawful basis and anything requiring the authority’s or the regulator’s approval belong to the operator; we engineer the touchpoints and the measurement so the technology enforces those commitments instead of merely coexisting with them.

Common questions

What buyers ask

Does measuring airport queues require identifying individual passengers?+

No. The operational questions — how long is the wait, where is the crowd building, when should another lane open — are answered by counts, densities and movement rates, all measurable anonymously with counting sensors and aggregate signals. Identification-based tracking adds operational value only in narrow cases and adds privacy risk in all of them, so our default is architectures that cannot identify a person rather than ones that promise not to. Where an airport does need identity — at border control, for example — that belongs to the government systems built and governed for it, not to the queue analytics.

What makes a terminal interface genuinely Arabic-first rather than translated?+

The direction of derivation. In an Arabic-first interface the layout is designed right-to-left, the copy is written natively in Arabic by someone who writes it well, the type, line lengths and truncation rules are proven against Arabic text, and mixed content — flight numbers, gate codes, names — is handled deliberately inside RTL strings. The English version is then derived from that design. You can test any interface in a minute: put the Arabic and English versions of the same screen side by side and ask which one looks designed and which one looks fitted. In a translated-last interface the answer is immediate, and so is the message it sends to the majority of your passengers.

How should an airport serve passengers who cannot or will not use self-service?+

By keeping the staffed path visible, adequate and free of penalty — and designing the technology to strengthen it rather than starve it. Some passengers cannot use a kiosk for reasons of ability, language or the complexity of their case; others simply prefer a person, and a terminal that punishes that preference with a hidden desk and a longer wait has made its service worse in the name of improving it. The productive pattern is self-service that genuinely absorbs the simple cases, which shortens the staffed queue for those who need it, plus handovers that carry context so the agent starts where the kiosk stopped. Accessibility is engineered on both paths, tested with assistive technology and with real passengers rather than signed off from a checklist.

Next step

Start from your terminal

A touchpoint review that walks one passenger journey through your terminal and scores each moment on effort added or removed.

Start from your terminal

What happens next

  1. 1We reply within one business day.
  2. 2A 30-minute scoping call with a senior consultant.
  3. 3A written proposal with scope, team, and timeline.

Or reach us directly

By submitting this form you agree to our Terms of Use and Privacy Policy.