Yes. AI can read a wedding enquiry, pull out the date, budget and guest count, check the date against your calendar, and sort the lead into "book a call", "send pricing" or "reply kindly and refer on". It works best as a sorter that routes every couple somewhere, not a gatekeeper that silently rejects, with the thresholds set by you.
The catch is that couples rarely give clean numbers. "Around 100, maybe 120 with evening guests", "next summer sometime" and "budget flexible" are normal. A stated budget usually means the whole wedding, not your part of it. Extracting the three fields is easy for current AI models; interpreting them well is where most set-ups go wrong, and it's fixed with written rules rather than a better tool.
Write down what "qualified" means for your business first
Before any AI touches an enquiry, turn your gut feel into rules. Here is a filled-in set for an illustrative wedding photographer whose full-day package starts at $3,200:
| Field | Book a call | Send pricing | Refer on kindly |
|---|---|---|---|
| Date | Free in the calendar | Free, or date not yet fixed | Already booked, and not flexible |
| Photography budget | $3,200 or more, or not stated with a total wedding budget over $30,000 | $2,000 to $3,200, or not stated | Under $2,000 (offer the short-ceremony package or a referral) |
| Guest count | Any (affects hours, not fit) | Any | n/a |
| Venue | Within 90 minutes' drive | Further, travel fee applies | Overnight travel you don't offer |
Notice guest count barely matters for this photographer, but it's the most important field for a venue (does it fit the room?) and a caterer (price per head). The same three fields carry different weight for every supplier, which is why a generic "lead score" from a tool is a poor substitute for your own table. For the general idea of scoring leads, see what AI lead scoring is and whether a small business needs it.
How the AI pulls three numbers out of a messy enquiry
A realistic enquiry, arriving through a wedding directory's contact form in December:
Hi! We're getting married next June, probably a Saturday but could do Friday if cheaper. Around 90 for the day and 130 in the evening. Venue is the old mill we saw last week (not booked yet). Our budget for everything is about 28k and we'd love someone relaxed who's good with families. Is there any chance you're free? Thanks, [names]
The prompt, used in a chat assistant or an automation step:
Extract these fields from the wedding enquiry below. Today's date
is [date]. Reply only in the format shown.
wedding_date: exact date if given; otherwise month and year, and
say "not fixed"
day_flexibility: any days or dates they'd accept
guests_day: number or range
guests_evening: number or range, or "not stated"
budget_stated: amount and whether it is for the whole wedding or
for this service
venue: name if given, and whether it's booked
notes: anything that affects fit (style, requests, concerns)
unclear: anything you had to guess
Enquiry: [paste]An illustrative output:
wedding_date: June 2027, not fixed
day_flexibility: Saturday preferred, Friday possible
guests_day: 90
guests_evening: 130
budget_stated: about $28,000, whole wedding
venue: "the old mill", not booked
notes: want a relaxed style, good with families; price-sensitive
(asked about Friday "if cheaper")
unclear: "next June" assumed to be June 2027 because the enquiry
arrived in December 2026This is a good extraction, and the "unclear" line is the most valuable part: it tells you what to confirm. What you'd fix: under the rules above, a $28,000 total budget with no photography figure falls just under the $30,000 line, so it goes to "send pricing", but the couple mentioned Friday "if cheaper", which suggests price matters. A human would probably send pricing with the weekday rate highlighted. Put that in the rules: "If they ask about cheaper days, include the weekday rate."
Five ways dates, budgets and guest counts get misread
- The year. "Next June" sent in December means the June after next for many couples, but in February it means this coming June. Always give the AI today's date and ask it to flag assumptions.
- Whose budget. "Our budget is 28k" is almost always the whole wedding. If the rule compares it with your package price, every couple looks rich. Keep "whole wedding" and "for this service" as separate fields.
- Shorthand numbers. "28k", "25-30", "under 5" and "5,000ish" all need turning into numbers. Models handle these well, but "under 5" from a couple who mean $5,000 for photography can be misread as five guests. Ask for the unit alongside the figure.
- Day and evening guests. A venue with a 100-seat room can host 90 for dinner and 130 for the evening in many layouts, or not at all in others. Extract both numbers and let your rules decide.
- Dates in other formats. "06/07" is June or July depending on where the couple is from. If a date is in numbers only, have the AI mark it as unclear and ask the couple to confirm in words.
Directory leads add a sixth problem of their own: the form fields and the message disagree. A realistic one arrives as "Wedding date: 01/01/2027 | Guests: 50 | Budget: Not specified", followed by a message that says "we're looking at a Saturday in May, about 120 guests, and we've set aside around $3,500 for photos". The form values are the directory's defaults, left untouched by a couple who typed everything in the message box instead. An extraction step that trusts the form puts this couple on New Year's Day with 50 guests and no budget. Add a line to the prompt: "If the message text and the form fields disagree, use the message text and list the conflict under unclear." Then check a few directory leads by eye each month, because directories change their form layouts without telling you.
Setting it up: three levels of effort
Level 1: a better enquiry form
Much of the "AI qualification" problem disappears if your own form asks the right questions with the right field types: a date picker with a "not fixed yet" option, a budget dropdown with ranges for your service, separate day and evening guest numbers. Form builders with conditional logic can show your weekday rate to anyone who ticks "flexible on day" and route couples to different thank-you pages by budget range. Tally, for instance, includes conditional logic on its free plan. This doesn't help with directory leads and emails, which is where levels 2 and 3 come in.
Level 2: features in your wedding CRM
Some client-management tools built for wedding and creative businesses now include AI lead features. HoneyBook, for example, has priority lead notifications, which predict which enquiries are likely to book or be high-value using the lead source, project type, budget and date alongside your own booking history. HoneyBook says it needs at least 20 enquiries through its contact or lead forms before it starts sending them, and the setting sits under Company settings, then HoneyBook AI, then Lead management. If you already use a CRM like this, switch on what's there and compare its picks with yours for a month before building anything.
Level 3: extraction and routing with an automation platform
For enquiries arriving from several places (directories, email, Instagram, your form), an automation platform can run the extraction prompt on each one, check the date against your calendar, apply your rules and label the lead in your inbox or CRM. On Zapier, an AI step uses 1, 3 or 5 tasks per run depending on the model tier (or 1 if you connect your own API key), and paid plans start at $19.99 a month billed annually for 750 tasks. At 40 enquiries a month, the sum is small: the trigger costs nothing, the AI extraction step 3 tasks on a middle tier, the calendar lookup 1, a filter or paths step nothing, the CRM label 1 and the draft reply 1, so about 6 tasks per enquiry and 240 a month, comfortably within the entry plan. Keep the final reply as a draft for you to send, at least for the first two months.
Route, don't reject: three tiers and what each gets
Every couple gets a reply within a few hours. What changes is the content. Filled-in examples for the photographer above:
Book a call (date free, budget fits):
Hi both, congratulations! Good news: I'm free on Saturday 12 June.
From what you've told me, the full-day package ($3,200) would cover
you from getting ready to the first dance. I'd love to hear more
about the day - here are three call times this week: [links].
[first name]Send pricing (date not fixed, or budget unclear):
Hi both, congratulations, and thank you for thinking of me.
June is filling up, but I still have several Saturdays and most
Fridays free. My packages start at $2,400 for ceremony and
portraits, with Friday weddings at a lower rate: the price guide
is attached. Once you've fixed the date, reply and I'll check it
straight away. [first name]Refer on kindly (date booked, or budget well below your smallest package):
Hi both, congratulations! I'm so sorry, I'm already booked on
12 June. Two photographers I'd happily recommend are [name] and
[name]. If your date changes, let me know and I'll check again.
[first name]One edge case the calendar check must handle: two couples asking about the same Saturday in the same week. If the check looks only at confirmed bookings, both get "good news, I'm free", and the second one to sign is disappointed. Count pending holds as well as bookings, and have the AI add "another couple is holding this date" to the tier note so you can reply honestly: "I have one other enquiry for that date, so I can hold it for you until Friday." Couples generally take that well; finding out after they've paid a deposit elsewhere, or after you've double-promised, they don't.
A reply in every tier protects your reputation in a small industry where couples talk and suppliers refer each other. If you want replies going out within minutes rather than hours, replying to wedding enquiries in minutes with AI covers the drafting side.
Enquiries a person should always read first
Some enquiries shouldn't be sorted by rules at all, because the details that matter aren't date, budget or guest count. Tell the AI to flag these for you and send nothing automatically:
- Anything mentioning illness, a bereavement or a rushed date. "We've brought the wedding forward because Dad is unwell" needs a personal reply, and possibly flexibility on your usual terms.
- Accessibility needs. A guest in a wheelchair or a couple with a hearing impairment may change how you plan the day. The reply should come from someone who can answer properly.
- A previous supplier who let them down. Couples who were dropped by another supplier weeks before the date are stressed and often ready to book fast, but they need reassurance, not a price list.
- Very large or unusual events. Multi-day celebrations, 300-plus guests or a ceremony in an unusual setting rarely fit your standard tiers.
- Enquiries from other suppliers or planners. A planner sending you three weddings a year deserves a direct reply from you, whatever the budget line says.
In practice these are a small share of enquiries, and they're often the ones that turn into your best reviews.
Test it on last season's enquiries first
Before a new couple sees any of this, run the rules against enquiries you've already dealt with. Export or collect last season's enquiries, remove surnames and contact details, and run each through the extraction prompt and your rules. Then compare the tier the AI assigned with what actually happened.
Illustrative numbers: from 60 past enquiries, 14 booked. The AI put 11 of those 14 in "book a call", 3 in "send pricing" and none in "refer on", which is fine, since "send pricing" still gets a warm reply. But it also put 4 couples in "refer on" whose dates were in fact free: the calendar check misread "the 5th" as the wrong month in two cases, and two had budgets stated per person. Two of those four had gone on to book with you last season. That's the result you want from a test: two fixable errors found before any real couple was turned away.
If you're on a CRM with its own lead predictions, run the same comparison against its picks. An illustrative month: the CRM flagged 9 of 31 enquiries as priority; your rules put 11 in "book a call"; 7 were on both lists. The 6 disagreements are the interesting part. Read each one and ask which call you'd have made. If the CRM keeps flagging couples with big total budgets but weekday dates you rarely book, it is learning from your history differently from how you want to run next season, and your written rules should win.
Repeat the test after any rule change. Once the tiering matches your own judgement on at least 9 in 10 past enquiries, switch it on for new ones, still with you approving each reply.
How a venue and a band set different rules
For a wedding venue, the order of the fields flips. Date comes first, because a booked date ends the conversation. Guest count comes second, checked against both the ceremony room and the dining layout; "90 day, 130 evening" might fit one package and not another. A filled-in capacity rule for an illustrative barn venue:
Ceremony room: up to 120 seated.
Dining: up to 100 at round tables, 110 at long tables.
Evening: up to 180 standing.
Rules:
- Day guests 1-100 and evening up to 180: book a viewing.
- Day guests 101-110: send the long-table package; note it in the tier.
- Day guests 111-150: send the marquee option (extra cost) and pricing.
- Day guests over 150 or evening over 180: refer on kindly.
- Guest count "not sure yet": send the brochure and ask for a range.Run the old-mill enquiry from earlier through it and the answer is immediate: 90 day and 130 evening fits the standard package, so the couple gets a viewing slot. An enquiry for "about 140 for the meal" gets the marquee option rather than a refusal, which keeps a couple who might otherwise have gone elsewhere without asking. Budget matters less early on, because venue pricing is usually published by season and day. The first reply often includes the right brochure for their season and a viewing slot, which is where how wedding venues use AI for viewings and follow-ups picks up.
For a wedding band, date and venue matter most: a free date and a venue with an evening noise limit or a sound limiter can make all the difference, and guest count only affects whether they bring the larger line-up. The extraction prompt is the same; the rules table is different. A band's most useful addition is a short venue notes list the AI can check the venue name against: "[venue]: sound limiter, amplified music must stop at 11pm, load-in via a narrow side door, no stage". With that list, an enquiry for a Saturday at that venue goes to "send pricing" with the acoustic or reduced line-up and a note about the limiter, instead of "book a call" for the full six-piece. A venue the list doesn't know gets flagged as unclear, and the first reply asks the couple one question: "Has the venue mentioned any noise or sound limits?" That single line saves the awkward conversation three months later when the coordinator sends the band the venue rules. Whatever your service, the mistakes are usually the ones in AI mistakes that put couples off a wedding business, and nearly all of them come from replies that feel automatic rather than from the sorting itself.
Qualifying wedding enquiries with AI: more questions
Will couples be put off by an automated first reply?
Not if it's fast, specific and clearly leads to a person. Couples mostly want to know quickly whether you're free and roughly what you cost. A reply that confirms their date is available, gives your starting price and offers a call time does that. What puts them off is a vague template or a reply that ignores the details they gave.
Is it unfair to screen couples by budget?
Being clear about your starting price early is kinder than a long email exchange that ends at a figure they can't afford. The unfair version is silently ignoring low-budget enquiries. Send every couple a reply, give lower-budget ones your smallest package or a referral, and keep only the data you need to answer them.
What should happen when the date is already booked?
Reply quickly and honestly, then offer something useful: a nearby date if they're flexible, a second shooter or associate if you have one, or two suppliers you trust. Ask whether you can keep their details in case the date frees up. A graceful booked reply often turns into a referral later.
How many enquiries do I need before this is worth setting up?
If you get fewer than about ten enquiries a month, a good form and a saved reply template are usually enough. Automated extraction and routing start to pay off when enquiries arrive faster than you can answer them within a day, or when directory leads arrive in inconsistent formats you retype by hand.
Further reads
- A Wedding Planner's AI Workflow From Enquiry to Final Timeline — What happens after a lead books, through to the final timeline.
- How to Add an AI Chatbot That Captures Leads on Your Website — Capture the same fields through a website chatbot.
- How to Build a Quiz Funnel With AI to Capture Leads — A package-finder quiz that qualifies as it collects.
- How Wedding Businesses Get Found When Couples Ask AI for Suppliers — Get more enquiries when couples ask AI for suppliers.
- What Is Lead Nurturing and How Can AI Automate It? — Keeping not-yet-ready couples warm without chasing.
- How to Write Wedding Flower Proposals With AI — Turning a qualified floristry lead into a proposal.
- Is AI Culling Worth Paying for as a Wedding Photographer? — What AI culling costs a wedding photographer, the break-even by weddings per year, where it misjudges wedding frames, and a two-wedding trial to settle it.
- Best AI Tools for Small Event Planning Businesses — Eight AI tools for small event planning businesses, ranked by the hours they give back, with prices, first uses and the two to handle with care.
- How Caterers Use AI to Quote Events and Plan Menus — How a small caterer can use AI to go from messy enquiry to costed quote and proposal, with a worked 70-guest quote and prompts to copy.
- How Coaches Use AI to Qualify Discovery Call Bookings — Set fit criteria, ask four questions before the calendar, let AI sort and brief each booking, and send people who aren't ready somewhere useful.
- ClickUp vs Asana vs Monday: Which AI Features Save Time? — All three now charge for AI differently. A timed photography-studio example shows which features save hours and what each costs a five-person team.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: HoneyBook help pages on priority lead notifications and HoneyBook AI; Tally help pages on conditional logic; Zapier pricing and AI by Zapier help pages.