Travel & Hospitality

Personalized Trip Concierge

Designed for Traveler

Turn a traveller's loose idea into a bookable, personalized itinerary by combining live inventory, rates, loyalty status, stated preferences, and destination knowledge, with explicit traveller confirmation before any booking is ticketed.

Contract TRV-01 · primary aggregate TripPlan · mode loading

Decision brief

Confirm and ticket the booking: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Traveller

The named role remains accountable for the consequential decision.

Governed evidence

6 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

A traveller asks for a five-night Lisbon trip in October under 2,000 euros with an aisle seat and walkable neighbourhood; the concierge assembles a flight plus boutique hotel itinerary, applies a loyalty upgrade benefit, cites the seasonality guidance for weather, warns the flight hold expires in 22 minutes, and books only after the traveller confirms..

Decision to make

Turn a traveller's loose idea into a bookable, personalized itinerary by combining live inventory, rates, loyalty status, stated preferences, and destination knowledge, with explicit traveller confirmation before any booking is ticketed.

Outcome to show

Confirmed BookingRecord set with supplier locators gives Traveller the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Describe the trip idea
  2. 2Ground suggestions in preferences and loyalty
  3. 3Shop live inventory and rates
  4. 4Assemble a coherent itinerary
  5. 5Confirm and ticket the booking

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Traveller verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved TripPlan evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Turn a traveller's loose idea into a bookable, personalized itinerary by combining live inventory, rates, loyalty status, stated preferences, and destination knowledge, with explicit traveller confirmation before any booking is ticketed.
Primary aggregate
TripPlan
Primary container
tripPlans
Hierarchical key
/tenantId + /travelerProfileId
Schema version
1

Sample scenario

A traveller asks for a five-night Lisbon trip in October under 2,000 euros with an aisle seat and walkable neighbourhood; the concierge assembles a flight plus boutique hotel itinerary, applies a loyalty upgrade benefit, cites the seasonality guidance for weather, warns the flight hold expires in 22 minutes, and books only after the traveller confirms.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
tripPlans Primary /tenantId + /travelerProfileId TripPlan, TravelerPreferenceProfile, InventoryOffer, LoyaltyStandingSnapshot, BookingRecord
destinationKnowledgeLibrary Reference /tenantId + /destinationCode DestinationKnowledgeChunk

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
TripPlan tripPlans /tenantId + /travelerProfileId trip::{travelerProfileId}::{tripId} tripIntentVector
TravelerPreferenceProfile tripPlans /tenantId + /travelerProfileId preference::{travelerProfileId} preferenceVector
InventoryOffer tripPlans /tenantId + /travelerProfileId offer::{tripId}::{offerId} None
DestinationKnowledgeChunk destinationKnowledgeLibrary /tenantId + /destinationCode destination::{destinationCode}::{chunkIndex} bodyVector
LoyaltyStandingSnapshot tripPlans /tenantId + /travelerProfileId loyalty::{travelerProfileId}::{programCode} None
BookingRecord tripPlans /tenantId + /travelerProfileId booking::{tripId}::{bookingId} None

Query patterns