The busiest day
Count the guest messages that arrive on a Saturday. Most of them are one of four questions, and all four have an answer sitting in the reservation already.
Guest contact in a rental operation is dominated by four questions. What time is my delivery. Where do I collect. Has it been dropped yet. Can I change the time.
None of the four needs a person. Each has an answer already sitting on the reservation, and each arrives by a different channel: the booking email, a text to the office mobile, a message on the business page, and a phone call while somebody is loading a van.
What makes them expensive is not the answering. It is that on a Saturday nobody owns the inbox. The person who knows the run is driving it, the person at the counter can see a booking but not the route, and a guest who does not get an answer inside ten minutes phones instead.
Take three hundred reservations in a peak week. If a third of those guests make contact once and each contact takes four minutes across reading, checking and replying, that is one hundred contacts and around seven hours.
Seven hours in the week where you have the least time, spent answering questions your own system already knows. Substitute your own contact rate; the point survives most versions of the arithmetic.
The second cost is worse and harder to see. A guest who cannot get an answer about a delivery window is a guest who is standing at a villa door with a phone, and that experience is what decides the review and the repeat booking.
Put the delivery window, the address, the collection time and the contact route into the confirmation itself rather than into a generic template. Most confirmation emails are a receipt when they could be an itinerary.
Send an unprompted message at the two moments guests ask about: when the run for their day is set, and at the moment of the drop. A photo of the chairs against the porch answers the third question before it is asked.
Give the run an owner for the day, and make sure a guest reply lands where that person can see it against the order rather than in a mailbox four people half-watch.
Messaging is tied to the order. The confirmation, the delivery window, the drop photo and the collection reminder come off the reservation rather than being typed, and a guest reply arrives against that order with the whole history under it.
The person holding the run sees the thread. Nobody has to forward a screenshot of a text message to explain what a guest was promised at eight in the morning.
Guest messaging has the detail.
4 bikes and 2 umbrellas, 14 Sea Pines Circle. Left inside the garage.
Every message hangs off the order, so a reply about a delivery reaches the person holding that run rather than a shared inbox.
The view where a guest watches how many stops away the van is has not shipped. It is the obvious next thing and it is left off this site until it exists.
What is there today is the drop confirmation: a photo, a timestamp and a location, sent as it happens. In practice that removes most of the same contact, which is the reason the tracking view is worth building rather than worth claiming early.
By answering the four common questions before they are asked. What time is the delivery, where is collection, has the drop happened, and how do I change the time. Each has an answer on the reservation, and each becomes a phone call when the confirmation is a receipt rather than an itinerary.
Sending an unprompted message when the run is set, and a photo at the moment of the drop, removes most inbound contact on a peak day. The remaining contact reaches whoever owns that run rather than an inbox nobody watches on a Saturday.
Both, off the reservation. SMS volume beyond the included allowance is passed through at cost rather than marked up.
No. That view has not shipped and there is no date published for it. What guests get today is a confirmation at the moment of the drop, with a photo, a timestamp and a location.
Whoever is holding that run, because the thread sits against the order rather than in a shared mailbox. The history is on the order for anybody who picks it up later.
A demo takes six fields and someone who understands rental operations calls you back. Where Bodhisys is the wrong fit you will hear it on that call rather than after three meetings.
