At 8:12 on a Sunday evening, a planner named Dana sits at her dining table with three browser tabs open, a cold cup of coffee, and a board offsite to place. Ninety people, two nights in late March, a private dinner on the second night, one general session and two breakouts. Her CFO wants a number by Wednesday.
Tab one took her to a contact form. She filled it in, got a thank-you page, and has no way of knowing whether it went anywhere. Tab two she called, because the property looked right and she wanted to hear a person say the ballroom holds ninety at rounds of ten. The greeting told her the events office is open Monday through Friday, nine to five, and invited her to leave her name and number after the tone. She did not. Tab three is still loading.
Monday at nine, the events director pours coffee, opens her inbox, and finds Dana’s inquiry sitting third from the top. It is, at that moment, exactly what it was thirteen hours earlier: a message.
That is the problem, and it is not a staffing problem. Every system a hotel or venue owns treats an inbound event inquiry as a message. The web form makes a message. The phone makes a message. The RFP platform makes a message with better metadata attached. A message has one property that matters, a destination. It gets captured, routed, queued, and then it waits for a human to arrive and give it meaning.
An event inquiry is not a message. It is a file.
A message has one property. A file has state.
Open any event file that eventually closed and look at what is actually in it. Dates, with a hold status. A headcount, with a rooming block attached. A budget ceiling the planner will not say out loud but will absolutely enforce. A space configuration: rounds or theater, one room or three, with a resolved capacity against the real floor plan and not the marketing PDF. A food and beverage minimum. A menu. An audiovisual line. A priced proposal. A contract. A deposit. A site visit on somebody’s calendar.
None of that is correspondence. All of it is state.
The entire job of an events office is to open that file and advance it, stage by stage, from a headcount and a hope to a signed banquet event order. Everything the department does is a state transition. Hold the dates. Confirm the room fits. Price the dinner. Send the proposal. Book the visit. Collect the deposit.
Here is what treating the inquiry as a message actually costs: the file does not exist until a human opens it. Not “the file sits idle.” The file has not been created. There is no held date, no resolved capacity, no priced anything. There is a name, a phone number, and a paragraph of intent decaying in an inbox. Thirteen hours of a planner’s decision window pass with the object at stage zero, because the only mechanism in the building that can advance state is a person who is asleep.
The live file is the alternative, and it is a simple idea stated plainly: the inquiry arrives already advanced. Dates provisionally held at 8:14 instead of Monday at 10:30. Space configuration resolved against actual capacity while the planner is still describing the room. A priced proposal assembled during the conversation. A site visit on the calendar before she closes the tab. The human who arrives Monday morning does not inherit a message to process. She inherits a file in motion, with one decision waiting for her judgment.
The difference is not response time. Response time is a message-world metric, and it flatters systems that send a fast, empty acknowledgment. The difference is what stage the object is at when the human touches it.
Nobody can tell you when event inquiries arrive, and that absence is the argument.
We looked hard for a defensible number on what share of event inquiries land outside business hours. Figures circulate. Every one traces back to a vendor citing another vendor, or to an attribution that dissolves the moment you follow it. So we are not going to print one. The Sunday-night inquiry is a narrative premise here, not a statistic, and every operator reading this has lived it enough times that a fabricated percentage would only make it less believable.
But the reason the number does not exist is the interesting part.
The industry has instrumented almost everything else. Occupancy by day of week. Pace against last year. Lead time by segment. Banquet check average by outlet. RevPAR at four decimal places. What it has not instrumented, in any published form, is the timestamp on the front door of its second-largest revenue line.
That is not an oversight. It is a direct consequence of the message model. You instrument objects that have a lifecycle. You do not instrument a message, you just deliver it and mark it read. Arrival time only becomes an interesting variable once you believe something should have happened at the moment of arrival. Nobody measures when the inquiries come in because, structurally, nothing was ever going to happen when they did.
The missing data is the live-file argument proving itself.
Speed is not a service level in this category. It is the competition.
Group sourcing is a race with a small number of finishers, and the race is largely over before most venues have opened the envelope.
Cvent reports that 62% of RFPs are awarded to one of the first three responses. That is vendor-published, from a company that sells sourcing software, and it should be read with that in mind. Amadeus Hospitality reports a similar shape from its MeetingBroker platform data, 72% of first responders winning the business, with no sample size stated. Neither number is a peer-reviewed finding. Taken together, from two vendors with different books of business, they describe a market where order of arrival is doing most of the work that operators believe positioning and pricing are doing.
The tighter number is the one that should reset how an events office thinks about its weekend. In Cvent’s 2026 Planner Sourcing Report, 1,650 professional planners across six regions surveyed in July 2025, the finding for small meetings is blunt. For events with 1 to 50 attendees, 79% of planners say they must receive an RFP response within 6 days or less to consider a venue at all. Of those, 63% need it inside 4 days. And 39% of that group will write off a venue that has not responded within 2 days.
The verb is the finding. Not “prefer a faster response.” Write off. The venue does not lose on price or on the ballroom. It is removed from consideration by a planner who never learns what it would have quoted.
Now put that next to what business-to-business response times actually look like. Harvard Business Review’s 2011 audit of 2,241 US companies found that among firms that responded within 30 days at all, the average response time was 42 hours. Twenty-three percent never responded. Firms that made contact within an hour were nearly seven times as likely to qualify the lead as firms that waited one hour longer, and more than sixty times as likely as firms that waited a day or more. One caveat worth stating: co-author Elkington was CEO of InsideSales, whose data underpins the companion analysis, so the finding is not disinterested.
Hold the two figures side by side. The benchmark for a business inbox is 42 hours. The strictest slice of small-meeting planners writes a venue off at 48. The average response arrives almost exactly as it stops mattering.
And the decay inside that window is steeper than most operators assume, because the mental model is usually “today versus tomorrow.” It is not. InsideSales.com data analyzed by James Oldroyd, PhD, under an MIT byline, covering three years, six companies, more than fifteen thousand leads and over one hundred thousand call attempts, found that the odds of contacting a lead drop by a factor of 100 between 5 minutes and 30 minutes, and the odds of qualifying one drop by a factor of 21 across the same 25 minutes. Vendor-published again, and worth labeling as such rather than dressing up as an academic study. But the shape holds: the expensive gap is not the overnight one, it is the half hour.
The same dataset contains a detail that should be printed on the wall of every events office. The best window to reach a lead is 4pm to 6pm, outperforming the worst block by 114%. Peak reachability is the hour the department is closing laptops and heading for the parking lot.
The social side of the events business tells the same story from the buyer’s chair. Bridebook’s UK Wedding Report 2026, surveying more than 7,000 couples, found that 81% felt frustrated with venue responses at the start of their search. Seventy-nine percent booked their venue within four weeks of first contact, and 92% within two months. The 2025 edition added the part that stings: 59% of couples will not contact a venue at all if pricing is not available online. Platform-published, and a UK sample, so read it as directional. Directionally, it says the decision window is weeks and the qualification window is minutes.
The department carrying a third of the top line is the one still running on voicemail.
This would be a smaller story if group and banquet were a rounding error. It is close to the opposite.
Look at the cleanest non-vendor source available, an SEC filing. Host Hotels & Resorts, the largest publicly traded lodging REIT with 81 hotels, reported that rooms delivered 60% of its 2024 revenues; the split of the rest, roughly 30% food and beverage and 10% other, is our arithmetic from the same filing. The filing defines that middle line itself: food and beverage revenues consist of revenues from group functions, which may include banquet revenues and audio and visual revenues, as well as outlet revenues from the restaurants and lounges at the hotels. Group functions come first in the company’s own description.
The room nights tell the same story. The filed business mix for 2024 across 78 comparable hotels shows just under six million transient room nights against 4.3 million group. That arithmetic is ours, not the filing’s, and it works out to roughly two in five comparable room nights arriving as group. The events office is not a support function. At a full-service property, it is a co-equal demand engine sitting on top of the entire banquet line.
It is also the part that is growing. CBRE Hotels Research, in a November 2025 analysis of 2,669 US full-service, resort and convention hotels plus 866 properties for the first half of 2025, found food and beverage revenue per occupied room up 3.8%, ahead of the 3.0% increase in total hotel revenue. Rooms revenue grew 0.8% over the same half. Host’s own filing points the same direction, reporting comparable food and beverage revenues up $57 million, or 3.6%, driven by improvements in banquet and audio-visual revenues at resort and convention hotels as group demand held through the year.
The honest footnote: that growth is not evenly distributed. In the same CBRE sample, banquet revenue declined 7.3% at convention hotels while rising 8.7% at resort hotels. The banquet business is not uniformly booming, it is migrating. Which sharpens the point rather than softening it, because the properties absorbing that migration are exactly the resorts and independents where the entire events function is two people, a shared inbox, and a phone that rolls to voicemail at five.
Flat rooms revenue. Growing banquet revenue. And the department carrying the growth is the one whose intake layer has not changed since the answering machine.
A live file arrives already advanced.
Run Dana’s Sunday again.
At 8:12 she reaches an agent that talks like a person, which matters for about four seconds and then stops being the interesting part. What happens next is the product. She says ninety people, two nights, late March, private dinner on the second night. The agent checks late March against the dates the property keeps open for groups and marks the two strongest pairs as provisionally held in the file, hers unless the events director says otherwise on Monday. It reads ninety at rounds of ten against the ballroom’s real capacity sheet, not a brochure number, and confirms the two breakouts can run concurrently on the same floor.
Then it shows her. The ballroom appears on her screen, set at rounds, as the agent describes it. The breakout wing. The terrace where the second-night dinner would go if the weather holds, and the indoor alternate if it does not. She is not imagining a room from a description. She is looking at it. This is Flowvue, the layer that renders the property on the guest’s screen on cue, and in an events conversation it does something a brochure cannot: it collapses the site visit’s job of “can I picture ninety of my people in here” into the first four minutes of the first call.
While she is still talking, a draft proposal assembles on the same screen, priced from the rates and minimums the property set. Room block, banquet minimum, audiovisual, a total at the bottom that updates as she adjusts the headcount from ninety to ninety-five. A draft, not a contract; the director turns it into one on Monday. Purely for illustration, call it a $60,000 room block and a $30,000 food and beverage program, a hypothetical $90,000 file, round numbers invented to show the shape. The point is not the figure. The point is that Dana now has a number for her CFO on Sunday night, and the two competing tabs do not.
Then the part that decides whether any of this survives contact with a real week. She walks into the parking garage at 8:29 and the call drops.
At 8:31 she calls back. She does not repeat the headcount. She does not re-spell her name or restate the dates. The file is where she left it, dates still held, proposal still standing, and the conversation resumes mid-state. That is FlowSense, one shared memory across the agent team, and it is the difference between a system that handles calls and a system that holds files. Interruption is the normal condition of a planner’s evening. A file that resets on interruption is not a file, it is a form.
She asks about a site visit. Thursday at 2pm goes into the file before she hangs up, holding its place with everything else that waits on the director’s yes.
Monday at nine, the events director does not inherit a message. She inherits a file at stage three with one decision waiting: approve the hold, adjust the dinner pricing, confirm Thursday. That is a fifteen-minute task with judgment in it. She is not doing intake. She is doing the part a human is uniquely good at, which is winning a piece of business already halfway to a contract.
Talk, show, and remember. Most systems in this category only route.
The math an owner cares about is not response time. It is how many files reach stage three instead of stage zero.
A property that advances the Sunday inquiry to a held date and a priced proposal is competing in the first three responses, where 62% of awards land. A property that advances it Monday at ten is competing for the 38%, on a business line that represents roughly two in five room nights and the entire banquet department at a full-service hotel. The gap between those two positions is not a service improvement. It is which side of the award distribution the property lives on, every week, on the part of the P&L that is still growing while rooms revenue is flat.
The events office was never the bottleneck. Its intake layer was. A message sits still overnight because a message has nowhere to go. A file does not, because a file has a next state, and the next state does not require a person to be awake.
FlowStay is taking pilot properties now, at no cost for 30 days. If you run an events office, bring us your worst Sunday night. We will show you what it looks like as a file.
And on a second night in late March, the weather holds, so the dinner goes to the terrace. Ninety people at rounds of ten under string lights, the bay going dark behind them, the chair on his feet mid-toast. Dana stands at the back wall with a glass she has not touched, watching her CFO laugh at the punchline, and lets herself stop counting chairs. The number he wanted by Wednesday was on his desk Monday at nine. The room she could not picture on a Sunday night is the one she is standing in.