
On this page
A group enquiry lands on a Tuesday. Twelve rooms for a family wedding, dinner on the Saturday, breakfast both mornings, and three people who need parking for vans.
The hotel replies with a room rate.
That is the moment the enquiry goes to the hotel down the road, which replied with a page.
Why group enquiries leak
They are not bookings. They are small projects with several decisions inside, and most hotel inboxes are built for one decision at a time.
- The enquiry is forwarded between reservations, events, and the restaurant.
- Each department answers its own part, in its own email.
- The organiser has to assemble the answer themselves, and usually gives up.
Ask everything once
One reply, five questions, numbered:
- Dates and nights. Arrival and departure, and whether either is flexible.
- Rooms. How many, what mix, and whether anyone needs accessible rooms.
- Food. Which meals, any dietary needs, and whether there is a private space needed.
- Space. A meeting room, a dinner table, a place for children.
- Money and decision. Who approves, and by when.
Ask once. Asking the same question three times across three emails is how a hotel looks disorganised.
The one-page proposal
The reply should be a single page, not a thread. Sections:
- What is included, room by room
- Food, with a per-head figure or a range
- Space, with the setup
- What is not included: parking, city tax, extra beds
- Total, and what changes the total
- A hold date and a deposit
If the total cannot be firm, say what it depends on. “From” pricing with the assumptions spelled out is honest and usable.
Hold the dates
Groups shop around. Without a hold, the hotel cannot tell the organiser whether the rooms are still there.
Offer a hold of a few days, in writing, and let it expire. A hold that never expires blocks inventory for a booking that will never happen.
The deposit
Groups cancel more than individuals, and later. A deposit at confirmation, with a clear cancellation schedule, protects the hotel without scaring the organiser.
State it plainly: how much, when, and what happens if numbers drop. Group numbers always drop.
The follow-up
- Day 1: the proposal, with the hold date.
- Day 3: a call. Not “did you get it” — “does the room mix work, or shall I adjust it?”
- Day 6: a short message before the hold expires.
- After the hold: release the rooms and say so, kindly.
If the organiser is comparing, the hotel that adjusts quickly wins more often than the cheapest one.
What to record
One record per group, with every department’s commitment attached: rooms, rate, dinner, space, deposit, and who agreed what.
Group bookings fail at the handover. The events team promises a private room, reservations never hears about it, and the group arrives to a table in the bar.
The detail that wins the booking
One line that proves you read the enquiry. “We’ve noted the two vans — there’s space in the rear car park, and we’ll keep the barrier code for your drivers.”
That sentence does more than a discount, because it answers something the organiser was worried about and did not ask.
Measure the response, not the enquiry count
- Share of group enquiries answered within one working day
- Share answered with a single consolidated proposal
- Share that converted
The second number is the one most hotels fail, and it is the easiest to fix.
Where BittaFlow fits
BittaFlow keeps a group enquiry as one record with rooms, food, space, and deposit in the same thread, so every department sees what has been promised. The proposal goes out as one page, and the hold date triggers the follow-up automatically.
Answer once, on one page, with a date. That is most of the sale.


