Friday, twenty past nine. Someone is organising a birthday for fourteen people in three weeks and is messaging four bars from a table in a fifth. The bar with the busiest floor has nobody free to look at a phone.
By Sunday afternoon she has booked somewhere. On Monday, a manager reads the message.
The teardown: why this keeps happening
Group enquiries are made socially, in the evening, often by someone who is already out. The bar is at its busiest at exactly that moment. The people who could confirm a booking are pouring drinks, and the enquiry sits until the quiet part of the week.
Failure one: no group booking page
Minimum group size, what can be reserved, whether there is a minimum spend, deposit terms and how long a table is held. Without this, every enquiry starts from nothing.
Failure two: nobody captures the basics
Date, arrival time, number of people, occasion, whether food is wanted and a contact number. Five fields, and with them a manager can confirm in one message on Saturday morning.
Failure three: the minimum spend is a secret
Groups planning a night out want to know before they ask. Publishing it filters out the enquiries that would waste both sides' time and reassures the ones that would not.
Failure four: deposits are handled inconsistently
Whether one is required, how much, whether it comes off the bill and what happens on a no-show. Groups cancel, and a stated deposit policy is the only protection.
Failure five: nobody explains what can be reserved
A booth, an area, a section or nothing at all. Bars often cannot guarantee specific spaces on a Saturday and should say so rather than disappointing fourteen people at the door.
Failure six: drinks packages are not published
Arrival drinks, bottle service, a bar tab arrangement or a pre-order. These convert a table booking into a substantially larger spend and most bars never mention them.
Failure seven: the reply comes too late to matter
Group organisers are making a decision within hours, not days. A reply on Monday is not a slow reply, it is a missed booking, which is exactly the weekend enquiry problem.
Failure eight: no confirmation, no show
Groups shrink. Confirming numbers a day or two beforehand, and making that a published part of the process, protects a Saturday night's covers.
What to publish
Minimum group size, what can be reserved, minimum spend, deposit terms, how long tables are held, drinks packages, food options and the cut-off for confirming numbers.
The booking itself is the easy part
Once captured, a manager confirms in a minute. The difficulty is only ever that nobody was free at half past nine on Friday.
Tables are lost to slow replies constantly
It is the pattern described in table and booth bookings bars lose to slow replies.
Quiet nights can be filled the same way
That is covered in event night enquiries that fill a bar on quiet evenings.
Detail capture matters in every venue
It is set out in large group bookings and the details nobody captures.
Getting started
Publish group terms, packages and deposits, then capture date, numbers and contact details at the moment someone asks. SpideyChat for hospitality answers from your published pages. Try SpideyChat on your own site, or read about capture on the features page.