A couple gets engaged in December. By January they've decided they need a planner. On a Tuesday night, around eleven, they sit down with a laptop and message eight of them.
Some of those eight will reply within the hour. Some will reply in three days. And the ones who reply late are competing against planners the couple has already had a conversation with, already warmed to, and possibly already booked a call with.
The same pattern runs in corporate events, just with different timing, an events manager with a brief and a deadline contacts several agencies in one afternoon and shortlists whoever responded most competently.
The consultation is expensive
Here's what makes event planning different from most service businesses: the discovery call is a real cost. An hour of your time, plus preparation, plus the follow-up proposal. And a large share of them are with people who were never going to book: the budget was a fraction of your minimum, the date was one you're already committed on, or they wanted a venue-finder rather than full planning.
So you have two problems that pull against each other. You need to respond fast, because speed wins enquiries. And you need to respond selectively, because consultations don't scale.
A chatbot resolves that tension by doing the qualification before the calendar gets involved.
Three questions that decide almost everything
The date. Obvious, and the fastest disqualifier. If you're already booked that weekend, nothing else matters. Capturing it in the first exchange means you can decline gracefully and immediately rather than three days later.
Guest numbers. A 40-person intimate wedding and a 250-person marquee event are different products, different pricing, and often different planners within a team. Corporate equivalents are the same, a 20-person board offsite and a 600-delegate conference share nothing but a category name.
Venue status. Have they booked one? This tells you which service they actually need. A couple with a venue booked wants coordination; a couple without one wants a full planning service that starts much earlier and costs much more. It also tells you how far along the decision is.
Three questions, ninety seconds, and you know whether this is a real opportunity.
The budget question
Most planners are uncomfortable asking about budget early, and understandably. It can read as mercenary before a relationship exists.
But the alternative is worse. An hour-long consultation that ends with a client discovering your fee is four times what they had in mind wastes their time as much as yours, and often ends with them feeling embarrassed. That's not a good experience for anyone.
A bot can ask it in a way that's genuinely easier than a person can, because it's framed as routing rather than judgement: "Roughly what budget are you working with overall? It just helps me point you toward the right package."
People answer that question honestly to a chat window far more readily than to a human on a phone call. And an honest number early means either a well-matched consultation or a polite, quick "we're probably not the right fit, but here's what a planner at that level would typically cost", which, incidentally, generates a surprising amount of goodwill and referral.
Planners who add the budget question at first contact usually see consultation volume fall and booking count stay flat. Same bookings, considerably less of the calendar spent getting there.
Corporate needs a different branch
After the first question, weddings and corporate diverge completely.
Corporate enquiries need: what's the event for, headcount, date or date window, location or region, whether there's a budget approved, and who signs it off. That last one matters more than any of the others, an enquiry from someone who has to get sign-off from three people is a longer process than one from the person holding the budget.
They also need routing to whoever handles commercial work, which in most planning businesses is a different person with a different follow-up rhythm.
Set the branch at the first question and let the two paths run separately.
What it has no business doing
Don't let it confirm availability. Your diary is the constraint, and a bot that says "yes, we're free that weekend" when you're not creates a problem that's very hard to walk back with a couple planning a wedding.
Don't let it quote a fee. Event planning fees depend on scope, and a number given without understanding the scope will either lose you the job or trap you at the wrong price. It can share your starting points and package structure, which is enough.
Don't let it run the whole conversation. Events are bought on trust and personal fit. The bot's job is to get a qualified enquiry to you fast, with the basics gathered, so the conversation you have is about the event rather than the logistics of the enquiry.
Tone matters more here than most places
A wedding enquiry is emotional. A bot that responds like a support ticket system sets the wrong expectation for what working with you feels like.
Configure warmth deliberately. Congratulate them. Keep it short. Offer the handover early and clearly, with a realistic timescale. "I'll pass this to [name], who'll come back to you within a day."
Getting it running
Point it at your website so it learns your services, packages, past events, and whatever pricing structure you publish. Add your current booked dates if you're comfortable, or at least your capacity position.
Set the capture fields per branch. Set the budget question wording carefully. It's the one line worth writing yourself rather than leaving to a default.
Checking the payoff
Track two ratios. Consultations booked per enquiry should fall, and that's the point. Bookings per consultation should rise sharply.
The volume of your enquiry pipeline probably won't change much. What changes is how much of your calendar it consumes, and in a business where your time is the product, that's the number that matters.