Skip to content
NewPazau Agent 3 is here: Procedures that test themselves before they go live
Airlines & travel

Rebook the whole flight before the storm clears.

Pazau Agent handles involuntary rebooking, refunds, baggage claims and loyalty requests end-to-end, inside Amadeus or Sabre. It applies EU261 and DOT rules the same way on the 40,000th passenger as on the first.

EU261 & DOT rules built inPCI DSS paymentsEU data residencyChat, WhatsApp and voice
Disruption queue · Conversation #9,204,117
WhatsApp · EN
Flight 1182 to Rome was cancelled 3 hours before departure. Do I get anything back?
Pazau Agent
Yes. It was cancelled for a crew shortage, which isn't an extraordinary circumstance, so you're owed €250 under EU261. I can also rebook you on tonight's 19:10 at no cost, or refund the ticket in full. Which would you prefer?
EU261 compensation · Art. 7(1)(a)
€250.00 → Visa ••2291
Eligible
Trace7 steps · exportable
  1. GuardPassport no. + email → redacted before model call
  2. Procedure matchedCancellation < 14 days → EU261 eligibility (v22)
  3. Action · get_bookingPNR 7TQ4MX · LHR→FCO · 1,434 km · Amadeus
  4. Action · get_flight_statusCancelled T−3h · ops code CRW · not extraordinary
  5. Rule applied≤ 1,500 km band → €250 · care owed while waiting
  6. Action · search_flightsSame day · 4 results · 1 same-cabin, $0
  7. Awaiting choiceCompensation queued · refund or rebook offered
1m 48s
median time to rebook a cancelled passenger
10×
normal contact volume absorbed during irregular operations
100%
of refund decisions cite the rule and fare condition applied
45+
languages across chat, WhatsApp and email (30+ on voice)
Top use cases

The six conversations that decide how passengers remember you.

Each one runs as a Procedure written by your team in plain language, with Actions into your reservation, baggage and payment systems. Every decision is traced.

01

Involuntary rebooking

78%
of disruption rebookings resolved by AI at Solstice

Cancellations, misconnects and schedule changes. Pazau finds same-day alternatives on your metal and partners, checks minimum connection times, and reissues the ticket before the passenger reaches the gate.

Procedure · Involuntary change → RebookLive
  1. 1.Look up the PNR with get_booking and the disruption with get_flight_status.
  2. 2.Search same-cabin alternatives on operating and partner carriers with search_flights.
  3. 3.Offer up to three options. Re-check minimum connection time before confirming.
  4. 4.Rebook with rebook_pnr and reissue with reissue_ticket. Fare difference over $150 needs approval: duty manager.
Actionsget_bookingget_flight_statussearch_flightsrebook_pnrreissue_ticket
02

Refund eligibility under EU261 and DOT

0
refunds outside your fare rules in audit

Pazau decides which regime applies, computes compensation by distance band, and issues cash refunds automatically where the US DOT rule requires them, citing the exact rule in the trace.

Procedure · Refund & compensation eligibilityLive
  1. 1.EU departure or EU carrier → EU261. US flight → DOT automatic refund rule.
  2. 2.DOT: refund in cash if cancelled or significantly changed (3h+ domestic, 6h+ international) and the passenger declines the alternative.
  3. 3.EU261: compensation €250 / €400 / €600 by distance, unless ops code is an extraordinary circumstance.
  4. 4.Issue with issue_refund to the original form of payment. Never offer a voucher first.
Actionsget_fare_rulescalculate_eu261issue_refundissue_voucher
03

Delayed and damaged baggage

62%
of delayed-bag contacts closed by AI

Pazau reads the bag trace, shares the latest scan, books courier delivery, and reimburses interim expenses within the limits your baggage desk sets. Lost bags move to a Montreal Convention claim.

Procedure · Baggage irregularityLive
  1. 1.Find the file reference with get_bag_trace (WorldTracer).
  2. 2.If located, share the last scan and book delivery with schedule_bag_delivery.
  3. 3.Reimburse interim expenses up to $100/day with reimburse_expense. Above that, approval: baggage desk.
  4. 4.Not located after 21 days → open a lost-bag claim with open_claim.
Actionsget_bag_traceschedule_bag_deliveryreimburse_expenseopen_claim
04

Loyalty, miles and status

74%
of loyalty contacts resolved end-to-end

Missing miles, award changes, status questions and goodwill. Pazau verifies the member, checks flown segments, and credits miles inside program rules, so your loyalty desk handles the exceptions.

Procedure · Missing miles → CreditLive
  1. 1.Verify the member with verify_member (member ID + one-time code).
  2. 2.Check the flown segment in get_flight_history. Claims must be within 6 months.
  3. 3.Credit eligible miles with credit_miles. Waive redeposit fees for Gold and above.
  4. 4.Goodwill over 5,000 miles needs approval: loyalty desk.
Actionsverify_memberget_flight_historycredit_mileswaive_fee
05

Hotel reservation changes

69%
of changes made without a human

Date changes, upgrades, late checkout and cancellations, made directly in the property system within rate-plan rules. Pazau never overrides a non-refundable rate without the policy that allows it.

