How to Reply to an Event Request Quickly and Well

Replying to requests is the most important step in selling a venue: the customer usually asks several venues at once and carries on the conversation with the one that replies clearly and specifically. Speed counts, but what matters more is that the first reply contains everything the customer needs to decide and moves things forward.

Fast does not mean short

A one-line "Hello, we'll look into it, let us know!" is fast but leads nowhere. The customer has to write again and ask for the price. A good first reply takes a little longer, but saves three emails back and forth.

Speed does not mean writing faster, it means starting from scratch less often. If every customer asks for the same information, it is worth thinking it through once in advance.

What you need from the request

Before replying, you need to know at least:

• the date and time (and a fallback option);
• the number of guests;
• the type of event and the layout (for example classroom, U-shape, round tables);
• whether catering, accommodation or equipment is needed;
• contact details and how the customer wants the reply.

If half of these are missing, it makes sense to review the request form rather than ask by hand each time. A form that collects this information straight away and shows only free times reduces clarifying emails.

Structure of the first reply

A good reply is simple and follows the same order:

1. The answer to the main question. Whether the date is free and whether the room holds the guests.
2. Price. The total or at least a range, and what it includes.
3. What is missing. One or two questions, not ten.
4. Next step. Coming to view the venue, accepting the quote, holding the date.
5. Deadline. How long you will hold the date.

Leaving out the price is a common mistake. Many venues answer "the price depends" and the customer moves on to where they can see a price. If you cannot give an exact price, say what it depends on and give an estimated sum.

Reply templates (examples)

The texts below are examples you can adapt to your venue. You fill in the parts in brackets yourself.

The date is free

Hello [name]! Thank you for your request. [Date] is free in [room] from [times] and the room holds [number] people in [layout]. The estimated price is [amount] + VAT, which includes [what]. For catering we can offer [options]. I will hold the date for you until [date]. Would [time] suit you to come and see the room, or shall I send the quote by email?

The date is taken

Hello [name]! Unfortunately [room] is already booked on [date]. Free are [two nearest dates] and [alternative room on the same day]. The price is the same: [amount]. If one of them suits you, I will hold it for you until [deadline].

When the date is taken, do not end the reply with "unfortunately". Offer alternatives; sometimes they suit customers perfectly well.

You cannot give the price straight away

Hello [name]! For an exact price I need two more things: [question 1] and [question 2]. As a guide: [room] costs [price] per hour / per day, plus [what]. Once you reply, I will send an exact quote within [time].

Follow-up when the customer goes quiet

Hello [name]! I just wanted to check whether my quote for [date] reached you. I am holding the date until [deadline]. If anything needs changing, such as the menu or the room, let me know.

Send the follow-up after a few days, not straight away. And only once or twice.

Things to have ready in advance

The time usually goes not on writing but on searching. Keep these to hand:

The exact wording of cancellation and deposit terms is a legal matter. Have your lawyer review it.

Channels: email, phone, social media

Requests come from several places and each channel creates its own problem. A phone call goes unrecorded, a Facebook message gets lost and an email sinks under others. A simple rule: a request that arrives through any channel is written down in one place where you can see who is replying and when. If the customer phoned, send a short confirmation email after the call with what was agreed. It is also good evidence if a misunderstanding arises later.

Also think about who replies at weekends and during holidays. If one person's holiday means a week of silence, the customer has already made their choice by then. Even a short automatic reply ("we got your request, we will reply by noon tomorrow") is better than silence, if you keep that promise.

Typical mistakes

• Too many options. Three rooms, five menus and two price lists make the customer wait. Offer one recommendation and say that alternatives are possible.
• Jargon. "Minimum event turnover" means nothing to a customer. Say how many people or how many nights are needed at minimum.
• An unanswered question. If the customer asked about parking, answer about parking, even if it seems unimportant.
• A forgotten promise. If you promised the quote for tomorrow, send it tomorrow.
• An old price. A reply copied from last year often contains the old price. Prices should come from one place, not from old emails.

Where AI fits in

AI can help draft a reply, for example by summarising a request, assessing urgency or preparing the reply text. Prices and dates must still come from your rules and calendar, not from the AI's guess, and a person reviews the reply before it is sent to the customer. More: AI in event venue sales.

Checklist for replying to a request

• Did I answer the main question in the first sentence?
• Are the price and what it includes stated?
• Did I ask only what is really needed?
• Did I offer a next step and a deadline?
• Is the date temporarily held in the calendar?
• Are there no mistakes in the email, such as a wrong name or wrong date?

How Saalo helps

The features include a request form on your site where the customer sees only free times and an estimated price based on your price rules. AI drafts the quote text, the system calculates the amounts and, by default, a person approves. See also the pricing: 30 days are free. For a seminar centre, the article on seminar catering is also useful.