More work · Travel CRM · Dynamic booking · Operations
From booking request. To travel operation.
A connected travel platform that brings public discovery, booking flows, customer context and agent operations into one product system.
The real experience
A connected travel workspace in motion.
The walkthrough moves through the real CRM surface: overview, customer context, travel products and booking actions sharing one operational language.
Autoplays when it reaches the viewport. Pause or replay to inspect the real interface.
The product
One workspace for selling, servicing and tracking travel.
vbooking combines a public travel experience with an internal CRM for agents. The interface has to move between discovery, flight and package details, customer records and operational follow-up without making the product feel fragmented.
- Role
- Frontend development · Product UI
- Platform
- Responsive travel platform
- Focus
- CRM + booking operations
- Direction
- English · LTR
The challenge
Different constraints.
One clear product language.
Each decision had to respect the real domain instead of forcing the project into a generic website pattern.
Many product types
Flights, hotels, rentals, experiences, packages and transfers need a shared interaction model.
Two audiences
Public discovery and agent operations must feel related while serving very different jobs.
Dense decisions
Search rules, dates, travelers, availability and customer context need clear hierarchy.
Interface story
The operational layer stays calm while the inventory changes.
A stable dashboard structure lets travel categories, customer data and booking controls change without moving the user’s mental map.
Interface decisions
A system shaped around the job, not the template.
Shared navigation
Travel products keep predictable homes across public and internal surfaces.
Progressive detail
High-level choices appear before dates, travelers and operational fields.
Reusable states
Search, selection, loading and empty states behave consistently across inventory types.
Agent context
Customer and booking information remains visible when the workflow gets deeper.
Outcome
A broad travel platform that still feels like one product.
The finished interface connects marketing, booking and CRM work through repeatable patterns instead of a collection of unrelated screens.
Built for the domain.
Clear to the user.