Employee Request
Start with destination, timing, travelers, constraints, and the actual business outcome the trip needs to support.
Demo flow
See how Yozu turns travel intent into a coordination-ready next step.
This page uses mock/sandbox data to show the launch MVP flow: options, disclosure, approval, and preflight before any checkout coordination.
AI Planning
Turn messy travel intent into a smaller decision set instead of another wall of search results.
Policy Review
Frame each option with provenance, freshness expectations, and policy/disclosure context before it moves forward.
Manager Approval
Nothing advances until the case crosses an explicit approval checkpoint and the intended option is confirmed.
Operator Coordination
Operators handle the guarded coordination step rather than pretending supplier execution already happened.
Ready for Booking
Preflight makes the case decision-ready, while the public product still stops short of automatic booking.
Decision-ready options
Readable tradeoffs, not a search-results wall.
Balanced arrival + recovery
Best for demo readiness and investor follow-up windows.
- Source
- Mock supplier reference · flight + hotel bundle
- fetched_at
- 2026-06-04 04:40 demo timestamp
- Policy / disclosure
- Cancellation rule opened before next step
- Current state
- Awaiting explicit approval
Lower-cost route with tighter layover risk
Budget-friendly but less forgiving if flights slip.
- Source
- Mock supplier reference · alternate route mix
- fetched_at
- 2026-06-04 04:40 demo timestamp
- Policy / disclosure
- Different cancellation rule surfaced in disclosure
- Current state
- Needs traveler review
Preflight boundary
One last check before confirmation.
No payment capture until explicit user confirmation. If price, inventory, policy, or route context changes, Yozu interrupts the flow and asks for a fresh decision.
Current launch rule
Demo and coordination only. No automatic booking, no merchant-of-record claim, no final booked/paid/ticketed state.