The challenge
Mosca Rental had a presentation problem and an operations problem at the same time. The booking interface was unclear enough to create hesitation before visitors submitted — but even when requests came through, they arrived with missing or inconsistent information that slowed down the response process and increased the back-and-forth before a booking could be confirmed.
Both problems needed solving together. Fixing the frontend without fixing the data structure would have improved the conversion rate while leaving the operational problem intact. The two sides of the system had to be designed as one.
The customer journey
The front end was rebuilt around confidence and momentum. Vehicle options were structured with clear, comparable information so visitors could make a decision without needing to ask follow-up questions. The form sequence was reordered to follow the natural decision path — vehicle first, dates and details second, contact last — rather than leading with administrative fields that interrupt the flow before trust is established.
Copy was tightened throughout. Every label, every placeholder, every button was written to guide rather than interrogate. On mobile — where a significant share of rental booking intent arrives — the experience was simplified to keep the path from interest to submission as short as possible.
The operational layer
A custom PHP plugin handled the booking logic rather than bending a generic WooCommerce extension to fit requirements it wasn't built for. That decision gave the form submission output a structured, consistent data format — vehicle type, dates, contact details, and any special requirements all captured in the same fields, in the same format, on every request.
The downstream effect was immediate: requests arrived complete and actionable. Staff could respond faster, prioritise more clearly, and spend less time chasing missing information. When the intake system is good, every step after it gets easier.
The result
A smoother customer journey and a materially better internal process. Booking completion improved because the flow removed the friction that was causing drop-off. Response quality improved because submissions arrived with the information needed to act. The website became the first step in the operations workflow — which is what it should always have been.
