Elena Rodriguez
Updated: 2026-05-19
For airlines and terminal service teams, the true high-pressure windows aren't during "normal operations," but during three specific moments: delays and rebooking, gate changes, and Emergency Alerts triggered by weather or traffic control. At these times, your biggest fear isn't that the message won't be sent, but that passengers "never saw it" or saw it too late, leading to queues, complaints, missed flights, and a meltdown of on-site services.
The reality is: a massive number of mainland travelers may be unwilling or unable to immediately download your App upon arrival. So, how do you achieve usable, controllable, and actionable reach under a "no-download" premise?
This guide focuses on a viable path: leveraging the message card capabilities of HarmonyOS Meta Services, combined with LBS (Location-Based Services) and delivery requirements of Millisecond Latency, to build a practical framework for passenger experience and terminal services.
1. The High-Pressure Scenario: A 1-Minute Delay Means Queues and Complaints
In the airline/terminal scenario, notifications generally serve three tasks:
- Emergency Alerts: Gate changes, flight cancellations, temporary security diversions.
- Passenger Guidance: Check-in reminders, boarding times, baggage carousels.
- On-site Coordination: Diversion strategies, service desk routing.
Once delivery is delayed or lost, the consequences are passengers missing critical actions, escalating on-site pressure, and soaring service costs. Therefore, airlines need to deliver actionable card information at the right time and the right place.
2. Why "No Download" is Critical: Passengers Aren't Always in Your App
Your passengers might be flying only once, unwilling to download the App, or too anxious on-site to complete downloads and registration. This means: if you rely solely on in-App reach, the coverage of Emergency Alerts will inherently fall short.
3. Practical Framework: Using Meta Services Cards to Turn "Notices" into "Actionable Commands"
1) Minimize Card Information: One card solves one action
Risk: Treating the card like a "bulletin board."
Measure: Each card carries only one clear action, e.g., which gate to go to, when boarding starts, or the next step for rebooking.
2) Millisecond Latency: Treat delay as a service risk, not a technical metric
In scenarios of delays and gate changes, the value of the message is highly time-sensitive. Establish a "time window" and "expiration strategy" to prevent displaying outdated information.
3) LBS: Use Location-Based Services to make reach "Right beside you"
The value of LBS is not "tracking," but "reducing comprehension costs." Layer scenarios using LBS (e.g., push security guidance to those arrived at the airport).
4. Execution Checklist: Aligning CDO, Passenger Experience, and Terminal Services
- Define grading and trigger conditions for Emergency Alerts.
- Map out 3 core passenger paths: Arrival → Check-in → Boarding.
- Design message card templates: One card, one action, one time window.
- Define LBS rules: Which scenarios can push, which must be suppressed.
- Conduct a drill: The full process of a gate change + delay/rebooking.
5. Learn More (Transportation Exclusive)
If you are evaluating "no-download reach" and Meta Services message card implementation, visit:
Explore HK Transport Push Solutions
