The usual framing of the Q&A section on a business listing is that it is a job to be done — answer the questions, fill the gaps, reduce the phone calls. Fair enough, and worth doing.
The more interesting use is diagnostic. A question that gets asked repeatedly is not primarily a gap in your listing. It is evidence that something about your restaurant is unclear in a way that is costing you guests who never asked, and the people asking are a self-selecting minority of the ones affected.
Rough arithmetic that is worth taking seriously: for every guest who rings to ask about parking, a substantial number simply book somewhere with a car park. You hear from the persistent ones. The question tells you about the others.
Where to collect the questions from
The listing's Q&A section is the obvious source and the thinnest. Four better ones:
What the phone asks. Keep a sheet by the phone for one week and tally every enquiry by type. Twenty minutes of effort across the week, and it is the single richest source available. Most operators are surprised by both the volume and the concentration.
What the booking notes contain. Free-text notes on bookings are where guests pre-empt their own anxieties: we have a pushchair, one of us is gluten free, is the upstairs accessible. Read a month of them as a set.
What the inbox asks. Social messages and email enquiries, categorised.
What reviews mention finding out the hard way. The complement to all of the above, and the most expensive category. Nobody told us there was no parking. Didn't realise it was all upstairs. These are the people who did not ask.
Put a week's tally next to a month of booking notes and you will have a ranked list. It is usually short — five or six categories account for most of it — and it is remarkably consistent across venues.
The seven that come up almost everywhere
Each one is worth reading twice: once as a listing gap, once as an operational statement.
1. Where do I park? The most common question in hospitality and the one most often absent from every surface a guest can reach. As a listing gap it is a line of text. As an operational statement it is more serious: if the honest answer is on-street, free after six, usually fine except Fridays, then on Fridays a proportion of your guests arrive stressed and late, and a few do not arrive at all. The listing fix takes a minute; knowing that Friday arrivals are compromised is the finding.
2. Can you cater for a coeliac / a severe allergy? Never just an information request. The person asking is deciding whether to risk you, and a vague answer loses the booking and the five people they were coming with. More importantly, if this question arrives often, check whether your kitchen's actual answer is consistent — ask three chefs and a server the same question separately. Where the four answers differ, you have a risk issue rather than a listing issue, and it is the kind that eventually produces a review that arrives four days after the meal.
3. Is there a step / is it accessible? Asked less often than it is needed, because people who have been let down before stop asking and go elsewhere. Precision matters enormously here: accessible is not an answer. Level entry from the street, accessible WC on the ground floor, two steps to the upstairs room is. A vague answer is read as a no by everyone who needs certainty.
4. Do I need to book? The operational version of this question is about your door policy, and if guests cannot predict it then your walk-in trade is being managed by chance. If the real answer is not usually, but always on Friday and Saturday, say exactly that. Guests can work with a rule; they cannot work with we'll try to fit you in.
5. Can children come / do you have high chairs? The listing fix is trivial. The operational read is worth having: if this is asked frequently and your actual provision is two high chairs and no changing table, you have a guest segment arriving to a slightly worse experience than they were promised, which shows up later as mild, unattributable disappointment in your reviews.
6. What are your actual hours today? If guests are asking rather than reading, your hours are either wrong or contradicted somewhere. This one is urgent because of the damage profile — a wrong-hours review is the angriest you will receive, written by someone who never ate your food.
7. Do you do takeaway / delivery / collection? Usually an attributes problem, and worth checking what a signed-out phone shows rather than what you believe you have set. An unset service option frequently reads as absent rather than unknown.
The audit, which takes about forty minutes
- Tally the phone for a week. Categories, not detail.
- Read a month of booking notes. Add to the tally.
- Rank. Anything asked more than three times in a week is in.
- For each one, write the answer in one sentence — the precise version, with the exception named. Free on-street parking after 18:00; a small car park two minutes away on Mill Street; Friday evenings are difficult.
- Put that sentence in all four places, which is the step that gets half-done: the listing Q&A, your own website, the booking confirmation email, and a line by the phone so that staff give the same answer.
- Then ask the operational question, which is the point of the exercise: does this question reveal something we should change rather than explain?
Step six is where the value is. Four categories of answer:
| The question reveals | Example | Response |
|---|---|---|
| Information missing | Parking | Publish the sentence |
| Information inconsistent | Allergens answered differently by different staff | Agree one answer, brief it |
| A genuine operational gap | Two high chairs for a family venue | Fix the provision |
| A policy nobody has decided | "Do we take walk-ins on a Friday?" | Decide it, then publish it |
The third and fourth rows are the ones a listing audit never surfaces. They are also the ones generating reviews.
The booking confirmation is the most underused surface
Of the four places to put the answer, the confirmation email is the one almost nobody uses and the one with the highest open rate in your whole operation.
Two sentences at the bottom — parking, the nearest alternative, and anything structural like stairs or a cashless policy — reach every booked guest at the moment they are planning the journey. It costs one edit to a template and removes a visible share of both the phone calls and the arrival-related complaints.
Answering publicly has costs
Answering publicly commits you. A published statement that you cater for coeliacs is a promise your kitchen has to keep on a Friday with two chefs down. Write what is reliably true, not what is true on a good day.
Do not publish a wishful accessibility answer. This is the one where vagueness does real harm to real people. If there are two steps, say two steps.
The phone tally will under-count. Staff forget during a rush, and the rush is when the calls come. Treat it as a ranking exercise rather than a census.
Q&A sections can be answered by strangers. Anyone can respond to a question on a public listing, and a well-meaning wrong answer from a member of the public will sit there indefinitely. Worth checking yours exists and is correct — and worth posting owner answers to the obvious questions pre-emptively, so there is nothing for a stranger to guess at.
Not everything deserves an answer. Six categories answered properly in four places beats twenty answered once. The long tail is genuinely what the phone is for.
The reason this is worth more than a listing tidy-up is that your guests have already done the research for you. They have identified, by repetition, the exact points at which your restaurant is hard to understand from the outside. Most of those are a sentence. One or two are a decision you have been postponing.
OMMU flags profile fields that have gone stale and picks up reviews mentioning parking, access and allergens so the pattern surfaces from the reviews as well as the phone. A tally sheet by the phone for one week does the diagnostic part just as well, and it is available on Monday.