The deposit reminder sitting in the outbox already has the amount and the payment link. The call that starts when someone says that amount is wrong does not have a template.
The acknowledgement can leave without a person in the loop. So can the chase, while the file is still quiet, and the reminder that the deposit is due. Reading whether the inquiry is real stays with a named person. So does cutting a line on the quote or handling a dispute, while the machine takes care of the waiting.
What the machine can send without a person in the loop
An acknowledgement that leaves within a minute, with the first name, the date and the event type, and one line that says when a real answer will come. That is all it is: it does not pretend the room is free, and it does not quote a price.
A first answer still has to leave within the hour in business hours, and never later than 24 hours. The automatic note is the placeholder, not the answer. The quote itself is still written by someone who opened the diary.
Then the chase. After the quote goes out, a planner comparing a Saturday wedding in the Cotswolds with two London rooms and a country house will not answer the first nudge, and a sequence that cannot stop itself when they finally write, or when that Saturday is cancelled, does more damage than a quiet sent folder. Silence is normal. A run of three to four contacts over two to three weeks, then a clean close, is what we see hold.
Each message dies the moment they reply, sign, or the file changes status. The channel-by-channel pace sits in our note on following up without being a pest. One extra rule here: every chase carries one thing the last one did not, such as a floor plan, a 48-hour hold or a line on the loading dock. "Just checking in" adds nothing.
The third safe job is the deposit reminder. Amount, due date, payment link. On most files we see, the first payment is 30 percent at signature, sometimes 50 percent on a wedding or a Saturday everyone wants. The reminder is a clock, not a judgement on whether the clause is fair.
A shared inbox tied to the file is enough to send those three from the thread, without copying the name onto a side sheet.
- Acknowledgement: received, named, dated, and when a person will write back.
- Quote chase: three to four contacts, two to three weeks, stop on any reply.
- Deposit reminder: amount, date, link. Kill it if paid or cancelled.
- Optional, after the night: a review request two days later, and only if the event actually happened.
- Prep tasks a week out: caterer brief, floor plan, confirmed headcount. Tasks for the team. Not more mail to the planner.
What still needs a name on the line
Hearing that the £8,000 "budget" on the form is a wish, and the real number sits closer to £12,000, takes a conversation. Same for a Tuesday offsite that needs the room next door kept empty. No merge field catches that.
The tour is still half the sale. Someone walks the room and answers the dock question. Holding the date for 48 hours is a judgement call, not a default on the form.
Negotiation needs a person. Waiving part of the beverage package on a grey Tuesday in February is a margin call, not a rule you encode. A Cotswolds Saturday and a 40-person Midtown breakfast do not share a discount logic. Write the floor down. Do not put it in an automatic reply.
Disputes, last. An unhappy client who gets an automatic "we hope you are well" becomes a worse one. Call the same day. Anything that touches money already taken, reputation, or a clause in the signed paper stays off the sequence.
A chase you can defend
Oldroyd, McElheran and Elkington, in The Short Life of Online Sales Leads (Harvard Business Review, March 2011), wrote that most companies are not responding nearly fast enough. The study looked at online sales inquiries rather than banquet rooms, but the lesson for a venue is still speed on the first touch, then a written chase, not a folklore of five-minute multipliers copied from another industry.
Our working numbers are simple: a first reply within the hour during business hours, the next day at the latest. Three to four contacts across two to three weeks after the quote, then an explicit close. Corporate files often sit 20 to 30 days from inquiry to signature. A low signature rate usually means the first answer is late, or the inquiries were never real.
| Job | Software | A named person |
|---|---|---|
| Acknowledgement | Send in a minute: name, date, type, when a real answer comes | Decide the inquiry is worth a quote at all |
| Quote chase | 3 to 4 contacts over 2 to 3 weeks, stop on reply | Add the floor plan, the hold, or the dock note |
| Deposit reminder | Amount, date, link, stop if paid or off | Call when they dispute the figure |
| Site visit | Calendar hold | Walk the room |
| Discount | Never | Cut food and drink, not the room, if you cut at all |
| Complaint | Kill every sequence | Phone. Same day if you can. |
Reply, reminder, or a sales pitch
An acknowledgement of an inquiry they just sent is a reply. A deposit reminder on a signed file is usually a transactional note. A fourth chase that starts selling next December's party to someone who never booked is a different animal.
In the United States, the FTC's CAN-SPAM compliance guide treats commercial email as any message whose primary purpose is advertising a product or service, including business-to-business mail. It asks for an accurate from-line, a real postal address, and a working opt-out honoured within ten business days. Transactional messages sit in a narrower box: they confirm or complete a deal already agreed.
In the UK, the ICO's PECR guidance on electronic mail marketing says you must not send marketing emails to individuals without specific consent, with a limited soft opt-in for your own previous customers. You can email corporate bodies, but it is good practice to keep a do-not-email list of companies that object. Sole traders are treated as individuals.
The desk test is dull. If the message answers their request or collects money already agreed, keep it short and stop it on reply. If you are offering a new date or a new package they did not ask for, treat it as marketing and put the opt-out in.
Switch on one rule, then stop
Do not switch on five sequences on a Monday. Measure two weeks as they are: time to first reply, how many quotes actually got a chase, how many deposits were late because nobody asked. Then turn on the acknowledgement alone and leave it for fifteen days before reading what went out.
Then add the chase. Then the reminder. An event venue CRM such as Joinways can sit on those three without a side sheet. What matters is the before-and-after number on first-reply time, not the brand on the login screen.
Ten minutes on Friday looking at what actually left is enough. If you would not sign the message with your own name, it stays in draft. Sequences die the first time they reply, or the file is signed, cancelled, or they ask you to stop.
Questions venues actually ask
- Can I automate acknowledgements without looking like a robot?
- Yes if the note is short, uses their name, date and event type, says when a person will write, and is signed by a real teammate. Generic "dear guest, your request is important" is what people spot. The automatic part is the send time. The copy still has to be yours.
- How many times should a venue chase a quiet quote?
- On the rooms we see, three to four contacts across two to three weeks, then a last message that closes the file. More than that usually means the sequence never stops on reply. Fewer means the quote dies in the sent folder. Channel detail is a separate decision.
- Should deposit reminders be automatic?
- The clock can be, but the argument cannot. Send amount, date and link before the due date, and kill the reminder the moment it is paid or the event is off. If they dispute the figure, a person calls. That is a clause conversation, not another email from the sequence.
