How it worked before
A single shared mailbox caught every touring vehicle requests inquiry. Several staff dipped in when they could, and ownership of any given message was invisible.
Routing and follow-up
Ending the relay race in touring vehicle requests handling
With touring vehicle requests, the 'I thought you had it' conversation has been designed out. Each inquiry shows its owner, its status and its fallback, and anyone covering can see all three.
- Client
- Surf trip campervan hire
- Region
- Sioux Falls, South Dakota
- Team
- 8 staff
- Timeline
- 20 working days
Where the business started
What it was costing the team
When it comes to touring vehicle requests, replies duplicated while neighbors went unanswered. Absence cover meant reconstructing each thread's history before daring to respond.
What we built
The intake workflow now gathers travel dates, passenger count and intended route, assigns a named owner to each request and keeps a simple status for follow-up. A designated backup picks up anything whose primary contact is away.
- Assignment rules
- Follow-up status
- Backup owner
- Internal request summary
How long it took, and in what order
20 working days after content approval, including staff review and handover.
- Day 0Content approvedThe clock starts once the client signs off the wording for this part of the site.
- In betweenBuilt and reviewedWe build it and the client's own staff review it. The parts: Assignment rules, Follow-up status, Backup owner, Internal request summary.
- Working day 20Handed overHandover to the team, with the review included in the count.
What changed
With touring vehicle requests, the 'I thought you had it' conversation has been designed out. Each inquiry shows its owner, its status and its fallback, and anyone covering can see all three.
I can open the touring vehicle requests queue and see who owns what. That was impossible to say six months ago.
Want the same fix on your site?
We will show you how routing and follow-up would work for your fleet, in about 30 minutes.
Questions about this project
How long did this project take?
20 working days after content approval, including staff review and handover. That is 20 working days from the client approving the content to handover. A whole new site launches in 7 to 15 days from the onboarding call depending on the plan.
What exactly was built?
The intake workflow now gathers travel dates, passenger count and intended route, assigns a named owner to each request and keeps a simple status for follow-up. A designated backup picks up anything whose primary contact is away. The parts used were: Assignment rules, Follow-up status, Backup owner, Internal request summary.
Why is the business not named?
The client asked us not to publish its name or web address, so it is described by type and region: a surf trip campervan hire in Sioux Falls, South Dakota. Madhuri Narayan, depot coordinator, is quoted in their own words.
Does this cost extra on top of a plan?
No. Work like this sits inside a managed plan rather than a separate project fee. Plans start at $127 a month, with a $697 one-time build fee invoiced only after the site is live and approved.
More case studies
See what your fleet's site would fix first
Plans from $127 a month, the $697 build fee invoiced only after launch, live in as little as 7 days.