AI for Event Venues: From Enquiry to Quote Without Missing Details

Turn every enquiry into the same list of fields, let AI mark what is missing and draft one reply that asks for it, check the date against your calendar, build the quote from your rate card, and hand the events manager a one-page brief. The AI drafts and checks; a person approves the quote and sends it.

Most missed details are the boring ones: the finish time, access for set-up, the catering route, the step-free entrance, the second-choice date. The fix is a fixed field list, not a cleverer prompt. A typical case: the 90-guest awards-dinner email below reads like a complete enquiry, yet nine of the 14 fields a quote needs come back missing. The venue, rates and calendar used with it are illustrative, so swap in your own.

Follow me on Instagram@sagnikteaches

An awards-dinner enquiry that looks complete and is not

Imagine a venue with a main hall, a terrace and a kitchen, and an 11.30 pm curfew. Capacity depends on layout and comes from your own capacity documents, not from memory: say 100 for banquet rounds, 120 theatre-style and 140 standing. This is the email that lands on a Tuesday.

Connect on LinkedInSagnik Bhattacharya

Subject: Awards dinner in December?

Hi, we're looking for a venue for our annual awards dinner for around 90 people, on a Saturday in December, probably the 12th or the 19th. We'd want a stage or at least a screen for presentations, a DJ for later, and food, though we haven't decided who would do the catering. Budget is flexible but not unlimited. Could you send prices?

[first name], [company]

It reads like a decent enquiry, and it is missing most of what a quote needs. That gap is the usual reason venues quote twice, or quote once and discover the problem in the week of the event.

Subscribe on YouTube@sagnikteaches

Fourteen fields every enquiry has to fill

The list below is the one I would start from. Each field changes the quote or the diary, which is the test for keeping it. The last column shows how our sample email scores.

The event planner's side of the same exercise, a question list grouped by decision, is in the event planner intake tutorial. For a wedding venue the dates and budgets get misread in specific ways, which the wedding lead qualification tutorial lists.

One page of venue facts, and the topics it bans

An assistant answers questions about your venue from whatever it can reach: the text you pasted, a web page it was pointed at, or its general idea of what venues are like. Only the first is safe. Write one page holding every fact you are happy for it to state, put a review date at the top, and tell it that nothing outside the page counts. It takes an afternoon to write and stops most wrong answers at source.

VENUE FACT SHEET (the only source for facts; review date: [date])
Capacity by layout (from our capacity documents): banquet rounds 100; cabaret 80; theatre 120; standing reception 140
Curfew: music off 23:00, doors closed 23:30; noise limits apply on the terrace after 21:00
Kitchen: in-house catering, or an external caterer with the kitchen access fee; no cooking on site by other suppliers
Access: loading from the rear yard; step-free entrance on the east side; accessible toilets on the ground floor; hearing loop in the main hall
Suppliers: our rule is that outside suppliers send public liability insurance details 14 days before the event
Quotes: valid for 14 days; holds last 7 days unless the manager agrees otherwise
ALWAYS PASS TO THE MANAGER: discounts, charity or repeat-client rates, extensions beyond curfew, anything not on the rate card

The "always pass to the manager" line does as much work as the facts above it. A charity asking for a reduced rate, a repeat client expecting last year's price and a party asking to run on past curfew are all decisions, and a polite assistant is exactly the sort of tool that says yes. Naming them as banned topics turns each one into a hand-over. Revisit the page whenever the rules change, and whenever you refit the hall: a capacity table that predates a new bar counter is how a quote ends up promising seats that no longer exist.

Extraction, then one reply that asks for everything

The first AI job is dull and valuable: read the email, fill the 14 fields, and label each one as given, assumed or missing. The label matters more than the value. "Assumed: 90" and "given: 90" look identical in a hurry and are not. Here is the prompt, and the result for the sample email.

