How Wedding Suppliers Can Reply to Enquiries in Minutes With AI

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How Wedding Suppliers Can Reply to Enquiries in Minutes With AI.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How Wedding Suppliers Can Reply to Enquiries in Minutes With AI.

Prepare three things once: a one-page facts sheet (packages, starting prices, what's included, booking rules), a reply template for each common type of enquiry, and a prompt that merges the couple's details into the right one. Then check the date in your diary, paste the enquiry in and edit the draft. A personal reply takes two to five minutes.

The speed comes from preparation, not from letting AI answer on its own. Availability and price are the two things couples act on, so those stay in your hands even when the drafting is automatic. The method works for photographers, florists, cake makers, bands, hair and make-up artists, celebrants and stationers; swap your own packages into the examples.

Follow me on Instagram@sagnikteaches

Sort the enquiry first: five types that need different replies

Most slow replies are slow because the supplier is deciding what kind of reply to write. Decide the type first and the draft almost writes itself.

Connect on LinkedInSagnik Bhattacharya
Enquiry typeWhat the couple needs from youWhat the AI draftsWhat you check first
1. Date free, details completeYou're available, the package that fits, a next stepA warm reply naming the matching package and a call linkDiary, and that the package really fits their numbers
2. Date free, details missingEnough to decide whether to keep talkingStarting price plus up to two questionsDiary
3. Date already bookedA kind no, ideally with somewhere to go nextA short decline with one or two referralsThe referral agreed to be recommended and is likely to be free
4. Budget below your minimumHonesty early, without a lectureYour starting price and any smaller option you genuinely offerThat the smaller option exists
5. The copy-paste enquiry ("are you free and how much?") sent to many suppliersA fast, short answer that feels humanFour to six lines: availability, starting price, one question about themDiary

Type 5 deserves its own template. Couples who send the same message to a dozen suppliers read replies quickly and compare them side by side. A 300-word essay loses to a friendly six-line answer that uses their venue's name and asks one good question.

Subscribe on YouTube@codingliquids

For a wedding band, that answer might read (illustrative): "Hi both, lovely to hear from you. We're free on Saturday 11 September and have played the barn at your venue twice, so we know the stage corner and the 11pm sound limit. Evening sets start from $2,400 for the four-piece, including a DJ playlist between sets. Are you after a first-dance song learned specially? [Sign-off]" Five sentences, one fact that proves you read the message, one price, one question. The couple can compare it with eleven others in ten seconds, and it's the one with a detail about their venue.

Write the facts sheet the AI works from

This is the single most useful hour you'll spend. It stops the AI inventing packages and it makes every reply consistent, whoever drafts it. Keep it to one page and update it at the start of each season:

BUSINESS: name; what you do in one line; who does the work
PACKAGES: name | what's included | starting price | typical total
EXTRAS: add-ons and their prices
MINIMUMS: minimum spend; peak-date rules; travel rules
BOOKING: how a date is secured (retainer, contract), and how long
         you'll hold a date without a retainer (if at all)
NEXT STEP: call link, consultation, brochure link
VOICE: five lines on how you write (first names? emoji? sign-off?)
NEVER SAY: discounts you don't offer, "guaranteed", anything
           about other suppliers' prices or quality
REFERRALS: suppliers you're happy to recommend when you're booked
           (ask them first)

Filled in by an illustrative two-person florist, the lines that do most of the work look like this:

PACKAGES: Ceremony and bridal party | bouquet, 4 bridesmaids,
          6 buttonholes, 2 pedestal arrangements | from $1,450
          Full day | the above plus 10 table centrepieces and
          set-up on the day | from $2,900
MINIMUMS: $1,200 on Saturdays May-September; $800 other days.
          Travel beyond an hour's drive charged at cost.
BOOKING: 25% retainer and signed contract secure the date.
         No holds without a retainer.
NEVER SAY: "any flower you like" (seasonal only); "guaranteed
           colour match"; anything about other florists' prices
REFERRALS: two florists who've agreed; both do smaller weddings

"Seasonal only" and "no holds without a retainer" are the two lines that stop the drafts making promises. Without the first, an assistant will cheerfully tell a September couple that peonies are no problem. Without the second, it will offer to "pencil in" a date, which is a hold you never agreed to give.

The reply prompt

Save this in a ChatGPT or Claude project with the facts sheet uploaded, or in your CRM's AI instructions if it has them. The DATE STATUS line is what keeps the AI from promising a date you haven't checked:

You draft first replies to wedding enquiries for [business].
Use only the facts sheet for packages, prices and policies.

ENQUIRY: [paste the couple's message]
DATE STATUS: [FREE / BOOKED / PROVISIONAL / NOT CHECKED]
ENQUIRY TYPE: [1-5]

Rules:
- If DATE STATUS is NOT CHECKED, write [CHECK DATE] where
  availability would go. Never state availability yourself.
- Use the couple's names and one specific detail from their
  message (venue, season, theme) in the first two lines.
- Quote starting prices only from the facts sheet. No discounts.
- Ask at most two questions.
- Under 170 words for types 1-4; under 90 words for type 5.
- Finish with one clear next step.
- Don't open with "Thank you for reaching out" or "Congratulations
  on your engagement"; every supplier says that.

The last rule matters more than it looks. Couples read a pile of replies that start the same way; writing reply templates that keep AI replies on-script covers keeping AI replies consistent with the templates you approve.

Three ways to run it, from copy-and-paste to automatic drafts

Option A: a chat assistant plus inbox templates

Keep the facts sheet and prompt in a project, paste each enquiry in, and copy the draft into your email. For the fixed parts (your sign-off, brochure links, a type 3 decline) use Gmail templates: in Gmail on the web, go to Settings, See all settings, Advanced, and enable Templates. You can save up to 50, though they only work in Gmail on the web, not the mobile app. Cost: nothing on a free chat plan, or $20 a month for ChatGPT Plus or Claude Pro. This suits most suppliers getting fewer than 15 enquiries a week.

Option B: a studio CRM with its own AI

If enquiries arrive through a CRM contact form, its built-in AI can have a draft waiting. HoneyBook, for example, creates an AI email draft when a new lead comes in through a HoneyBook contact or lead form, using your company and project details and a tone it learns from your past emails. The draft appears in the email composer for you to edit before sending, and you can switch automatic drafts off under Company Settings, HoneyBook AI. HoneyBook's plans start at $29 a month billed annually, and its pricing page lists the AI features across all three plans. Add your facts sheet's rules to your company details so the drafts use your real packages.

Option C: an automation that leaves drafts waiting in your inbox

For higher volumes across several channels, an automation tool can do the pasting. In Zapier the chain is: new form submission (or a new email with an enquiry label) as the trigger, an AI step that writes the reply using your facts sheet, then Gmail's Create Draft Reply action, so a draft sits in the thread ready for you. Triggers don't count as tasks; each successful action does, so two action steps across 60 enquiries a month is 120 tasks, well inside the 750 on Zapier Professional ($19.99 a month billed annually). The automation can't see your diary unless you connect it, which is why the prompt's [CHECK DATE] rule matters even more here. Before sending anything automatically, read how to add human approval steps to AI automations; for wedding enquiries, I'd never skip that step.

My rule of thumb: run Option A for two weeks. Move to B or C only if you're still pasting more than about ten enquiries a week and the copy-and-paste is the part slowing you down.

One enquiry, one draft, three edits

An illustrative enquiry to a hair and make-up artist: "Hi, we're getting married on a Saturday next June at a barn venue about an hour from you. It'd be me, four bridesmaids and my mum. Do you travel, and roughly what would it cost?"

The artist checks the diary (free), marks it type 1 and gets this draft:

Hi [name], a June barn wedding sounds lovely, and good news: I'm free on your date. For you plus five, my Bridal Party package covers your trial, your wedding-morning look and five guests, starting from [price from facts sheet]. Travel up to an hour is included, so your venue is fine. Could you let me know your ceremony time? That tells me what time we'd start. If it helps, you can book a 15-minute call here: [link]. [Sign-off]

Three edits before sending. The artist changed "five guests" to "four bridesmaids and your mum", because the couple will notice that she read the message. She removed "your trial" from the package line, since trials are booked separately on her facts sheet and the AI had merged two packages. And she added one sentence about how early a six-person party usually starts, which is the question couples always ask on the call. Total time: about three minutes.

The replies that go wrong: declines and budgets below your minimum

Types 3 and 4 are where drafts most often need a heavier edit, because the assistant tries to soften the no. Here's a type 3 draft (illustrative) from a photographer who's booked on the date: "I'm so sorry, I'm already booked on 20 June. I'd recommend a photographer I trust, whose style is similar to mine and who is a little more affordable, so she could be a great fit." The comparison on price has to go: it breaks the facts sheet's NEVER SAY line, it may not be true this season, and the referral didn't agree to be described that way. The sent version: "I'm already booked on 20 June, I'm afraid. Two photographers I'd happily recommend, both with a relaxed documentary style: [name and link], [name and link]. I hope the day is wonderful." Shorter, kinder and nothing in it that anyone can dispute.

Type 4 goes wrong the other way, with a lecture. A couple tells the florist above their flower budget is $800 for a Saturday in July, below the $1,200 minimum. A first draft explained why wedding flowers cost what they do, over three sentences. The edited reply: "Thanks for being upfront about budget, it really helps. Saturdays in summer have a $1,200 minimum with me, so I couldn't do the full ceremony package for $800. What I can do is a bridal bouquet and six buttonholes, collected from the studio on the Friday, from $450, and that leaves room for jam-jar table flowers you arrange yourselves. Would that help?" The smaller option has to exist on the facts sheet first, and the reply's job is to offer it, not justify your prices.

When you're working a wedding: the holding reply and the Monday batch

Wedding suppliers have a problem most businesses don't: the busiest enquiry days are the days you're at someone else's wedding. Saturday and Sunday enquiries can sit for 48 hours, which is exactly when couples are browsing together and sending messages.

Don't solve this by letting an AI reply to couples unsupervised. Solve it with an honest holding reply that needs no AI at all: an auto-reply, switched on for wedding days, that says you're working a wedding today, that you'll reply personally by a named time (Monday by noon, say), and that gives your starting prices and brochure link in the meantime. Couples get something useful straight away, and you've made a promise small enough to keep. For a hair and make-up artist it could say:

Thanks for your message. I'm with a bride and her party today, so I can't reply properly until Monday, but I will by 12 noon. In the meantime, my bridal packages start from [price] and my brochure is here: [link]. If you can, send me your date, venue and how many people need hair or make-up, and I'll check the diary first thing. [First name]

The last line matters: couples who answer it over the weekend arrive on Monday as type 1 enquiries, ready for a full reply.

Then treat Monday morning as a batch. Paste all the weekend's enquiries into the project at once with this:

Here are [number] wedding enquiries from the weekend. For each:
give the couple's date, venue if mentioned, what they asked for,
and which enquiry type (1-5) it looks like. Sort them by wedding
date, soonest first. Don't draft replies yet.

An illustrative slice of what comes back:

Date             Venue            Asked for                      Type
Sat 17 Apr 2027  Country house    Bride + 3, trial               1
Sat 12 Jun 2027  Not given        "How much for hair?"           5
Sat 10 Oct 2026  Barn, 1hr away   Bride + mum, travel?           2
next Saturday    Hotel            Urgent: artist let them down   2

Look hard at the last row. The message, sent on Sunday, said "next Saturday", and on a first pass an assistant is quite likely to turn that into a firm date of its own choosing, which may be a week out either way. Here it left the phrase as written, which is the safer failure. Either way, a last-minute couple whose artist let them down is the most urgent enquiry in the pile and the least likely to wait until the afternoon: check the date with them by message, then reply to them first, not in wedding-date order.

Check the dates against the diary in one go, mark each status, and draft the replies one by one with the main prompt. Sorting by wedding date means couples with the least time get answered first, and checking the diary once for twelve dates is far quicker than opening it twelve times.

What turns minutes back into hours

  • A diary that isn't current. If Monday's admin doesn't include updating the diary with the weekend's bookings, every date check becomes a hunt.
  • A stale facts sheet. Last season's prices in the sheet means last season's prices in every draft.
  • Enquiries scattered across channels. Email, DMs, a directory inbox and WhatsApp each need visiting. Pick one place to collect them before you speed up the replies.
  • No follow-up. A fast first reply wins attention; it doesn't win the booking on its own. Decide when you follow up a couple who went quiet, and whether the date is worth a second message. Qualifying wedding leads by date, budget and guest count helps you decide which ones deserve it.
  • Replies that all sound alike. Read ten sent replies in a row once a month. If you could swap the names between them, rewrite the templates.

Some of these are the same errors that put couples off wedding businesses more generally; the AI mistakes that put couples off covers more of them.

Measuring whether faster replies win more bookings

Track three numbers in a simple sheet: minutes from enquiry to reply (the enquiry's timestamp against your sent time), the share of couples who reply back, and the share who book a call or consultation. Compare them with the month before you started. If reply time fell but replies-back didn't rise, speed wasn't your problem: look at the first two lines of your drafts and the next step you're offering. If both rose, you've found the hour a week that pays for everything else in this tutorial. For a stationer, a month might look like this (illustrative figures): reply time down from a median of about nine hours to 40 minutes, replies-back up from 12 of 30 couples to 17 of 31, calls booked up from 5 to 8. Small numbers, so give it three months before you trust the trend, and note anything else that changed, such as a new price list or a wedding fair, which moves enquiries more than reply speed does. For a broader version of this system beyond weddings, replying to every enquiry in under five minutes covers other service businesses.

Wedding enquiry replies: what suppliers ask next

Should I include prices in my first reply to a wedding enquiry?

Include a starting price or typical range in most first replies. Couples comparing several suppliers tend to drop the ones who won't say, and a range filters out enquiries you couldn't take anyway. Keep the detailed quote for after a call, when you know guest numbers, timings and what they actually want. The exception is fully bespoke work, where a range plus one question is more honest.

Will couples mind that AI helped write my reply?

They mind replies that feel generic, not the tool behind them. If the reply uses their names, mentions their venue or theme, answers their actual question and comes from you, it reads as personal. Problems start when every reply opens with the same phrase or promises something you didn't check. Edit every draft and you're simply replying faster.

Can the AI check my diary and confirm availability automatically?

Some CRMs and automation tools can look up a connected calendar, but I wouldn't let a first reply confirm a wedding date without a person checking. Diaries miss provisional holds, second-shooter bookings and travel days. The safer pattern is a draft that says the date looks free, written after you've looked, with the booking step making it firm.

Further reads

Sources: Gmail Help on creating templates; HoneyBook help article on drafting emails with HoneyBook AI and the HoneyBook pricing page; Zapier Gmail integration pages and plan pricing (checked September 2026).

Want your enquiry replies set up to run fast?

On a 1:1 call we'll sort your enquiries into types, write the facts sheet with you, and decide whether a chat assistant, your CRM's AI or an automation fits the number of enquiries you get.

Book a 1:1 call with me