The Guest Who Messages Instead Of Calling

The phone is answered. The messages are answered when somebody remembers. The social account is answered by whoever has the password.

Guests do not know which is which, and they choose whichever is easiest for them.

What actually happens

Some routes have an owner. Most do not. ⚠️ The ones without an owner are answered when someone happens to look, which is not a service level.

Response time varies enormously. Minutes on the phone, sometimes days elsewhere — and the guest cannot tell in advance which they will get.

Nobody knows how many were missed. An unanswered message leaves no trace in any total, so the loss is invisible.

The busiest routes are frequently the least staffed. ⚠️ Younger guests will not phone. If your messages are unwatched, you are unavailable to a whole segment while believing you are open.

Why closing a route is a real option

The instinct is to be available everywhere. It is better to be reliably available in fewer places.

⚠️ An unwatched route is worse than no route — it looks open, so people use it, and their message sits unread while they conclude you are ignoring them.

Turn off what you cannot staff, or set an automatic reply that says where to go instead. Both are honest; leaving it silently open is not.

What each route needs

A named owner. By role. ⚠️ "Whoever sees it" means nobody, and this is the whole failure.

A stated response time. Internally at minimum, ideally to the guest. "We reply within a few hours" sets an expectation you can meet.

A check schedule. ⚠️ Not "when there is time" — specific points in the day, especially before service, which is when tonight's enquiries arrive.

Somewhere the answer gets recorded. A booking taken by message is a booking, and it has to reach the same place as the phone ones.

The one that costs most

The enquiry that arrives while you are open.

Somebody deciding tonight, messaging at 20:30. ⚠️ Answered within ten minutes, they come. Answered tomorrow, they went somewhere else — and this is the route least likely to have anyone watching, because everyone is working.

Deciding who checks it during service is worth more than any other change on this list.

The third-party routes

Listing sites, booking platforms, review sites with messaging. ⚠️ Frequently forgotten entirely, sometimes for years, and they are where people who do not know you go first.

Check every one you have an account on. There will be messages.

Three to hold

Response time by route. ⚠️ The variation is the finding, not the average.

Enquiries received by route. You will be staffing the wrong one — most venues are, and the count is the only way to see it.

Unanswered messages, older than a day. Should be zero. Look now — it usually is not, and each one was somebody who wanted to come.

Where the record has to sit

An enquiry answered in a message thread and never written down is a booking only in the memory of whoever replied. Every route has to end at the same record, or the phone bookings are real and the rest are approximate.

tasteck keeps bookings on one record regardless of how they arrived, so a booking taken by message and one taken by phone are the same booking.

They did not fail to contact you. They contacted you on the route nobody was watching, and from where they were sitting it looked exactly like being ignored.