Airlines, hotels & operators
Disruption is a communications problem with a deadline.
When a flight cancels or a property oversells, hundreds of people need the same three facts and one decision, simultaneously, and the phone system is the first thing to fail.
An illustrative reference architecture, not a customer
case study. No organisation is named and no deployment is described - this is
what the layers look like for a travel & hospitality organisation,
so you can map it onto your own estate.
Channelswhere the conversation starts
Inbound numberspublished lines
SIP / contact centreexisting estate
Outboundcampaigns and callbacks
In-appbrowser WebRTC
▼
VoiceKernelthe agentic voice layer
Conversationagent, voice, turn taking
Knowledge groundinganswers with citations
Tool callsreads and writes back
Transferto a human, with context
Tenant isolationownership registry
Audit and erasureper call, per mutation
▼
Integrationyour boundary, your rules
REST + typed SDKscoped API keys
Signed webhooksretried, replayable
Live event streamSSE
▼
Travel & Hospitalityyour systems of record
Reservation systembookings, inventory, fares
PMS / CRSproperty and rate availability
Loyaltytier, points, entitlements
Paymentsrefunds and re-fares
Ops / disruptionschedule changes
Only the bottom layer is specific to travel & hospitality. The
three above it are identical in every deployment, which is the point: the
voice layer does not need to know what industry it is in, only which systems
it is allowed to reach and what it may say.
What it changes
Mechanisms, not projections. Each of these follows from something structural
about the work, so you can check whether it holds for your own queues.
The disruption spike stops being unanswerableOutbound at the scale of the disruption itself, so the airline calls the passenger rather than the other way round.
Rebooking happens while inventory still existsSpeed is the whole game; the seats go to whoever is contacted first, and contact is the constraint.
Every language on every shiftMultilingual coverage without recruiting for it, which matters most at 2am in a foreign airport.
Fare rules applied consistentlyNo discretionary variation under pressure, and every quote is recorded.
What the agent actually does
Disruption rebookingCall every affected passenger with the options that actually exist, take the choice, and rebook in the same conversation.
Booking changes and cancellationsApply the fare rules honestly, quote the fee before changing anything, and confirm by message.
Pre-arrival and conciergeConfirm arrival time, capture requests, and route the ones that need a person to a person.
What keeps it deployable
Fare and fee transparencyThe agent states the cost before it commits the change, and the utterance is retained.
Payment separationRe-fares route to your existing payment flow; the agent never handles the card.
Consent for recordingCaptured per call and stored before anything else.
Disruption volume arrives in minutes and decays in hours, which is precisely the shape no staffing model can meet.
NextRead the source
Everything above is in the open-source Community edition. Nothing on
this page needs a licence.
NextRun it yourself
Point it at your provider account and put one queue through it before
you talk to anybody.
NextThen buy the guarantees
An Enterprise agreement adds the SLA and the
support contract when it carries real volume.