Where they started
The daily vehicle hire reference lived in a document built for a printer. Anyone opening it on a phone faced a wall of tiny type.
Pages and answers
Daily vehicle hire details, readable at last
For daily vehicle hire, answers are shared as links to exact sections. Reading happens on whatever device the visitor holds, and paper remains an option rather than a requirement.
- Client
- Short-notice daily hire branch
- Region
- Frederick, Maryland
- Team
- 16 staff, one locally managed operation
- Timeline
- 25 working days, from content approval
- Quoted
- Edmund Alford, Customer care supervisor
The engagement
Before the build
What kept going wrong
Day to day with daily vehicle hire, no section could be linked, quoted or checked on a phone. The information was good; its container made it useless.
What we built
Content about rental conditions and collection instructions now lives in clearly headed page sections. Anchor links point to individual answers, and a printable summary remains for anyone who wants a copy.
Where this lives in a plan
Features used
- HTML reference pages
- Descriptive headings
- Section links
- Printable summary
How the 25 working days ran
25 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 25 working days count starts here, once the team has signed off the wording the site will use.
The build
HTML reference pages, descriptive headings, section links and printable summary.
Staff review and handover
The team's own staff reviewed the work and took it over, inside the same 25 working days.
Live
For daily vehicle hire, answers are shared as links to exact sections. Reading happens on whatever device the visitor holds, and paper remains an option rather than a requirement.
For daily vehicle hire, we had solid information trapped in a file nobody wanted to open on a phone. As pages, it finally gets read.
Questions about this case study
How long did this take for the short-notice daily hire branch?
25 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?
Content about rental conditions and collection instructions now lives in clearly headed page sections. Anchor links point to individual answers, and a printable summary remains for anyone who wants a copy. The pieces it used: HTML reference pages, descriptive headings, section links and printable summary.
Is this part of a GetRentalWebsite plan?
The work here maps to pages that open before the tab closes and weekly updates to fleet and rate text 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 short-notice daily hire branch in Frederick, Maryland, and quote the person we worked with, Edmund Alford, customer care supervisor. 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.