You help an events manager. Read the enquiry below and fill these 14 fields: date and alternatives; event type; guests (min and max); access, start, finish and clear-down times; layout; food and drink route; music and noise; AV and staging; accessibility needs; own suppliers; budget range; decision date; contact and invoice details; how they found us.
For each field write the value and one of: GIVEN (stated in the email), ASSUMED (you inferred it, say how), MISSING.
Do not guess dates, capacities or prices. Do not offer availability.
Then draft one reply, under 180 words, that asks for all MISSING items in a numbered list, most important first.

ENQUIRY: [paste]

1 Date: Sat 12 Dec or Sat 19 Dec - GIVEN (two options)
2 Event type: annual awards dinner, corporate - GIVEN
3 Guests: "around 90"; min and max not stated - ASSUMED 90
4 Times: access, doors, finish, clear-down - MISSING
5 Layout: dinner, presentations, dancing later - ASSUMED banquet rounds plus stage/screen and dance floor
6 Food and drink: caterer undecided - MISSING (in-house or external)
7 Music: DJ "for later"; finish time not stated - MISSING (end time)
8 AV and staging: "stage or at least a screen" - GIVEN, undecided
9 Accessibility: not mentioned - MISSING
10 Own suppliers: not mentioned (DJ probably their own) - MISSING
11 Budget: "flexible but not unlimited" - MISSING (ask for a range)
12 Decision date: not mentioned - MISSING
13 Contact and invoice: first name and company only - MISSING
14 Source: not mentioned - MISSING (low priority)

DRAFT REPLY
Hi [first name], thanks for thinking of us for your awards dinner. We'd be glad to quote, and to get it right first time it would help to know:
1. Timings: when you would like access to set up, doors, the end of the dinner, the DJ's finish and your clear-down.
2. Numbers: your likely minimum and maximum guests.
3. Food: our in-house menu, or your own caterer (and their details if so).
4. Staging: whether you need a stage or a screen would do, and any other equipment.
5. Access: any step-free or other accessibility needs among your guests.
6. Budget: a range you would like us to work to, and when you hope to decide.
I'll check both Saturdays against our diary and come back with availability and a first quote within one working day. Kind regards, [your name]

Notice what the reply does. It asks six questions in one message instead of dribbling them out over five emails, it puts timings first because they drive everything else, and it does not mention the date being free. A first draft of this reply, from a looser prompt, said "our main hall holds 140, so 90 will fit comfortably". That sentence is wrong for this event: 140 is the standing figure, banquet rounds top out at 100, and 90 diners plus a stage and a dance floor is tight. The capacity table in the fact sheet is the only source of capacity figures, and the assistant is told to quote none that is not in it. The manager also has to own the last sentence, since "within one working day" is a promise.

Calendar checks: the AI reads, you decide

A calendar check is pattern-matching on entries, which assistants do well, provided the entries are consistent. Give every entry a status word at the start of the title (CONFIRMED, HOLD with its expiry date, BLOCKED or ENQUIRY), the hours including set-up and clear-down, and the rooms used. Then paste the relevant weeks, or export them, and ask which date works. Here is the export for our two Saturdays, followed by the check.

Fri 11 Dec  09:00-17:00  CONFIRMED  Conference, Main Hall (clear-down by 18:00)
Sat 12 Dec  12:00-17:00  CONFIRMED  Wedding afternoon, Hall + Terrace (clear-down to 18:30)
Sat 12 Dec  all day      HOLD (expires Mon 2 Nov)  Charity dinner enquiry
Fri 18 Dec  18:00-23:00  CONFIRMED  Private party, Terrace only
Sat 19 Dec  nothing booked
Sun 20 Dec  nothing booked

SAT 12 DEC: NOT WORKABLE. A confirmed wedding afternoon runs to an 18:30 clear-down, so set-up could not begin before 18:30, and another enquiry holds the date until Mon 2 Nov.
SAT 19 DEC: AVAILABLE on the calendar. The Friday party uses the Terrace only and ends at 23:00, so the Hall is free for set-up from Saturday morning. Check the Terrace if the dinner needs it.
CAUTION: the calendar shows only logged entries. Confirm there are no unlogged phone holds before offering a date.

