Start With the Arithmetic
Venue phone conversations usually start with features and monthly cost. Start somewhere more useful: what one call is worth.
| Type of call | Roughly worth | How it behaves if you miss it |
|---|---|---|
| Someone asking your opening hours | Nothing directly | They look at your website. No loss |
| A table booking | One cover, or a few | Books online instead, or rings back. Small loss |
| A change to tonight's booking | Protects an existing booking | May become a no-show. Moderate loss |
| A complaint | Protects a customer and a review | Becomes a public review instead. Real loss |
| A function or event enquiry | Heads × spend per head | Goes to a competitor within minutes, permanently, and you never find out |
Work out your own bottom-row number now. Forty people at $65 a head is $2,600. A corporate Christmas booking or a wedding is a multiple of that. And most function customers come back — the same organiser books the following year, and the guests become covers.
The most valuable call a venue receives, and the most likely to be missed, are the same call. Everything else in this article follows from that one sentence.
The reason it is the most likely to be missed is structural rather than careless. Function enquiries are made during business hours by people at their desks — which is exactly when your lunch service is running and the host station is unattended. Your busiest phone hour is your busiest floor hour. An office does not have that problem. A venue has it every single day.
The One-Week Count
Before spending anything, spend a week counting. A sheet of paper at the host station, five columns, one tally mark per call.
What you will find
Between a third and a half of all calls are routine questions — hours, address, parking, dietary, is the kitchen still open. None of them needs a human.
What will surprise you
How few function enquiries you are recording compared with what you assumed. That gap is not fewer enquiries arriving. It is enquiries arriving and not being captured.
What to do with it
Design from your own numbers rather than from an article. A venue with heavy function volume and one with almost none should build quite different systems.
Add a sixth column while you are at it: calls that rang out. Nobody will fill it in reliably, which is precisely the point — the calls you miss are invisible by definition, and the only real way to count them is from the phone system's own reporting. If your current system cannot tell you how many calls went unanswered last Friday between noon and two, that is itself the finding.
The Caller Who Is Shopping
A function enquiry is not a booking. It is a sales conversation, and the caller is running a comparison.
| What they are doing | What that means you must do |
|---|---|
| Ringing three or four venues in one sitting | Answer, or be the venue that did not. There is no second chance and no callback |
| Judging whether you can handle their event | They need someone who knows capacity, minimum spend and available dates — not whoever was nearest the phone |
| Under time pressure and often emotional | A wake, a milestone birthday, a work party they were told to organise. Confidence and speed matter more than price |
| Not leaving voicemails | If you rely on voicemail for this category you are relying on the least likely outcome |
| Deciding partly on who responds first | Same-day response is not good service; it is the difference between winning and losing the event |
So build a path that matches that behaviour:
- A dedicated route. A menu option and a direct number published on your functions page. It costs nothing and it lifts the highest-value call out of the general queue.
- A named owner and a deputy. Functions should never be "whoever picks up". Two people who can talk confidently about dates, capacity and minimum spend.
- It follows them. The functions manager is on the floor, in the cellar, or at another site. Route to the person, not to a handset bolted to a wall.
- If it does go to voicemail, it is text within a minute. Transcribed and pushed to a phone, not sitting in a mailbox until close. A ninety-minute callback wins events that a next-morning callback loses.
A test worth running this week
Have a friend ring your venue at 12:40pm on a Friday and ask about a function for forty people in November. Then ring at 7:30pm on Saturday and do the same. Note how long it rings, who answers, whether they could answer the questions, and how long the callback took. That is what your best prospect experiences. Most venue owners find the exercise uncomfortable, which is what makes it worth doing.
Service Periods Beat Business Hours
Phone systems are configured with business hours because that is what offices have. A venue does not have business hours; it has periods, each of which wants the phone to behave differently.
| Period | Floor capacity to answer | What the phone should do |
|---|---|---|
| Morning admin | High | Everything rings through. Best window for functions, suppliers and complex bookings |
| Lunch service | Near zero | Greeting absorbs routine questions, bookings to online, functions to a mobile |
| Afternoon lull | High | Everything rings through, and callbacks from lunch get worked. The most productive phone hour of the day |
| Dinner service | Zero | As lunch, tighter. Nobody should be answering general enquiries at 7:30 on a Saturday |
| Closed | None | Greeting with hours and booking link; functions to transcribed voicemail with a promised response |
Two settings that cost venues real money every year
Weekend schedules configured as a copy of weekdays — a venue's Saturday shape bears no relation to its Tuesday. And public holidays, which are usually set once and never revisited: a venue trading on a public holiday while its phone tells callers it is closed loses an entire day of trade, and it happens somewhere every long weekend. Put a recurring calendar reminder against the holiday settings.
The Twenty Seconds That Frees Your Floor
The single cheapest improvement available to a venue is a good recorded greeting, and it is usually either absent or six years out of date.
A third to a half of calls are answerable in twenty seconds without a person: opening hours, address and parking, whether the kitchen is still serving, whether you cater to dietary requirements, and the booking link. Handling those with a greeting is not worse service. A caller who wanted your Monday hours and had them in twelve seconds had a better experience than one who waited ninety seconds and interrupted a service to get them.
Short
Twenty seconds. Hours, address, the two questions you get most, then the options. Anything longer and people press zero out of frustration.
Three options, not seven
Bookings, functions, everything else. Depth in a menu is where venue callers give up. Three is enough for a venue and always has been.
Current
Re-recorded whenever hours change, and specifically before every long weekend. An out-of-date greeting is worse than none, because it is confidently wrong.
Recovering the Calls You Never See
Two categories of call disappear entirely: those arriving while you are flat out, and those arriving while you are shut. Hospitality enquiries do not respect trading hours — people organise work Christmas parties at 4pm on a Tuesday and plan events on Sunday evenings.
Widely cited industry research puts a large share of calls to small service businesses outside business hours, and finds that most people who reach voicemail leave no message. Treat the figures as directional; your own reporting is the number that matters. The direction, though, is not seriously disputed, and three inexpensive things follow from it.
| Fix | What it recovers |
|---|---|
| Missed-call SMS | An automatic text on every unanswered call — hours, booking link, and "reply here about a function and we'll call you back today". Works identically whether you were shut or simply slammed, and turns a dead end into an open thread |
| Voicemail transcribed to text | Messages read at a glance instead of listened to at close. This is the practical difference between a function voicemail being actioned in an hour and being actioned next week |
| Unanswered-call reporting | The number itself. Until a venue can see that it missed 22 calls last Friday between 12 and 2, the problem does not exist in anyone's mind |
Some venues take the next step and put an AI agent on out-of-hours calls, answering the repetitive questions properly and capturing function details for a callback. Hospitality suits it unusually well precisely because the questions are so predictable — which calls to automate covers how to judge it. For most venues, though, the missed-call SMS and a current greeting capture the majority of the value for almost nothing.
The Deposit Trap
A short section on something almost no venue has considered, because it is a genuine exposure sitting quietly in most systems.
Function bookings involve deposits. Deposits are commonly taken by having the customer read out a card number. Many phone systems record calls by default. Put those together and you are creating and storing audio files containing full card numbers and security codes, often going back years.
Why it matters
Payment card industry security standards specifically restrict storing sensitive authentication data, including the card security code, after authorisation — and a recording is storage. A venue with two years of recorded deposit calls has an obligation problem and a genuinely attractive target. Nobody decided to do this; it is what happens when call recording and phone deposits are each switched on for perfectly good reasons, separately.
Three ways out, best first. Stop taking cards by phone — send a payment link by SMS while the caller is still on the line, which is faster, removes transcription errors, produces a receipt trail and is what most customers now expect. Or pause the recording for the payment portion, which works but depends on staff remembering every time. Or exclude the functions line from recording entirely, which is blunt but closes the gap.
The payment-link approach has a side benefit worth noting: it timestamps the deposit and gives you a written trail, which resolves the "we definitely paid the deposit" conversation that every venue has had at least once.
Groups: The Central Functions Desk
For a group of three or more venues, one change usually outperforms everything else on this page.
The single highest-return change for a group
A caller wanting a room for forty on a Saturday in November does not care which of your venues they get. But if they ring the one site that is booked out and are told no, they leave the group entirely and ring a competitor. One functions team, seeing enquiries from every venue with visibility of each site's availability, converts “sorry, we're full” into a booking somewhere else in the group. That is revenue you are currently handing away several times a month without ever seeing it.
| Group problem | Design |
|---|---|
| Callers constantly ring the wrong venue | Internal transfer between sites, never "here's their number, try them". A caller made to redial is a caller you may lose |
| Every venue's phone is configured differently | One platform, one template per venue. Consistency is what makes a group manageable |
| Nobody knows which venue misses calls | Reporting by site. Answer rates commonly range from 95% to 60% across sites in the same group |
| Head office cannot reach a venue at peak | A separate internal path that does not queue behind customers |
| A new venue takes weeks to set up | Template plus pre-configured handsets — see zero-touch provisioning |
One more design rule that applies to every venue but bites hardest in groups: assume the person answering tonight started last week. Hospitality turnover means any design requiring training decays within a season. Route to roles rather than to individuals' mobile numbers, make transfer a single button, keep the menu to three options, and put a five-line printed card at the host station. If a new starter cannot transfer a call to functions on their first try, the design is wrong — not the person.
What to Do, in Order of Return
Ordered so a venue that stops after step three has already fixed most of the problem.
| # | Action | Cost | Return |
|---|---|---|---|
| 1 | Count calls for one week, in five categories, plus unanswered | Free | Tells you which of the rest matters to you |
| 2 | Dedicated function path: menu option, direct number, named owner, follows them to mobile | Negligible | Highest per-call value in the business |
| 3 | Re-record the greeting; set service-period routing; fix the holiday calendar | An hour | Removes a third of calls from the floor at peak |
| 4 | Missed-call SMS and voicemail transcription | Small | Recovers the calls you currently never see |
| 5 | Move deposits to a payment link by SMS | Small | Closes the recording exposure and speeds up deposits |
| 6 | Cordless handset that reaches somewhere quiet | Hardware | Fewer wrong bookings; longer calls handled properly |
| 7 | Groups: central functions desk, per-site reporting | Setup | Converts "we're full" into a booking elsewhere in the group |
1
Enquiry > a year of phone bills
~⅓
Calls a greeting can answer
3
Menu options, never more
0
Card numbers in recordings
None of this requires a hospitality-specific product. It is ordinary capability arranged around how a venue actually trades, rather than around the office template nearly every venue inherited without choosing it. Start with the count — it takes a week, costs nothing, and it will tell you which of the six steps below it are worth your time.
If your peak is seasonal, set the function path up in September rather than in the second week of December. And if you run takeaway or delivery alongside the room, business SMS from your phone system covers order-ready notifications, which take a surprising volume of calls off the phone entirely.
Frequently Asked Questions
What is a missed function enquiry actually worth?
Do the arithmetic with your own numbers: heads multiplied by spend per head. Forty people at sixty-five dollars a head is two thousand six hundred dollars, and a corporate Christmas booking or a wedding is a multiple of that. Most function customers also return — the same organiser books again the following year, and their guests become ordinary covers. Compare that with the other calls a venue takes. Someone asking your opening hours is worth nothing directly and will simply check your website. A table booking is worth a cover or a few, and if missed the customer usually books online or rings back. A function enquiry, if missed, goes to a competitor within minutes, permanently, and you never find out it happened. That asymmetry is the whole argument: the most valuable call a venue receives and the one most likely to be missed are the same call. The reason it is most likely to be missed is structural rather than careless — function enquiries are made during business hours by people at their desks, which is exactly when your lunch service is running and the host station is unattended. Your busiest phone hour is your busiest floor hour, which is a problem an office simply does not have.
How should function enquiries be handled differently?
Treat them as a sales conversation rather than a booking, because that is what they are. The caller is ringing three or four venues in one sitting, judging whether you can handle their event, often under time pressure and emotionally invested — a wake, a milestone birthday, a work party they were told to organise. They will not leave a voicemail, and they frequently decide partly on who responds first. Four design responses follow. Give them a dedicated route: a menu option plus a direct number published on your functions page, which costs nothing and lifts the highest-value call out of the general queue. Give that route a named owner and a deputy who can talk confidently about capacity, minimum spend and available dates, rather than whoever happens to pick up. Make it follow the person, since the functions manager is on the floor, in the cellar or at another site rather than next to a wall-mounted handset. And if it does reach voicemail, have it transcribed and pushed to a phone within a minute — a ninety-minute callback wins events that a next-morning callback loses. A test worth running this week: have a friend ring at 12:40pm on a Friday asking about forty people in November, then again at 7:30pm on Saturday, and note what happens.
How should a venue phone behave during service?
Route by service period rather than business hours, because a venue does not have business hours — it has periods that each want different behaviour. Morning admin has high capacity to answer, so everything should ring through and this is the best window for functions, suppliers and complex bookings. During lunch service capacity is near zero, so a recorded greeting should absorb the routine questions, bookings should point at your online system, and function enquiries should go to a mobile. The afternoon lull is the most productive phone hour of the day and should be used deliberately for working callbacks from lunch. Dinner service is the same as lunch but tighter — nobody should be answering general enquiries at half past seven on a Saturday. When closed, the greeting should carry hours and a booking link, with functions going to transcribed voicemail and a promised response time. Two settings cost venues real money every year: weekend schedules configured as a copy of weekdays, when a Saturday bears no relation to a Tuesday, and public holidays, which are typically set once and never revisited — a venue trading on a public holiday while its phone says it is closed loses a full day of trade.
Is a recorded greeting worse service than a person answering?
Not for the calls it handles. Between a third and a half of a venue's calls are routine questions answerable in twenty seconds without any human involvement: opening hours, address and parking, whether the kitchen is still serving, dietary requirements, and the booking link. A caller who wanted your Monday hours and got them in twelve seconds had a better experience than one who waited ninety seconds and interrupted a service to get the same answer. Three rules make a greeting work rather than annoy. Keep it to about twenty seconds — hours, address, your two most common questions, then the options — because anything longer makes people press zero out of frustration. Keep it to three options: bookings, functions, everything else. Menu depth is where venue callers give up, and three has always been enough for a venue. And keep it current, re-recorded whenever hours change and specifically before every long weekend, because an out-of-date greeting is worse than none at all since it is confidently wrong.
Is it a problem to take deposit card details over the phone?
It can be, and almost no venue has considered it. Function bookings involve deposits, deposits are commonly taken by having a customer read out a card number, and many phone systems record calls by default. Combined, you are creating and storing audio files containing full card numbers and security codes, often going back years. Payment card industry security standards specifically restrict storing sensitive authentication data including the card security code after authorisation, and a call recording is storage. A venue with two years of recorded deposit calls has both an obligation problem and a genuinely attractive target sitting in its system. Nobody decided to do this — it is what happens when call recording and phone deposits are each switched on for perfectly good reasons, separately. Three ways out, best first: stop taking cards by phone and instead send a payment link by SMS while the caller is still on the line, which is faster, eliminates transcription errors and produces a receipt trail; or pause the recording during the payment portion, which works but relies on staff remembering; or exclude the functions line from recording entirely, which is blunt but closes the gap. The payment-link approach also timestamps the deposit, which settles the 'we definitely paid' conversation every venue has had.
How do we capture calls that come in after hours?
Hospitality enquiries do not respect trading hours — people organise work Christmas parties at four o'clock on a Tuesday and plan events on Sunday evenings. Widely cited industry research puts a large share of calls to small service businesses outside business hours and finds that most people reaching voicemail leave no message. Treat those figures as directional and use your own reporting for the real number, but the direction is not seriously disputed. Three inexpensive fixes follow. Missed-call SMS sends an automatic text on every unanswered call with your hours, a booking link and an invitation to reply about a function for a callback — it works identically whether you were shut or simply slammed, and it turns a dead end into an open thread. Voicemail transcription lets messages be read at a glance rather than listened to at close, which is the practical difference between a function voicemail being actioned within the hour and next week. And unanswered-call reporting gives you the number itself: until a venue can see that it missed twenty-two calls last Friday between twelve and two, the problem does not exist in anyone's mind. Some venues go further with an AI agent handling out-of-hours enquiries, which suits hospitality well because the questions are so predictable.
What changes when you run several venues?
One change outperforms everything else: a central functions desk. A caller wanting a room for forty on a Saturday in November does not care which of your venues they get, but if they ring the site that is booked out and are told no, they leave the group entirely and ring a competitor. One functions team seeing enquiries from every venue, with visibility of each site's availability, converts 'sorry, we're full' into a booking somewhere else in the group — revenue currently being handed away several times a month without anyone seeing it. Beyond that, four things. Transfers between sites should be internal calls rather than reading out another number, because a caller made to hang up and redial is a caller you may lose. Use one platform with one template applied per venue, since consistency is what makes a group manageable at all. Add reporting by site, because answer rates commonly range from ninety-five per cent to sixty per cent across sites in the same group and it is invisible until measured. And give head office a separate internal path that does not queue behind customers. Underlying all of it, assume the person answering tonight started last week: route to roles not individual mobiles, make transfer one button, keep the menu to three options, and put a five-line card at the host station.
