Illustrative reference architecture. Validate requirements for your organization.
Illustrative architecture: A travel operator manages guests whose delayed arrival affects hotel check-in, airport transfers, and a prepaid activity. Service staff need compatible alternatives across suppliers. Agents prepare options with clear terms; travelers and authorized staff approve changes and financial commitments.
Problem
Availability expires quickly, supplier confirmation can lag, and one successful cancellation may leave another service unchanged. An agent that says the journey is fixed after a single receipt can leave the guest stranded or double booked.
Why a multi-agent system?
Booking, inventory, policy, and itinerary specialists work on separate supplier interfaces. A durable coordinator owns reservation expiry, customer consent, and partial-success recovery across the journey.
Intended outcome
The intended result is a reviewable operational decision with source evidence and explicit ownership. Evaluate confirmed recovery quality and repeat contacts alongside preparation time. Guest satisfaction depends on supplier execution and individual needs, so retain requirement-level evidence and unresolved obligations throughout the case.
Specialist agent team
Booking reconciler
Read confirmed itinerary items, traveler entitlements, and prior change operations.
Tools
Reservation system API
payment status reader
Authority boundary
Cannot cancel or change bookings without scoped approval.
Alternative finder
Query current rooms, transfers, and activity options matching recorded requirements.
Tools
Supplier availability APIs
accessibility attribute catalog
Authority boundary
Cannot assume accessibility from marketing text or promise unheld inventory.
Policy evidence agent
Retrieve change terms and calculate supplier-confirmed charges.
Tools
Fare and rate rule reader
exact price calculator
Authority boundary
Cannot waive supplier conditions or invent refund eligibility.
Journey coordinator
Present compatible options and manage the approved change sequence.
Tools
Itinerary draft tool
reservation hold service
Authority boundary
Requires traveler consent for the exact itinerary and authorized approval for exceptions.
Enterprise systems
Reservation and customer platforms
Own confirmed bookings, traveler identity, preferences, and approved communication.
Supplier distribution adapters
Expose live availability, temporary holds, confirmation receipts, and cancellation status.
Payment and service recovery systems
Track charges, refunds, vouchers, and unresolved partial changes independently.
Architecture diagrams
Disruption-aware guest journey recovery — logical architecture — Specialists produce bounded findings; the evidence ledger preserves source versions and human decisions before an authorized adapter changes a system of record.
Failure and decision sequence — A hotel hold expires while the transfer change succeeds. The workflow records unresolved work and resumes only after the source state and reviewer authority are checked.
sequenceDiagram
participant O as "Case orchestrator"
participant S as "Reservation and customer platforms"
participant H as "Accountable reviewer"
O->>S: Read confirmed journey components
O->>H: Present complete priced change
H-->>O: Approve itinerary and limits
O->>S: Commit held components
S-->>O: Transfer confirmed and hotel rejected
O->>H: Present partial recovery and next options
Runtime flow
1
Register disruption
Verify traveler identity and link affected itinerary components with current confirmations and remaining service deadlines.
2
Read constraints
Retrieve explicit accessibility, timing, occupancy, and change-policy requirements without inferring sensitive preferences.
3
Find compatible options
Query suppliers in parallel and label unheld quotes, held inventory, and confirmed bookings distinctly.
4
Price complete change
Calculate total fees and refund timing across components, including the consequences if only part of the plan succeeds.
5
Confirm traveler choice
Present exact services, times, accessibility confirmations, amounts, and expiry before recording consent.
6
Execute coordinated recovery
Commit held components in the approved order, reconcile acknowledgements, and escalate or compensate partial changes under the agreed policy.
Failure recovery
A hotel hold expires while the transfer change succeeds.
Detect: Supplier receipts show a confirmed transfer but rejected accommodation commitment.
Recover: Keep the case open, present remaining options, and apply only the compensation actions the traveler approved.
An accessibility attribute is unverified.
Detect: Supplier data lacks the required confirmed attribute or conflicts with the guest's requirement.
Recover: Request supplier confirmation and exclude the option from confirmed-compatible choices until resolved.
Security & decision boundaries
Require traveler consent bound to exact itinerary components, prices, and change terms.
Keep accessibility requirements explicit and verify supplier evidence before making commitments.
Protect passport and identity data from unnecessary specialist prompts and logs.
Track each supplier operation with its own idempotency key and confirmation state.
Never describe a partially completed journey change as fully confirmed.
Operational metrics
Measurement definitions, not promised improvements.
Compatible option latency
Time from verified disruption to a fully priced option satisfying recorded requirements.
Confirmation completeness
Approved changes with all required supplier receipts divided by approved changes.
Partial recovery duration
Time from first partial failure to traveler-accepted resolution or accountable escalation.
Requirement fidelity
Audited booked options meeting all explicitly recorded requirements divided by audited booked options.
Architecture tradeoffs
Decision
Benefit
Cost
Cross-supplier orchestration
Offers coherent journey choices.
Introduces distributed transaction and compensation complexity.
Temporary inventory holds
Reduces quote expiry during consent.
May incur fees or consume scarce capacity until released.
Explicit requirement matching
Protects traveler needs from vague recommendations.
Supplier metadata gaps can reduce available options.
Rollout plan
Synthetic disrupted itineraries
Service staff verify consent, pricing, accessibility evidence, and partial booking recovery.
Draft assistance pilot
One destination team reviews options without supplier mutations or customer promises.
Approved booking changes
Selected suppliers launch after hold-expiry, duplicate-payment, and partial-confirmation tests pass.