Two habits make this safe. First, the caution line is a standing instruction: the assistant must always say what the calendar cannot show, because a verbal hold given on the phone last week is the classic double booking. Second, a turnaround rule goes into the prompt. Something like "at least three hours between one booking's clear-down and the next set-up" lets the check flag tight changeovers that look free on paper.

How the assistant sees the calendar matters. Claude's Google Calendar connector, for example, can create, update and delete events as well as read them, asking for your approval before each action by default, and other assistants' calendar apps have permission settings of their own. Check what yours can do, keep it read-only wherever there is a choice, and never let it place holds on its own. A hold is a commercial decision, and it belongs to the manager. If you want the full picture of calendars, deposits and AI replies inside booking software, the venue booking software tutorial compares the options on exactly those three things.

Building the quote: the rate card does the sums

The assistant should write the words of a quote and never decide a price. Prices come from a rate card you paste into the prompt, and the arithmetic is checked in a spreadsheet. Here is the illustrative rate card. How to set one, including peak dates and minimum spends, is covered in the venue pricing tutorial.

Suppose the client replies with the timings: access at 3 pm, doors at 6 pm, DJ to 11 pm and clear-down by midnight, on Saturday the 19th. That is a nine-hour hire, so three hours beyond the six included. Ninety guests need two supervisors (90 divided by 50 rounds up to 2, which is also the minimum) from doors to the end of clear-down, six hours. The AV package is needed for the presentations. The caterer is still open, so the quote has two options.

Staging is an optional extra at $180, which takes option A to $7,664. A 25% booking deposit, if that is what your terms say, would be $1,871 on option A, with the $500 damage deposit separate. For the budget conversation the assistant can also state the per-head figure: $7,484 over 90 guests is about $83 a head. The prompt that produces this is short and strict.

Build a draft quote from the rate card and confirmed details below. Use only the rate card.
Show each line as: item, working (quantity x rate), amount. Add a total.
If a decision is open (for example in-house menu or external caterer), show two options. List optional extras separately.
If the client asks for anything that is not on the rate card, write NEEDS MANAGER and do not price it.
Never offer a discount or change a rate.
RATE CARD: [paste]
CONFIRMED DETAILS: [paste]

Then check it. Put the same lines in a spreadsheet and compare totals. Assistants occasionally slip on a multiplication, and the most common error is the supervisor count, because the "minimum 2" and "1 per 50" rules interact. If the two totals differ, trust the spreadsheet and look at which line the assistant got wrong. Anything off the rate card goes to the manager: here that means the DJ's power and equipment, decorating access before 3 pm, and any request to run past the 11.30 pm curfew.

A last discipline on the card itself: keep one current version in one place, with a date at the top, and paste from that. A prompt holding last season's rates is the commonest cause of a wrong quote, and it never looks wrong, because the arithmetic is flawless on stale numbers.

A charity quiz night, quoted in the same steps

The 14 fields flex. Picture a smaller case: a charity writes asking for the hall on a Wednesday evening for a quiz night, around 60 people, with a projector and two microphones, doors at 7 pm and everyone out by 10. Catering is "just tea and coffee", and they ask whether you have a charity rate. The extraction marks music, staging and own suppliers as not applicable and sends back three questions: the set-up and clear-down times, who will sign the agreement, and whether they are bringing their own quizmaster equipment. The quote is quicker, and it shows what the assistant does with requests that fall outside the card.

The assistant prices what the card covers: $1,100 for a weekday evening, two supervisors for 60 guests, cleaning and the AV package, which makes $1,824, with the assumed set-up and clear-down times marked for the client to confirm. It writes NEEDS MANAGER against the other two items, the tea and coffee because it is not on the card and the charity rate because it is a concession. Neither gets a number or a yes. The manager might price refreshments per head and decide the charity question on its merits. The assistant's job was to make sure the decision reached a person instead of being answered politely inside a draft.

