Loading / Chargement
Passenger Operations Orchestration
PaxRelay connects your transportation systems, turns service changes into configurable workflows, and helps your teams keep passengers informed.
Operational event
PX204 · YUL → YVO
Departure +75 min
Source
Normalize
Decide
Communicate
Workflow outcome
Operations approval required
EN 31 · FR 16
PX204 is now expected to depart at 15:45. We will keep you informed if the timing changes.
The operational gap
When a departure slips or a sailing is cancelled, the information usually exists somewhere — in a scheduling tool, an operations inbox, a shared sheet. Turning it into a consistent response across teams and languages is the real work.
That space between a change and a consistent response is where connections get missed and passengers are left guessing. PaxRelay is built to close it.
Inside the operational work
A focused operating view keeps the source change, passenger impact, workflow state and prepared communication in one traceable record.
Active events
03PX204
Approval+75 min · 47 passengers
Selected event
CH407
RecoveryCancelled · 28 passengers
PX118
SentGate B4 · 83 passengers
Event record
Action path
Prepared communication
Your flight PX204 is now expected to depart at 15:45. We will keep you informed of any further changes.
Review this same path using a real change from your operation.
Map my workflowHow it works
Receive operational data from the systems you already run — by API, webhook, scheduled feed or file.
Different systems describe the same event differently. PaxRelay maps them into one consistent operational change.
Rules decide what applies: who is affected, which workflow runs, and whether a person needs to approve it.
The message is prepared for the intended recipients in their language, and the delivery outcome is recorded.
The platform
PaxRelay is organized around what an operation actually needs when something changes — from the first signal to the message a passenger reads.
Connect operational systems
Webhooks, APIs, scheduled feeds, SFTP and files bring operational signals in — without replacing your core systems.
Turn changes into workflows
Rules, conditions, automation, approvals and escalation that reflect how your operation actually works.
Keep passengers informed
Multilingual templates across email and SMS, with delivery status, versioning and approved content.
Give teams control
Incidents, approvals, exceptions, affected passengers and workflow state in one operational view.
A clear source of truth
A passenger-facing view of current service, with white-label experiences on the roadmap.
Control stays with you
Your team defines each workflow mode and the steps that require human approval.
For routine, low-risk changes, PaxRelay can act without waiting.
A person reviews and releases before anything reaches a passenger.
PaxRelay prepares everything; your team sends when it is ready.
Integration-first
PaxRelay is designed to sit alongside the systems you depend on — reservation, scheduling, operational tools — rather than replace them.
Systems send a change as soon as an event is available.
PaxRelay retrieves data on a schedule or on demand.
For established batch exchanges between systems.
CSV and structured files for operational data.
For legacy or proprietary systems.
Designed to work with APIs, webhooks, scheduled feeds, files and legacy integration patterns.
Security by design
Passenger operations data is sensitive. PaxRelay is designed around isolation, least privilege and a clear record of what happened.
Book a working session with our team. We will walk through your systems, a disruption you deal with often, and how a workflow would handle it.