Procedure · Reservation changeLive
  1. 1.Look up the stay with get_reservation (OPERA or SynXis).
  2. 2.Same rate plan and availability → change with modify_reservation.
  3. 3.Non-refundable rate: free cancellation only within 24 hours of booking.
  4. 4.Upgrade offers follow rate: upsell table. Comps need approval: front office.
Actionsget_reservationcheck_availabilitymodify_reservationcancel_reservation
06

Proactive disruption outreach

−57%
inbound calls during disruption

When operations cancels a flight, Pazau messages every affected passenger on the channel they booked with, with options already held. Most never need to call.

Procedure · Cancellation webhook → OutreachLive
  1. 1.On flight_status cancellation, list affected PNRs with get_manifest.
  2. 2.Hold the best alternative per passenger with hold_seat for 30 minutes.
  3. 3.Message in the booking language. Unaccompanied minors and PRM passengers go to queue: special handling.
Actionsget_manifesthold_seatsend_message
Compliance

Passenger rights, applied the same way every time.

Regulators and passengers ask the same question: why this outcome? Pazau answers it for every conversation, with the rule, the data and the Action in the trace.

Pazau Guard · Travel policy log
  • RedactedPassport number removed before model call
  • RuleEU261 Art. 5(3): ATC strike → no compensation, care still owed
  • ApprovedFare difference $212 · approved by duty manager
  • HeldWheelchair assistance request → routed to accessibility desk
  • RoutedEU passenger → processed in eu-west-1 (Dublin)
EU261 / UK261

Compensation bands and right to care

Distance bands, delay thresholds, extraordinary-circumstance codes and re-routing options are encoded as rules your team maintains. Every decision cites the article it applied.

US DOT

Automatic refunds

Cash refunds for cancellations and significant changes when the passenger declines the alternative, issued within 7 business days for card payments. Vouchers are only offered when the passenger asks.

PCI DSS

Payments without card data in the model

Card numbers are tokenized at capture. Pazau Voice pauses recording and takes DTMF for payments (PCI DSS, SAQ-D). No PAN ever reaches a model or a transcript.

GDPR

EU data residency

European passengers are processed and stored in Dublin and Frankfurt through Pazau Ireland Limited. Model providers retain nothing, and we never train on your data.

ACAA · EC 1107/2006

Accessibility requests go to people

Wheelchair, medical and assistance requests are detected and routed to your special-handling team with a summary. The AI never declines one.

Traces

Exportable for regulators

Immutable traces show the Procedure version, the data seen, and every Action taken. Export by PNR, date range or rule for enforcement inquiries or complaint bodies.

Integrations

Built for the systems travel actually runs on.

Prebuilt Actions for the reservation, departure-control and baggage systems you already operate, plus any REST or SOAP API your team exposes.

Browse all integrations
Reservations & PSS
Amadeus AltéaSabreNavitaireTravelport
Hotels
Oracle OPERASabre SynXisMews
Ops & baggage
SITA WorldTracerCiriumOAG
Payments
AdyenStripeWorldpay
CRM & contact center
SalesforceZendeskGenesysTwilioWhatsApp
Customers

Travel brands that resolve with Pazau.

From online travel agencies to hotel groups, teams use Pazau to keep promises when schedules break.

All customer stories
✺Solstice Travel
“Disruption used to be the worst day of the year for our customers and our team. Now it's a Procedure. Pazau finds the next eligible flight, rebooks it inside our fare rules, and sends the ticket before most travelers have left the gate.”
TA
Tom Achterberg
Director of Customer Operations, Solstice Travel
78%
of disruption rebookings resolved by AI
41,200
travelers rebooked in a single storm weekend
2h 40m → 0
peak phone hold time during disruption
Read the Solstice Travel story
Harbor & Pine Hotels
“Our front desk teams were spending two hours a shift on the phone moving dates. Now Pazau makes the change in our systems, inside our rate rules, and our people are back at the desk with guests who are actually standing there.”
DO
Danielle Okoro
VP Guest Experience, Harbor & Pine Hotels
69%
of reservation conversations resolved by AI
31,000
front desk calls avoided each month
+$1.2M
annual upsell revenue from AI-offered upgrades
Read the Harbor & Pine Hotels story
FAQ

Questions we hear in every evaluation.

Does Pazau make the rebooking itself, or just suggest it?+
It makes it. Pazau calls your PSS through Actions to search, hold, rebook and reissue. You decide the limits: fare difference caps, cabin rules and which changes need a duty manager's approval.
How does Pazau decide between EU261 and DOT?+
Your Procedure defines the jurisdiction logic: departure airport, operating carrier and itinerary. Pazau applies it, computes the outcome, and records the rule it used in the trace. Your team maintains the extraordinary-circumstance code list.
Can it handle a mass disruption without falling over?+
Yes. Pazau scales horizontally and has absorbed 10× normal volume for travel customers during weather events. Proactive outreach reaches most passengers before they contact you.
What about passengers who need assistance?+
Accessibility, unaccompanied minor and medical requests are detected and routed to people with a summary. Pazau never declines them and never makes promises on your behalf.
Where is passenger data processed?+
US customers in the US; EU customers in Dublin and Frankfurt. Passport numbers and card data are redacted before inference, and Pazau never trains foundation models on your data.

Be ready for the next storm.

Bring a week of disruption conversations. We'll show you how many Pazau Agent resolves end-to-end, and which rules it applied.