The hand-off brief for the events manager

By now the facts are scattered across an email thread, a calendar and a quote. The last AI job is to put them on one page, so the manager can pick the file up cold. The structure matters because it keeps given and assumed facts apart, which is where surprises come from.

HAND-OFF BRIEF: awards dinner, 90 guests, [company]
Prepared by: [your name]   To: events manager   Date: [date]

CONFIRMED BY THE CLIENT: Sat 19 Dec; annual awards dinner; around 90 guests; access 15:00, doors 18:00, DJ to 23:00, clear-down by midnight; stage or screen; budget "flexible"
ASSUMED BY US: banquet rounds (capacity 100) plus stage and dance floor; the DJ is their own supplier
STILL MISSING: caterer choice; minimum and maximum numbers; accessibility needs; DJ details; budget range; decision date; invoice details
CALENDAR: Sat 12 Dec not workable (wedding to 18:30 plus a hold). Sat 19 Dec free on the calendar; Friday 18 Dec party is Terrace only. No unlogged holds confirmed yet.
QUOTE (draft, rate card only): option A in-house menu $7,484; option B external caterer $3,494 plus the caterer's own charges; optional staging +$180; damage deposit $500 refundable under our terms
NEEDS MANAGER: DJ power and equipment; decorating access before 15:00; any request beyond the 23:30 curfew
NEXT ACTIONS: approve the quote; decide whether to place a 7-day hold on Sat 19 Dec; follow-up due 2 days after the quote goes out

The hand-off is where the "assumed" label earns its keep. When the manager reads "assumed: banquet rounds, capacity 100", the question "is 90 plus a dance floor really workable?" gets asked on Tuesday rather than on the day. The brief also makes one thing explicit that email threads bury: the next action and who owns it. The contract stage then follows your own terms, and the venue contract tutorial covers deposit, cancellation and damage clauses and the checks to run before a solicitor sees them.

Holds, follow-ups and a second enquiry for the same date

A quote that goes out and is never mentioned again loses to the venue that follows up. The cadence is simple. A short note two days later checks that the quote arrived and offers to answer questions. If a hold is in place, a reminder five days in says when it expires. And a polite close at ten days releases the date. The assistant drafts each from the status in your sheet; you send them, so the deadlines in them are real.

Hi [first name], a quick note that we are holding Saturday 19 December for you until [date], 5 pm. After that we will release it, as we have another enquiry for the same date. If you would like to go ahead, the booking deposit is [amount] and I can send the agreement today. If you need more time or want to change anything, tell me and I will see what I can do. [your name]

Two rules keep these honest. The line about another enquiry stays only if it is true; an invented rival date is the quickest way to lose trust, and the assistant will add urgency happily if you let it. And the policy for two enquiries on one date, such as first deposit wins or first written enquiry gets first refusal, is the manager's decision. The assistant only drafts the message: "that date has a provisional hold; I can add you to a waiting list and tell you at once if it is released".

The same follow-up pattern applies to viewings. The wedding venue viewings tutorial times messages around provisional holds and notes taken after each visit.

Enquiries that do not arrive as tidy emails

Not every enquiry is an email, and the 14 fields still apply. A phone call is the easiest to fix. Right after hanging up, the manager dictates the call into a voice note, in whatever order it was said, and the assistant fills the fields from that, marking whatever was not discussed as missing. The follow-up email then asks only for the gaps, and it reads as a thoughtful recap of the call rather than a form.

An enquiry from a planner or agent on behalf of a client adds two fields that a direct enquiry never needs: who the client is, and who signs and pays. Without them, a quote goes to one party and an invoice to another. Ask for both in the first reply. Any commission arrangement is the manager's decision, so the assistant writes NEEDS MANAGER against it.

