Simplifying a booking flow without hiding the information needed to price the trip.

The challenge

The earlier booking flow exposed too much information at once and duplicated steps. A customer trying to check a rate could be asked for booking details before they had decided whether the price or vehicle worked for them.

How the project was approached

• Separated rate-check information from the later booking details so customers can get to a price faster.
• Kept one-way, return and hourly trip types visible without creating separate booking systems.
• Placed pickup date and time before return details and added support for multiple intermediate stops.
• Moved passenger, luggage, child-seat, contact and payment questions to the booking stage after a vehicle is selected.
• Designed vehicle cards and pricing breakdowns for small screens first, including base rate, tax, tip and estimated total.

Resulting direction

The resulting flow has fewer decisions in the first step and a more natural progression from route to price, vehicle and reservation details. The work also creates a cleaner handoff for the Angular/.NET booking system and future mobile apps.