What a Quiet Phone Is Costing You

Someone called at 7:40pm. Nobody picked up. They called the room down the street instead.

Nothing in your system records that. No line in the report, no missed revenue figure, no notification. The event is invisible by construction — an unanswered call leaves no trace inside the business it failed to reach.

And it is not a small number.

Why the phone still matters

Booking apps and web forms exist. The phone is still the highest-intent channel most night venues have.

Web form  … "I am considering this"
Message   … "I have a question"
Phone     … "I want to do this now, and I want a person to confirm it"

Someone dialling at 7:40pm on a Friday is not researching. They are choosing between you and one other room, and the decision is being made in the next four minutes.

Which is why the answer rate matters more than any other conversion number in the building.

The number nobody has

Answer rate = calls answered ÷ calls received

Most venues cannot compute this, because the phone system and the booking system are separate, and only the second one creates records.

If you have a CTI setup, you already have it. If you do not, your phone provider almost certainly has call logs — most do, and most operators have never looked.

Pull one month. The number is usually worse than expected, and the shape is worse than the number.

The shape matters more than the average

An answer rate of 80% sounds acceptable. Then you split it by hour.

14:00-17:00  … 95% answered.  Nobody is calling
18:00-20:00  … 60% answered.  Everybody is calling
22:00-24:00  … 85% answered.  Some calling

The average is 80%. The number that matters is 60%, in the two hours that produce the bookings.

This is the standard pattern, and it has an obvious cause: the hours with the most calls are the hours with the most in-room work. The person who would answer is doing something else.

The fix is not "answer more calls." It is coverage in a two-hour window.

What happens to a missed caller

Three outcomes, roughly:

They call back later      … some do. Fewer than you would like
They call somewhere else  … most, at peak
They give up entirely     … some, and you never learn

The one that hurts is the second, because it is not a lost booking — it is a booking that went to a competitor, at the moment of highest intent, for a reason that had nothing to do with your room.

And if they had a good night there, you did not lose one booking. You lost a guest.

Measuring the cost

Missed-call cost = missed calls × booking rate on answered calls
                 × average booking value
                 × (1 − callback rate)

The last term is the one people forget. Not every missed call is lost — some ring back. But most operators assume the callback rate is high, and it is usually much lower at peak, precisely because the caller had somewhere else to try.

Even a conservative estimate usually makes the case for the fix, and the fix is normally an hour of rota change rather than a system.

Four fixes, cheapest first

One — move one person into the two-hour window. Not a new hire. A shift adjustment covering the peak, with answering as an explicit duty rather than an interruption.

Two — make the phone visible. In many rooms the phone rings somewhere nobody is standing. A second handset in the right place fixes a surprising share.

Three — a callback list. If the missed number is captured, someone rings back at 9pm. A callback within the hour recovers a meaningful portion — the guest often has not decided yet.

Four — CTI, so the caller is identified before the greeting. A returning guest heard by name books faster and cancels less. This is the only one that costs real money, and it should come last.

The record that makes the rest work

Time of call
Answered / missed
Caller number
Outcome  … booking / enquiry / wrong number

Four fields. The second and third are the ones most systems lose, and they are the two the whole analysis needs.

Wrong numbers matter too. A room with 15% wrong numbers has a listing problem somewhere, and that is a cheap fix once you can see it.

The system we built

tasteck is a booking and analytics system for night venues, built by people who ran them for sixteen years and grew from ¥200 million to ¥1.2 billion a year — six-fold, by attacking the business with systems rather than by pushing harder on sales.

The phone was one of the first things we instrumented, because it was the only channel where we could not see what we were losing.

What it does here: a reservation screen wired to inbound calls — the caller's number arrives before the greeting, and a returning guest's history is on screen while you talk. Call history with timestamp, number, and whether it converted to a booking. Guest records that persist across visits, so a caller is recognised rather than re-entered. Bookings created from the call without retyping the number.

What it does not do: it does not replace your phone system. CTI integration connects to an existing telephony service — the call log and the identification come from that side. What tasteck supplies is the guest record the number resolves to, and the booking that follows.

The output no one else produces

tasteck outputs the maximum you can spend on each marketing channel next month, as an amount in your currency.

Missed calls corrupt every channel number you have. A listing that generates 100 calls and 60 bookings looks half as good as one generating 100 calls and 90 bookings — when the difference was your answer rate, not the channel.

You will cut the wrong channel. Answer rate has to be understood before channel performance means anything.

Nothing else in the nightlife category produces that figure.

Ask it from ChatGPT

tasteck connects to ChatGPT over MCP: ask your numbers as a question and the answer comes back in the chat — how many calls came in last Friday, which converted, who called and had been before.

Measured against every vendor listed on Japan's principal nightlife-industry directory, this is the first implementation of it in the category, and the same interface is callable from anywhere rather than being tied to one assistant.

Multi-language is built in, the operating surface itself, with your language set put in place during onboarding.

From $34 a month for up to two venues. Thirty days free on every plan, cancel any time. → Pricing

Start this week

1. Get one month of call logs from your phone provider. Most operators have never asked.
2. Compute answer rate by hour, not overall. The average hides the two hours that matter.
3. Estimate the cost with a conservative callback rate. It will still make the case.
4. Move one person into the peak window before buying anything.
5. Start a callback list. Within the hour recovers more than you would guess.

Read next

• The Phone Is Your Booking System, Whether You Built One Or Not
• No-Shows: The Money That Never Walks In
• The Guest Who Books and the Guest Who Walks In Are Different Businesses

---

On benchmarks. No target answer rates, callback rates, or missed-call costs appear in this guide. We do not have a dataset broad enough to publish them, and they vary enormously by format, city, and how bookings arrive. One month of your own call log, split by hour, will show you a two-hour window that no industry average can.