The inquiry lands at 9:40 on a Saturday night, an hour after the proposal, and it asks one thing: whether October 17 is open. By Monday morning that couple has heard back from two other venues and toured one of them Sunday afternoon. The desk phone was never part of the decision.
A date is inventory, and it expires
A venue sells Saturdays. There are fifty-two of them, perhaps thirty inside the season people actually want, and every serious inquiry is a claim on one of them. This is what makes the event business unlike almost every other trade: the product is a specific date, the supply of that date is exactly one, and once it books, every later inquiry for it is worth nothing. An inquiry answered Tuesday is not a delayed sale. It is usually no sale at all, because the couple kept moving over the weekend and something else now holds their date.
The first automatable act is simply answering the question that was asked. An after-hours inquiry can get a reply within a minute that says whether the date is open, offers a short courtesy hold, and links a tour calendar. Not a brochure, and not a promise to be in touch. The date — because the date is the entire conversation.
The buying happens when the office is dark
Engagement season runs from Thanksgiving through Valentine's Day, which means the inquiry surge hits in January, and the asking happens at night and on weekends — after proposals, after tours of competing venues, during a couple's Sunday-evening planning session on the couch. Meanwhile the venue's staff is busiest on exactly those nights, because Saturday night is when this week's event is running. The coordinator is on the floor managing a reception, not watching an inbox. The structural problem is that the buying hours and the working hours are the same hours, and no schedule fixes that. A capture system is how the two coexist.
Qualifying without interrogating
The reply thread can carry the few questions that separate a real prospect from a price-shopper: approximate headcount, whether the date is fixed or flexible, what kind of event it is. Asked one at a time in a text conversation, they feel like planning. Asked as a twelve-field form, they feel like an application, and the couple closes the tab.
The hold, the contract, and the deposit chase
Between "we love it" and a signed contract with a deposit sits the most fragile week in the pipeline. The couple toured, said yes with their faces, and went home — and now the venue is informally holding a Saturday for people who have signed nothing. Every venue has a story about the date that was verbally promised twice.
This is sequence work, and machines are better at it than embarrassed humans. A courtesy hold gets an explicit expiry the couple is told about at the start. The contract goes out with the deposit request the same hour, not the next business day. If the deposit is unpaid at day three, a reminder goes; unpaid at the expiry, a plain message that the hold is releasing. The payment schedule that follows runs on the same rails — the midpoint payment, the balance due before event day — each with its own reminder ladder. None of it requires the coordinator to be the person who nags, which is precisely why it happens consistently instead of whenever someone remembers to feel awkward about it.
The BEO is where the event actually lives
Every catering operation runs on the banquet event order: the one document carrying the timeline, the guaranteed headcount, the menu, the room set, the bar package, the linens, the AV, and each vendor's load-in time. The kitchen cooks to it. The banquet captain staffs to it. When event day goes wrong, the autopsy almost always finds a change the client mentioned — in a text, on a call, in a hallway after the tasting — that never made it into the current BEO. The count moved from 120 to 137, and the kitchen prepped for 120.
The mechanical fix is a single thread of record. When client changes arrive by text or email into one captured channel, each one can be extracted into a proposed revision that a human approves into the working BEO, with versions kept, so the question of which count is current has exactly one answer. The guarantee deadline — final headcount due a week to ten days out — belongs on the same automated calendar as the payments, with the reminder going to the client, not just into the file.
The day before, the call sheet goes out
The florist, the DJ, the photographer, the rental company: each needs the arrival time, the load-in door, and the on-site contact, and each has a slightly different idea of when to show up. The day-before vendor confirmation is tedious and completely mechanical, which makes it ideal work for a system: send each vendor their slice of the BEO, request a confirmed reply, and surface the one vendor who has not replied by mid-afternoon so a human calls that one instead of all six. The failure this prevents is specific and familiar — the rental truck arriving at the locked back door at 7 a.m. while setup waits.
What this does not do
A text thread cannot walk a couple through the room at golden hour, and it cannot taste a menu. The sale still closes on the tour, in person, and nothing here replaces the coordinator who runs a flawless event — it exists to protect her hours for the work only she can do. There is also a precondition worth naming: one calendar of record. If holds live in three places — a wall calendar, a coordinator's memory, and a booking platform — automation will faithfully amplify the confusion and double-book faster than a human could. Fix the single calendar first; automate second.
Where to start
Take last month's inquiries and write two timestamps next to each: when it arrived, and when the first substantive reply went out. Then note which of those dates eventually booked somewhere else. The gap between the columns, held against the lost dates, is the whole case — made with your own numbers rather than anyone's statistics.