Where they started
Whether someone was starting fresh or following up on daily vehicle hire, the site gave them the identical form to complete.
Routing and handover
Existing daily vehicle hire conversations stay findable
With daily vehicle hire, new business and ongoing conversations sort themselves before staff get involved. Customers with a history are no longer processed as strangers.
- Client
- Airport-adjacent car rental office
- Region
- Manchester, New Hampshire
- Team
- 13 staff, one locally managed operation
- Timeline
- 10 working days, from content approval
- Quoted
- Bruce Hollister, Bookings coordinator
The engagement
Before the build
What kept going wrong
When it comes to daily vehicle hire, follow-ups arrived dressed as new business. Staff matched names to old threads before anyone could address the actual question.
What we built
A clearly labeled follow-up path now asks for a reference where one exists, plus the question itself. New requests keep their own route, collecting pickup location, rental dates and vehicle class, and the two message types arrive under different subjects.
Where this lives in a plan
Features used
- Existing-request contact route
- Optional reference field
- Separate email subjects
- New-inquiry form
How the 10 working days ran
10 working days after content approval, including staff review and handover. Four stops, from signed-off wording to the day it went live.
Content approved
The 10 working days count starts here, once the team has signed off the wording the site will use.
The build
Existing-request contact route, optional reference field, separate email subjects and new-inquiry form.
Staff review and handover
The team's own staff reviewed the work and took it over, inside the same 10 working days.
Live
With daily vehicle hire, new business and ongoing conversations sort themselves before staff get involved. Customers with a history are no longer processed as strangers.
Asking an existing daily vehicle hire contact to re-introduce themselves was always faintly insulting. The separate path fixed it.
Questions about this case study
How long did this take for the airport-adjacent car rental office?
10 working days after content approval, including staff review and handover. Because the count starts at content approval, the time the team spent agreeing the wording is not inside it, and their own review before launch is.
What exactly was built?
A clearly labeled follow-up path now asks for a reference where one exists, plus the question itself. New requests keep their own route, collecting pickup location, rental dates and vehicle class, and the two message types arrive under different subjects. The pieces it used: existing-request contact route, optional reference field, separate email subjects and new-inquiry form.
Is this part of a GetRentalWebsite plan?
The work here maps to every booking request lands where you work and A booking request tool built for rental on the features page, which every plan carries. Plans start at $127 a month, with the $697 build fee invoiced only after launch. How it is shaped for your own operation is agreed on the demo call.
Why is the business not named?
Case studies on this site describe the client by the kind of operation and the city, here a airport-adjacent car rental office in Manchester, New Hampshire, and quote the person we worked with, Bruce Hollister, bookings coordinator. The business name, web address and logo are left out on purpose.
Want the same fix at your rental desk?
A live walk-through of the site you would get, built around how your team already works. Plans from $127 a month, the $697 build fee invoiced only after launch.