Working With Your Existing Disruption Products
Many airlines already run tooling for parts of a disruption: an automated re-protection engine in their PSS, a compensation module, a passenger notification platform. Nexa does not ask you to replace any of them. Each Nexa capability can lead, follow, or be switched off, per airline, so Nexa fills the gaps — above all passenger care: hotels, meals, ground transport, and the operators who coordinate them.
At a glance
| You already run… | That system decides… | Nexa then… |
|---|---|---|
| Automated re-protection / disruption transfer (in your PSS) | Which flight each passenger is moved to. | Adopts that decision. Nexa's own rebooking engine stays off for your tenant; the new flight drives hotel nights, transport times, and the passenger's itinerary in Nexa. |
| Compensation management | Monetary compensation and entitlements (EU261 and equivalents). | Does care, not compensation. Hotel, meals, and transport are Nexa's; compensation stays in your module. Nexa's prepaid cards are optional — typically used for meals and incidentals. |
| Your own passenger notification platform | How and when passengers are messaged. | Hands off messaging. Nexa emits events (hotel assigned, voucher ready, transport booked, itinerary changed) to your platform, which sends them in your voice. Nexa-originated sends can be switched off per channel. |
Re-protection: Nexa follows your decision
- The new flight arrives through the airline connector — by re-reading the PNR, reading the queue your re-protection places it on, or by push (Partner API).
- It is stored as the re-accommodated segment, separate from the sold itinerary, so "booked on" and "moved to" are never confused (Data requirements § Itinerary segments).
- The stay length is computed from it: the passenger needs a room until their new departure.
- If re-protection later changes the flight, Nexa extends or shortens the stay and reschedules transport. Confirmed rooms are never disrupted by a later update.
- For passengers your engine could not re-protect, operators see them flagged as such. You decide whether Nexa's rebooking engine may propose options for them, or whether they stay with your agents.
Compensation: Nexa cares, you compensate
Nexa's scope is the passenger's physical care during the disruption and its audit trail — the evidence that care was provided, when, and at what cost. Compensation calculation, eligibility, and payment remain in your compensation module. Nexa can send that module a per-passenger care summary (services, nights, cost) through outbound events.
Notifications: your platform, Nexa's content
Two modes, per airline and per channel:
| Mode | Who sends | What Nexa does |
|---|---|---|
| Delegated | Your notification platform | Emits signed outbound webhooks carrying everything the message needs: hotel, address, check-in window, voucher link, transport pickup. |
| Nexa-sent | Nexa (SMS, email, messaging apps) | Sends in the passenger's language, under your brand. |
A common split: your platform sends the flight-change messages it already owns; Nexa's content (hotel voucher, transport pickup, the passenger self-service link) is either delegated to your platform or sent by Nexa on those channels only.
Where to next
- Amadeus Altéa connector — APIs and volumes for Altéa-hosted airlines.
- Airline systems (PSS / DCS)
- Webhooks — the outbound event contract.