Someone looking for a car usually sends requests to two or three rentals at once. Whoever answers first has the best chance to get the booking. The problem is rarely the price. More often it is a request that arrived at 21:40, landed in a mailbox nobody checked in the evening, and got an answer the next morning.
Where requests get lost
Most small rentals take requests from several places: the site form, phone calls, messengers, email. Each channel has its own weak spot:
- form emails go to a shared mailbox that nobody opens after work;
- a manager sees the request, plans to call back after a hand-over, and forgets;
- two people answer the same client, or nobody does, because each thinks the other one did;
- a request for tomorrow morning is noticed only tomorrow morning.
None of this is about effort. The request is simply not in front of the right person at the right time.
Put new requests where your team already looks
For most rental teams that place is Telegram. It is on every phone, notifications work, and in a group chat the owner and the managers see the same thing.
A useful alert is short but complete: the car, the dates, the client's name and phone. Then a manager can call back without opening anything else. If the message only says "You have a new request", people will still put it off.
In Carentos each company connects its own Telegram bot and its own chat. A new request from the site reaches that chat within a minute. Requests can also go to an email address, for example for a second office.
Add reminders, not just alerts
An alert solves the first minute. Reminders solve the rest of the day. Three of them cover most of what we have seen go wrong in rentals:
- Unanswered request. If a request is still unanswered after 15 minutes, Carentos sends a reminder to the chat. A second message is much harder to ignore.
- Tomorrow's plan. At 20:00 the chat gets the list of tomorrow's pick-ups and returns. The morning shift knows which cars must be clean and fuelled.
- Late returns. If a car was due back and the booking is still open, you get a message. That is the moment to call the client, not the next day.
Keep one list of all requests
Telegram is good for speed, but a chat is a poor archive. Messages scroll away, and a request someone is working on looks the same as a finished one.
That is why every request also lands in the back office, sorted by status: new, in progress, done, cancelled. The dashboard shows unanswered requests and how long each has been waiting, so in the morning you see at once what was missed overnight.
A simple routine that works
- One person is responsible for new requests during each shift. Others can see the chat but do not answer by default.
- When you call a client back, change the request status right away, so colleagues see it is taken.
- Read the 20:00 message before you leave. Tomorrow's problems are easier to fix today.
- Once a week, look through cancelled requests. If many of them were answered late, the issue is in the routine, not in the price.
What to check this week
In the evening, send a test request from your own site using your phone. Note when it arrives, who sees it and when somebody answers. If the answer takes more than 15 minutes, you now know where some of your bookings go.