Is an automatic reply enough?

It helps, but it is not a reply. An automatic message confirms that the inquiry arrived and says when a person will answer. It does not tell the client whether their date is free, so follow it with a real answer as soon as you can.

What if I cannot answer the question yet?

Reply anyway. Say you have received the inquiry, say what you are checking and give a time when you will come back with an answer. A short reply with a promise you keep beats a long reply tomorrow.

Should I reply to inquiries on weekends?

It depends on when your clients inquire and what you can staff. Many inquiries arrive at weekends and in the evening, so a short acknowledgement and a promised time for the full answer is a reasonable minimum. Decide on a rule and write it down.

How many times should I follow up if there is no answer?

Two or three polite follow-ups spread over a couple of weeks is common. Stop when the client says no or asks you to, and make each follow-up add something, such as a new date option or a tour slot.

How fast should a venue reply to an inquiry?

Reply to a venue inquiry the same business day, and aim for a few hours. The reply does not need to close the sale. It needs to confirm that a person has read the inquiry, answer the question the client asked first (usually whether the date is free), and say what happens next. A fast, specific reply beats a slow, polished one.

Why does reply speed matter for venues?

Inquirers contact several venues at once, and the first useful answer often gets the tour. Research on online sales leads in other businesses points the same way. A Harvard Business Review study of how companies handle web leads concluded that most companies are not responding nearly fast enough.¹ It was not a study of venues, so treat it as a reason to measure your own response time, not as a target for your venue.

Speed also signals how you run events. A client who waits three days for a reply reasonably wonders how you will answer them in the week before their wedding.

What counts as a good reply time?

Set a target you can keep every day, then measure it. A workable structure for a small team:

Same business day for a full first reply.
Within a couple of hours during working hours, for a short acknowledgement.
By the start of the next working day for inquiries that arrive in the evening or at the weekend.

The number matters less than the habit. Write the target down, look at your last 20 inquiries and note how long each one waited. Most venues find a few outliers that explain a lot.

A hand holding a smartphone over a desk with a notebook and a cup of coffee

What should a first reply say?

Answer the question, confirm the details and offer one next step. A first reply that works for most venues does five things:

Thanks the client by name and repeats the event type, date and guest count they gave, so they know you read it.
Answers the date question. Say it is available, or it is taken, and offer alternatives.
Gives one useful fact about the space that fits their event. Not the whole brochure.
Asks for what you need to quote, if anything is missing.
Offers a next step, such as a tour with two or three suggested times. When the client is ready for numbers, send a proposal.

Keep it short enough to read on a phone. Attach your price list or link to it only if you are happy for it to be the first thing the client reads; the rate card guide explains how to build one.

How do I cover evenings and weekends?

You have three options, and you can combine them. An automatic acknowledgement that says when a person will answer. A shared inbox that more than one person watches. And a short list of reply templates for the situations you see every week, so a reply takes two minutes rather than twenty.

Be honest in the automatic message. Do not promise a reply time you cannot meet. If you promise "within one hour" and then answer the next day, the automatic message made things worse.

Which situations need a prepared reply?

Most inquiries fall into a handful of situations. The venue inquiry reply email templates cover ten: a date that is available, a date that is taken, a budget that is too low, an after-hours request, a follow-up after three days of silence, a corporate inquiry, a tour follow-up, a post-event thank-you, a first reply to a new inquiry, and a request for the details you need to quote.

Each comes in a warm, a professional and a short version. You fill in merge fields such as the client's first name, the event date and your tour link, then copy the text into your own email or download the set as a Word file or PDF. The templates contain no prices, response times or policies, so you add your own before sending. The tool writes the text only. It does not send email or watch your inbox.

When should I follow up?

Follow up if you have not heard back after about three days, and make the follow-up useful. Offer a second date, a tour slot or an answer to a question you suspect they have. "Just checking in" gives the client nothing to respond to.

After two or three follow-ups over a couple of weeks, stop. Leave the door open with a short note that the date is held until a certain day, and then release it.

How do I check if my website makes replying easy?

A slow reply is sometimes a form problem. If the inquiry form does not ask for the date and guest count, your first reply has to ask for them, which adds a round trip. Our guide to getting more inquiries from your website covers the form in more detail. The free Venue check looks at your public website and your Google listing and reports on things like whether you have an inquiry form, whether it asks for date, guest count and event type, and whether the homepage has a clear call to action. VenueDirector is in early access, and you can join the list on the home page. [REVIEW]

James B. Oldroyd, Kristina McElheran and David Elkington, "The Short Life of Online Sales Leads", Harvard Business Review, March 2011, https://hbr.org/2011/03/the-short-life-of-online-sales-leads. The article opens: "Our research shows that most companies are not responding nearly fast enough." [REVIEW: the article's specific response-time figures were not read in full and are not quoted here.] ↩