Where they started
Nobody knew which page a daily vehicle hire inquiry had come from. Content reviews were exercises in collective guesswork.
Routing and handover
Learning which pages generate daily vehicle hire
Day to day with daily vehicle hire, content discussions begin from recorded evidence.
- Client
- Compact car hire specialist
- Region
- Fargo, North Dakota
- Team
- 16 staff, one locally managed operation
- Timeline
- 15 working days, from content approval
- Quoted
- Sarah Redmond, Office manager
The engagement
Before the build
What kept going wrong
For daily vehicle hire, without origins, every page looked equally valuable, which meant no page could be improved with confidence.
What we built
Submissions capture the page and category they came from, together with pickup location, rental dates and vehicle class. The resulting report distinguishes inquiries from pageviews, and message content stays out of the reporting layer.
Where this lives in a plan
Features used
- Originating-page field
- Service category
- Inquiry reporting
- Exclusion of sensitive message text
How the 15 working days ran
15 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 15 working days count starts here, once the team has signed off the wording the site will use.
The build
Originating-page field, service category, inquiry reporting and exclusion of sensitive message text.
Staff review and handover
The team's own staff reviewed the work and took it over, inside the same 15 working days.
Live
Day to day with daily vehicle hire, content discussions begin from recorded evidence.
I can see which page a daily vehicle hire inquiry started on. That gives our content discussions something sturdier than a hunch.
Questions about this case study
How long did this take for the compact car hire specialist?
15 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?
Submissions capture the page and category they came from, together with pickup location, rental dates and vehicle class. The resulting report distinguishes inquiries from pageviews, and message content stays out of the reporting layer. The pieces it used: originating-page field, service category, inquiry reporting and exclusion of sensitive message text.
Is this part of a GetRentalWebsite plan?
The work here maps to every booking request lands where you work 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 compact car hire specialist in Fargo, North Dakota, and quote the person we worked with, Sarah Redmond, office manager. 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.