The HoneyBook inquiry process, done right.
The inquiry stage decides more bookings than your pricing does. Here’s how to set up HoneyBook so every lead gets a fast, warm reply and the right information, without you living in your inbox.
Written by Sydney Young, HoneyBook Pro & Template Partner.
Where this sits in the client journey
New to HoneyBook?
This guide assumes you've already got a HoneyBook account with the basics in place. Starting from zero? Walk through the full setup guide first — brand, services, your first Smart File and payments — then come back here to layer on this stage's playbook.
Jargon, decoded
{ in any text block to insert one.The five steps
From first click to booked call.
Build one inquiry form, not five
Replace scattered contact forms across your website, Instagram bio and email signature with a single HoneyBook inquiry form. Ask only what you need to qualify a lead: event date, event type, guest count, budget range, and how they found you.
Why it matters: A shorter form gets more submissions, and one form means every lead lands in the same pipeline instead of scattered across your inbox.
Set an instant auto-responder
The moment someone submits, HoneyBook can fire an automatic reply confirming you’ve received it and setting expectations for when you’ll follow up personally, ideally within 24 hours, often same-day.
Why it matters: Couples and event clients inquire with several vendors at once. The first warm, professional reply often wins the booking before pricing even comes up.
Qualify before you quote
Use the form answers to sort inquiries by fit, right budget, right date, right vibe, before you spend time on a custom proposal. HoneyBook’s pipeline lets you tag and filter leads so the best-fit ones rise to the top.
Why it matters: Sending a full proposal to every inquiry, including poor fits, is the single biggest time drain in the booking process.
Send a real, personal reply
Once you know it’s a good fit, send a short, warm personal message, not just a template, referencing something specific from their inquiry. This is the message that gets them on a call or straight to a proposal.
Why it matters: This is the human touch that no automation should replace: it’s where trust actually starts.
Track every lead until it’s answered
Use HoneyBook’s pipeline stages (New Inquiry, Contacted, Call Booked, Proposal Sent) so nothing goes quiet by accident. A lead that goes unanswered for a week is a lead you’ve likely lost.
Why it matters: Most missed bookings aren’t lost to competitors, they’re lost to silence and disorganization.
Ready for the next stage? Once a lead is qualified and warm, move to the booking process: proposal, contract and invoice.
Beyond the five steps
Where this stage actually goes wrong.
Mistake: Sending the same pitch to every inquiry, good fit or not.
Instead: Let the form answers sort leads by fit before you spend time writing anything custom.
Mistake: Hiding all pricing until a call happens.
Instead: Share a starting range up front. It filters out budget mismatches before either of you spends time.
Mistake: Treating the instant auto-responder as the whole reply.
Instead: Still send a short, personal follow-up referencing something specific from their inquiry.
Mistake: Not tracking which pipeline stage a lead is sitting in.
Instead: Use pipeline stages as your cue to follow up, so nothing goes quiet by accident.
When the playbook needs to flex
A few situations that don't fit the template.
"Just exploring" inquiries: No date yet, just gathering info. Don't chase these like a hot lead — tag them as nurture and let a lighter-touch automation handle it.
Two inquiries, same date: Friends or family of an existing client sometimes inquire for the same weekend. Flag it internally early to avoid an awkward availability surprise later.
Inquiry via DM or phone call: Manually create the Project in HoneyBook so it still enters your pipeline, instead of living only in a text thread you'll lose track of.
Steal the framework
The exact checklists & prompts I use.
This is the same framework I hand private clients inside The Systems Academy — built here for wedding and event pros, ready to copy straight into HoneyBook.
Quick primer on the automation language below: a Trigger is the event that starts things off, a Wait adds a delay, a Condition branches the path, and an Action — like sending an email — is what actually happens. That's the whole of HoneyBook's Automations 2.0.
Auto-responder
Fires instantly when a lead form is submitted.
Pricing guide
A Smart File built once, reused for every inquiry.
Follow-up sequence
Waits + conditions that catch leads who go quiet.
The instant auto-responder
The email that fires the moment someone submits your inquiry form. Paste it in as-is, or tweak the tone.
Lead form submittedyour inquiry/contact form
5 minutesoptional — feels personal, not robotic
Send emailselect this template
Save the copy above first: Templates → Emails → New Template. Then go to Automations → Create Automation, set the trigger and action above, and Activate.
Pro tip: Keep it under 100 words. A long auto-reply reads like a form letter; a short, warm one reads like a person who's genuinely excited.
Your pricing guide & packages
The whole Smart File, written and ready — intro, three packages, and a next-steps CTA. Swap in your real prices and details.
Build it under Templates → File Templates → New Template, then save it as a reusable Smart File template so every future lead gets it in one click.
Pro tip: Always show a starting price or range, even a rough one. Guides that hide all pricing get fewer serious replies, not more — people self-select out before they ever message you. Cap it at three tiers, too — a fourth option tends to make couples freeze instead of choosing.
The inquiry response email
What you send after reviewing a good-fit inquiry — book a call, or point them to pricing.
This one's usually sent by hand, not automated — it's the personal touch. In Automations 2.0 you can still save it as an email template so it's one click away.
Pro tip: Reference one specific detail from their inquiry — their venue, their date, their vibe — in the first line. It's the fastest way to prove a human actually read their message.
The 3-email follow-up sequence
For leads who go quiet after your pricing guide.
Smart file sentyour pricing guide
3 days
Smart file not completedbranch: not yet
Send emailFollow-up 1
Repeat with longer waits (5 days, 9+ days) and the same "not completed" condition for Follow-ups 2 and 3 — each checking the file is still incomplete before it sends.
Pro tip: Space these at least 3–4 days apart. Back-to-back follow-ups read as pressure, not care — and pressure is what makes leads go quiet for good.
Ready to stop losing leads to silence?
Start a free 7-day trial and lock in 30% off your first year through my HoneyBook Pro link.
Get 30% off HoneyBook →
Questions
The inquiry stage, answered.
How fast should I reply to a HoneyBook inquiry?
Aim for an automatic acknowledgment within minutes, and a personal reply within 24 hours. Wedding and event clients often inquire with multiple vendors at once, so response speed is a real competitive advantage.
What should my inquiry form ask?
Keep it short: event date, event type, guest count or scope, budget range, and how they found you. Enough to qualify a lead without creating friction that stops people from submitting.
Should I quote pricing before a call?
Many wedding and event pros share a starting-price range in their auto-responder or a linked pricing guide, then save custom numbers for after a discovery call. This filters out budget mismatches early.
What if a lead goes quiet after my first reply?
Set a follow-up reminder for 3–5 days later with a brief, no-pressure nudge. Many bookings come from a second or third touch, not the first message.
What's the difference between a Trigger and an Action?
A Trigger is the event that starts an automation, like a lead form being submitted. An Action is what happens as a result, like sending an email. Automations 2.0 also supports Waits (delays) and Conditions (branches) between them.
Keep reading