A repeat client is the third case. The assistant can pull last year's brief from your sheet to pre-fill the fields, which saves everyone repeating themselves, but it must not quote last year's price. Rates change, and a repeat client who expects the old figure is asking for a concession, which belongs to the manager.

Three failures that look like help

These are the slips I would test for in the first month, each with how it shows up and the fix.

1. Capacity from the wrong layout. The draft says the hall holds 140, a standing figure, for a seated dinner. It shows up as a client who books and then finds the stage and dance floor do not fit. The fix is a capacity table by layout in the fact sheet, with a rule that no other figure is ever quoted.
2. Dates read the wrong way. "Next Saturday" means a different day depending on when the email arrives, and "03/04" is March or April depending on who typed it. The shape of the failure is a hold on the wrong weekend. The fix is to restate the weekday, date and month in every reply and to have the assistant ask when a date is ambiguous.
3. Holds read as free. A calendar entry such as "Charity dinner enquiry" with no status word looks like a free day to a literal reader. It shows up as an offer of a date that a rival enquiry already holds. The fix is the status word at the start of every entry, and the standing caution about unlogged holds.

The measure that matters: details found in the week of the event

Five numbers tell you whether the workflow earns its keep. They come from your inbox, your calendar and your event debriefs, and the values here are illustrative.

The last row is the real test, and it takes a month of debriefs to move. If it does not, look at which field is still being found late; it usually tells you which question is missing from the reply template. Add it, and the next enquiry asks for it up front.

Questions venue managers ask about AI quoting

Can AI send quotes without my approval?

It can if you give it sending rights on your email, but I would not. A quote is a commercial offer with prices, dates and terms, so a person should read it before it goes. Keep the assistant to extracting, drafting and checking, and treat 'needs manager' as the default for anything that is not on the rate card.

Do I need a venue CRM before I start?

No. A shared inbox, a spreadsheet and your calendar are enough to run this workflow. Venue CRMs and booking tools add forms, pipelines and calendar syncing, which become worth paying for once enquiries outgrow a spreadsheet. Do the workflow by hand first, because it shows you which features you would actually use.

How do I stop the AI inventing packages or prices?

Make the rate card the only source of prices, tell the assistant to write 'needs manager' for anything not listed, and check every total in a spreadsheet that does the sums. If the AI's total and the sheet disagree, trust the sheet. A draft that quotes a package you do not sell is a sign the rate card in your prompt is incomplete.

Should a chatbot answer venue enquiries instead?

A chatbot can answer simple questions about hours, capacity, parking and accessibility from your fact sheet. A quote needs details that only a conversation reveals and decisions only a manager can make. Use chat to collect the fields and to book a call or visit, then follow this workflow. Say clearly that it is an automated assistant, and keep a visible route to a person.

Further reads

• Wedding Venue CRM: Which Features Matter and Where AI Helps — Which venue CRM features matter, and where AI adds value.
• Food Truck Booking Software: Screen Private-Event Requests With AI — Seven answers to collect from every private-event enquiry.
• Party Rental Booking Software: Quote and Availability Tools With AI — Quote and availability tools for party hire, with sums.
• Event Venue Marketing: Corporate Away-Day Campaign Written With AI — Fill midweek dates with a corporate away-day campaign.
• AI for Meeting Planners: Venue Shortlists and RFP Replies — The buyer's side: how planners shortlist and ask venues.
• Wedding Venue Newsletter: Seasonal Updates to Past Enquiries With AI — Re-use old enquiries with consent-checked seasonal updates.
• Village Hall Booking System: Can AI Answer Enquiries for You? — A smaller hall's booking system and AI-drafted replies.
• ChatGPT for Event Planning: Strengths, and Where It Gets Facts Wrong — What ChatGPT does well for an event planner, eight kinds of invented fact to check, a calibration test, and a run sheet that names its sources.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Claude's help article on its Google Workspace connectors (calendar actions and approvals); the venue, rate card, capacities and calendar in this tutorial are illustrative.