Event enquiries arrive in a particular order. First the date. Then the number of guests. Then, if the date is free and the room is big enough, everything else: catering, bar, parking, music curfew, whether the dog can come.
That first question is the one a venue cannot afford to get wrong. Tell someone the 14th of June is free when it was provisionally held last week, and you have either a double booking or an awkward retraction to a couple who have already told their families.
A venue enquiry assistant is useful precisely because most of those questions can be answered well from your content. The date question is the exception, and handling it properly is what makes the rest work.
Why "is it free?" must go to a person
Venue diaries move constantly. Provisional holds, deposits pending, a corporate client who might take the whole floor. Even if you uploaded a list of booked dates, it would be wrong within days, and the assistant would repeat it confidently.
So the rule is fixed: the assistant never confirms or denies availability. It collects the date, a backup date if there is one, and the details needed to check fit, and it says plainly that the events team will confirm.
This is not a weakness to apologise for. Planners expect a venue to check. What they do not expect is to wait three days for a reply to "is the 14th free?", which is what happens when enquiries sit in a shared inbox over a busy weekend. What an AI receptionist must never promise covers this principle across other businesses.
An enquiry, handled well
Here is the shape of a good conversation. Notice that the assistant answers everything it can and parks only the date.
Visitor: Hi, is Saturday 14 June next year available? It's for a 60th birthday party.
Assistant: Happy to help with that. I can't check the diary myself, but I'll take the details and the events team will confirm whether the 14th is free, usually within one working day. Roughly how many guests are you expecting?
Visitor: Around 90.
Assistant: The Garden Room holds up to 120 for a standing reception or 80 seated, so 90 would work well for a buffet or drinks and canapés, but not a full sit-down meal. The Main Hall seats up to 150. Were you thinking seated or more of a party format?
Visitor: Party, with some food. Can we bring our own DJ?
Assistant: Yes, external DJs are welcome, with music finishing at 11.30pm. Would you have any flexibility on the date, in case the 14th is taken? And what's the best email or phone number for the team to reach you?
The capacity figures, curfew and DJ policy come straight from content the venue supplied. The date is captured, a backup is requested, and the visitor knows when to expect a reply.
What the assistant can answer, and what it should capture
A split like this is worth writing out before launch, so everyone agrees where the line sits.
| Question | Answer from content | Capture for the team |
|---|---|---|
| Is my date available? | No | Date, backup date, event type |
| How many people does each room hold? | Yes, seated and standing | Guest numbers |
| Do you do catering, and can we use our own? | Yes, per your policy | Dietary needs, menu interest |
| What do packages cost? | Published packages and minimum spends | Budget, tailored requirements |
| Parking, access, step-free entry? | Yes | Specific accessibility needs |
| Music curfew, noise limits, decorations? | Yes | Nothing, unless unusual |
| Can we hold the date? | Explain your hold process | Request to hold, for a person to action |
| Can we visit? | Explain viewing options | Preferred viewing days |
The right-hand column is effectively your enquiry form, gathered in conversation rather than by a wall of fields.
The details that make an enquiry worth replying to
A bare "is the 14th free" leaves your coordinator doing the interview on the reply. A full enquiry lets them respond with a yes or no and a proposal in one message. The details that tend to matter most:
- Date and backup date. A second date turns some "sorry, taken" replies into bookings.
- Guest numbers. A range is fine. It decides the room before anything else.
- Event type. Wedding, birthday, corporate dinner, wake, conference. Each has different needs and pricing.
- Format. Seated meal, buffet, standing reception, day meeting.
- Budget, if they will share it. Asked lightly, it stops you sending a premium proposal to a modest budget.
- Contact details and preferred method. Many planners want email so they can compare venues side by side.
Six items, gathered a couple at a time, not a form fired off at once. If you run weddings specifically, an AI receptionist for wedding venues covers the extra questions couples ask.
Speed still decides who gets the booking
Planners and couples usually enquire at several venues on the same evening. The venue that comes back first with a clear answer often gets the viewing. An assistant that captures a complete enquiry at 9pm on a Sunday is only useful if someone replies on Monday morning.
A simple routine does it. Whoever opens up checks captured enquiries first thing, checks the diary for each date, and replies before mid-morning. A morning follow-up routine has a template. If your team already lives in a CRM or Slack, a webhook can post each new enquiry there so nobody needs to check a separate inbox.
Where to begin
Write down your rooms with seated and standing capacities, your catering and bar policies, curfew, parking, accessibility and published packages. Add these as documents or Q&A pairs. Then write the availability rule into the assistant's instructions in plain words: never confirm a date, always capture it with a backup and guest numbers.
Test it by typing in five enquiries from last season, including one for a date you know was booked. If it tries to answer that one, tighten the instruction. To see how a grounded assistant handles this kind of conversation, open the demo.