ChatGPT Prompts for Wedding Planners: Vendor Emails, FAQs, Thank-Yous

Nine ChatGPT prompts in three chains do the work. The vendor chain turns notes into a brief, an email and a reply check. The guest chain finds gaps in your fact sheet, answers questions only from it and adapts the answers for email, messaging and print. The thank-you chain logs who to thank and drafts supplier notes and guest cards.

A chain beats a list of prompts because each output becomes the next input, and all three chains start from one master fact sheet. That is what stops ChatGPT telling a guest the shuttle leaves at 15:00 when your notes say 14:45. Suppliers appear as "the caterer" or "the florist" throughout, and no names go in.

Follow me on Instagram@sagnikteaches

Every sample comes from the same 96-guest wedding with 11 suppliers, so you can follow one fact from the sheet into an email, an FAQ and a card. The sample outputs are illustrative. Run the chains on a finished wedding before a live one, and read where ChatGPT gets event facts wrong if you want the failure modes first.

Connect on LinkedInSagnik Bhattacharya

One master fact sheet feeds all nine prompts

ChatGPT writes fluent text whether or not it has the facts, which is the whole risk. The fix is a master fact sheet with a source beside every line, so each answer it writes can be traced to a row. Keep it as a file in a ChatGPT Project, with your style notes in the project instructions. OpenAI describes a Project as keeping related chats, files and instructions together, and you can add documents, spreadsheets, images or pasted text.

Subscribe on YouTube@sagnikteaches

This is the sheet for the example wedding. Where the planning questionnaire from the couple feeds it, a wedding planner client questionnaire turned into a brief covers how to gather those answers.

The source column does the most work. When a later prompt writes an answer about parking, you can find row 7 and see it came from the venue contract rather than from the model's idea of what a venue has. If you can't give a row a source, it doesn't belong on the sheet yet.

Vendor chain: from messy notes to a florist email that gets answered

Vendor emails go unanswered when the questions are buried in a friendly paragraph, and they go wrong when your notes and the supplier's assumptions quietly disagree. The chain has three steps: tidy your notes into a brief, write the email from the brief, then compare the reply with the brief. The florist is the example, but the same three prompts fit the caterer, the DJ or the shuttle company.

Prompt 1: the one-page brief

Turn my notes about one supplier into a one-page brief. My notes are messy: keep every fact, invent none.

Supplier: the florist
Notes: install 12-ish? ceremony arch x1, 12 round tables (8 each) low centrepieces, 2 pedestals at entrance, bouquet + 5 buttonholes to hair and make-up room by 13:00?, room access 12:00 per venue, van must use side gate (check height limit), vase collection Sunday 09:00?, palette sage and cream, no lilies (a guest reacts badly), couple want dried grasses, final payment due 14 days before.

Format: FIXED FACTS, TO CONFIRM (anything with a question mark or "check"), QUESTIONS FOR THE SUPPLIER (maximum 6), DEADLINES, MISSING (what a florist would need that my notes lack).
Take times and numbers from the master fact sheet below. Never add a name.

[paste the master fact sheet]

Sample output (illustrative):

FIXED FACTS
- Ceremony 15:30, on the lawn. 96 guests, 12 round tables of 8.
- Room access from 12:00 (venue, confirmed by email).
- Palette sage and cream. No lilies. Dried grasses wanted.
- Items: 1 ceremony arch, 12 low centrepieces, 2 entrance pedestals, 1 bouquet, 5 buttonholes.
TO CONFIRM
- Install start (notes say "12-ish").
- Bouquet and buttonholes to the hair and make-up room by 13:00.
- Van height against the side-gate limit.
- Vase collection Sunday 09:00.
QUESTIONS FOR THE SUPPLIER
1. How long does the install take, and does it fit between 12:00 and 15:00?
2. Can the bouquet and buttonholes reach the hair and make-up room by 13:00?
3. What is the van's height?
4. Can everything avoid lilies, buttonholes included?
5. Can dried grasses go into the arch?
6. Who collects the vases on Sunday, and when?
DEADLINES
- Final payment 14 days before the wedding.
MISSING
- Where the hair and make-up room is. Who signs for the delivery. Bouquet style.

Two things to check. First, that the question-marked items from your notes landed under TO CONFIRM rather than being promoted to fixed facts; the instruction asks for it, but a draft sometimes tidies "12-ish" into "12:00". Second, that the brief keeps the reason for "no lilies" out of the supplier's inbox. "A guest reacts badly" stays in your notes; the brief says only "no lilies", which is all the florist needs and keeps a guest's health detail unattached to anyone.

Prompt 2: the email, built from the brief

Write an email from me (the planner) to the florist from this brief. Under 170 words. Friendly and direct. Open with the one thing I most need, the install window. Put the questions in a numbered list. End with a reply-by date of [date]. Use only facts in the brief. Where something is under TO CONFIRM, ask; do not state it.

[paste the brief]

Hi [first name], I'd like to lock the install window for the wedding on [date]. The room is open to you from 12:00 and the ceremony is at 15:30, so could everything be finished by 15:00? A few quick questions: 1) How long will the install take, and does it fit between 12:00 and 15:00? 2) Can the bouquet and five buttonholes reach the hair and make-up room by 13:00? 3) What is your van's height? Access is by the side gate, which has a limit I'm checking. 4) Can everything avoid lilies, buttonholes included? 5) Can dried grasses go into the arch? 6) Who collects the vases on Sunday, and when? If you can reply by [date], I can confirm access with the venue. Thank you, [your name]

That's sample output, trimmed to the essentials. Read it the way the florist will: is the ask in the first sentence, and could they answer all six questions from a phone in a van? If not, shorten it. The "side gate, which has a limit I'm checking" line shows the TO CONFIRM instruction working: the email asks for the van's height instead of pretending the planner knows the gate's limit.

Prompt 3: compare the reply with the brief

Compare the florist's reply with my brief. Give me four lists: AGREED, DIFFERENT FROM MY NOTES, CONFLICTS (where the reply contradicts a fixed fact or another supplier's needs), and NEW QUESTIONS the reply raises. Then draft a confirmation email of under 150 words that confirms only what is agreed. Do not smooth over a conflict: name it, with both times.

BRIEF: [paste the brief]
REPLY: [paste the florist's reply, signature and phone number removed]

Suppose the florist replies, in part: "We'll need access from 10:00 to dress the room by 15:00. The arch takes our team 3 hours and the centrepieces another 2. Our van is 2.4 m high. Bouquet and buttonholes can be with the make-up room by 13:30. Dried grasses are no problem and lilies aren't in our palette anyway. Vases collected Sunday 11:00." Sample output (illustrative):

AGREED
- Dried grasses. No lilies. Finish by 15:00.
DIFFERENT FROM MY NOTES
- Vase collection: Sunday 11:00 (notes said 09:00, unconfirmed).
CONFLICTS
- Access: florist needs 10:00 to 15:00 (5 hours: arch 3 + centrepieces 2). Venue gives access from 12:00, which is 3 hours.
- Delivery: bouquet and buttonholes at 13:30, brief asked for 13:00.
NEW QUESTIONS
- Is a 2.4 m van within the side-gate limit? Who opens the gate at 10:00 if access is moved?
DRAFT CONFIRMATION
Thanks [first name]: confirmed dried grasses, no lilies and vase collection on Sunday at 11:00 (pending the venue). I'm taking the access time and gate height to the venue and will come back to you on both.

The conflict is the point of the chain. A five-hour install can't fit into a three-hour window, and on the day that gap would have been found by a florist standing at a locked door. ChatGPT can list your options, such as asking the venue to open up earlier for the florist alone, trimming the install, or adding a second pair of hands, but it can't know which the venue will accept. That is an email to the venue, written with prompt 2 and the new facts. The 13:30 delivery also matters to anyone photographing the preparations; if your photographer builds a timeline too, the photographer's prompts for timelines, groups and albums show how a half-hour slip ripples through their day.

Guest FAQ chain: answers that stay inside the fact sheet

A guest FAQ is where a fluent wrong answer does the most damage, because up to 96 people may read it and nobody checks it against the contract. The chain therefore starts by asking what the sheet doesn't cover, writes answers only from what it does, and then adapts the approved text for each place guests will read it.

Prompt 4: find the gaps before writing anything

Below is my master fact sheet for a wedding. List every fact a guest would reasonably ask about that the sheet does not cover. Start from these topics: getting there, parking, accommodation, dress code, children, plus-ones, dietary needs, accessibility, rain plan, gifts, photography, bar and music times, who to contact on the day. Output a list called MISSING, one line each, with the person who can answer (couple, venue or me). Do not answer any of them.

[paste the master fact sheet]

Sample output (illustrative):

MISSING
- Step-free route from the car park to the lawn (venue)
- How guests tell us about dietary needs, and the deadline (couple, me)
- Hotel block: booking code and release date (me)
- Whether the ceremony is phone-free (couple)
- Gifts: any preference or registry (couple)
- Evening-only guests: arrival time (couple)

This list is a to-do list for you, not text for guests. Go and get the six answers, add them to the sheet with a source, and only then move on. Suppose the venue confirms in writing that the route is step-free: add a row, "Access: step-free route from the car park to the lawn", source "Venue, email", and that fact can now appear in the FAQ.

Prompt 5: the FAQ, from the sheet and nothing else

Write 12 guest FAQs and answers using only the master fact sheet below. Answers are one to three sentences, warm and plain, in the couple's voice ("we"). If the sheet does not answer a question, write ANSWER NEEDED: and the person to ask, instead of answering. Never round a number, shorten a time or add a detail. Order: before the day, on the day, afterwards.

[paste the master fact sheet]

Sample output (illustrative, five of the twelve):

Q: When does the shuttle leave?
A: From the hotel at 14:45 and 15:10. Return shuttles leave at 23:30 and 00:00.

Q: Is there parking?
A: Yes, there are 40 spaces on site, free of charge.

Q: Can I bring a plus-one?
A: Plus-ones are named on the invitation only.

Q: What if it rains?
A: The ceremony moves indoors. We decide at 12:00 on the day and a text goes to everyone.

Q: What time does the evening finish?
A: Music ends at 23:00 and the bar closes at 23:15.

Look at the rain answer. "A text goes to everyone" isn't in the sheet; the model supplied a plausible process, and a guest might wait for a message that nobody has agreed to send. Either add a fact (who tells guests, and how) or cut the clause. Also read the plus-one answer as a guest would: accurate, but cold. Rewording is fine as long as no fact changes, and it's quicker to soften a correct sentence than to hunt for a hidden wrong one.

Prompt 6: one approved FAQ, three versions

Rewrite the approved FAQ below in three versions: (1) a website FAQ page with each question as a heading; (2) a message for guests, under 120 words, covering only the five most time-sensitive facts for the week of the wedding; (3) a printed card of 90 words or fewer for the welcome table. Keep every number and time exactly as in the FAQ. Add "Correct as at [date]" to each.

[paste the approved FAQ]

Hi everyone, a few things for Saturday. The shuttle leaves the hotel at 14:45 and 15:10, and the ceremony is at 15:30 on the lawn. Parking on site is free, with 40 spaces. If it rains the ceremony moves indoors; we'll decide at 12:00. Music ends at 23:00, and the last shuttles leave at 23:30 and 00:00. Correct as at [date]. See you there!

The "Correct as at" line is the one that saves you. When a fact changes, a dated message makes it obvious which version a guest is holding. Put the version date in the file name of the approved FAQ too.

Five awkward questions that test the FAQ

Before the FAQ goes anywhere, put it and the fact sheet back into a fresh chat and ask the questions guests actually ask, the ones the sheet can't answer. A pass is a flagged gap; a fail is a confident answer.

1. "Can I bring my partner of three weeks?" The sheet says plus-ones are named on the invitation, so ChatGPT should give that rule and flag that late additions need the couple's decision.
2. "Is there parking for two minibuses?" The sheet says 40 spaces and nothing about minibuses. Expected: ANSWER NEEDED, venue. A cheerful yes is a fail.
3. "My daughter is three. Can she stay for the evening?" Children are welcome and a quiet room is available, but evening hours aren't covered. Expected: ANSWER NEEDED, couple.
4. "Is the cake gluten-free?" The sheet is silent. Expected: ANSWER NEEDED, via you to the cake maker, with no guest's dietary detail pasted in.
5. "What time should I leave the hotel?" The shuttle times and ceremony time answer this, so ChatGPT should answer from the sheet.

If a run fails question 2 or 3, check the prompt text first: that "ANSWER NEEDED" is still in the instruction and that the sheet is actually attached to the chat. For the longer picture of how couples' questions land across a planner's whole workflow, a wedding planner's AI workflow from enquiry to final timeline is the companion piece.

Thank-you chain: notes that name one real thing

Thank-you notes fail in two opposite ways. Asked to write from nothing, ChatGPT produces "you went above and beyond", which every supplier has read a thousand times. Left to a tired planner on the Tuesday after, they never get sent. The chain solves both by making you supply one real thing per person while you still remember it, then letting ChatGPT handle the sorting and phrasing. The same rule drives donor thank-you letters that still feel personal: the detail has to come from a human.

Prompt 7: the thank-you register

Build a thank-you register from my notes. I give one specific thing each supplier did. Output a table with four columns: ROLE, THE SPECIFIC THING (copy my words, do not embellish), CHANNEL (email, call or handwritten note) and SEND BY (days after the wedding). Match the channel to the size of the thing: a small favour gets an email, a rescue gets a call or a handwritten note. Do not add any detail.

Notes:
- Caterer: rebuilt the dessert table in 20 minutes after a late delivery.
- Shuttle driver: waited 25 minutes for the last guests without being asked.
- Hire company: swapped two wobbly chairs before the ceremony.
- DJ: reworked the speech order twice at the last minute without fuss.
- Venue coordinator: held the rain decision to the 12:00 deadline.

Sample output (illustrative):

The channel and the timing are suggestions; the second column is the one that must match your notes word for word. Edit the channel column freely. A driver who waited 25 minutes might well be happier with a message to their employer than to themselves, which is why the table copies the firm's office.

Prompt 8: the supplier notes

Write a thank-you note from me (the planner) to each supplier in the register. Under 70 words each. Mention the specific thing once, in plain words. Do not use "amazing", "incredible" or "above and beyond". Start every note differently. Sign off [your name]. Leave [first name] as a gap for the contact.

Sample output for two of the five (illustrative):

Hi [first name], thank you for Saturday. When the dessert delivery arrived late, you rebuilt the table in 20 minutes and nobody at the party knew anything had gone wrong. I'd be glad to work with you again. [your name]

Hi [first name], thank you for waiting 25 minutes for the last guests without being asked. It took one worry off my list at the end of a long day. Best wishes, [your name]

The first note includes a sentence that is not in your register: "nobody at the party knew anything had gone wrong". It sounds kind and might even be true, but you didn't tell ChatGPT that, so strike it or replace it with something you saw yourself. Check the openings too. "Start every note differently" helps, but five notes that all begin "Hi [first name], thank you for..." are still common, so rewrite two of them by hand.

Prompt 9: card wording the couple can finish

Draft four short thank-you card messages for the couple to send to guests. Each has two gaps: [first name] and [specific detail the couple adds]. Four situations: (1) a cash or voucher gift, (2) a physical gift, (3) guests who travelled a long way, (4) guests who helped on the day. Maximum 40 words each. Warm and specific, not gushing. Do not mention amounts or what was bought. Write in the couple's voice: friendly, a little dry, no exclamation marks.

1. Dear [first name], thank you for your generous gift. We've set it aside for [specific detail the couple adds], and we'll think of you when we use it.
2. Dear [first name], thank you for the [specific detail the couple adds]. It already has a place at home, and it made the day feel more ours.
3. Dear [first name], we know how far you came to be with us. Thank you for making the journey, especially to [specific detail the couple adds].
4. Dear [first name], thank you for helping on the day, in particular [specific detail the couple adds]. We couldn't have done it without you.

These are templates, not finished cards, and the couple should write the gap themselves. I'd give ChatGPT three adjectives for their voice rather than pasting their messages, because their messages carry other people's names and plans. Approval comes before printing: send the four versions to the couple, take their edits, and only then let them copy into cards by hand.

When a fact changes: edit the sheet, then rerun

The real test of a chain comes three weeks out, when the transport firm moves the first shuttle from 14:45 to 14:30. Without a fact sheet, that change lives in your inbox and gets copied by hand into the FAQ, the guest message, the printed card and an email to the photographer, and one of them stays wrong. With the sheet, the change takes four steps.

1. Edit row 6 of the master fact sheet and change its source to "Transport firm email, [date]".
2. Rerun prompts 5 and 6 with the updated sheet, not the old FAQ.
3. Ask ChatGPT to list every line that differs between the old and new FAQ, and read only those lines.
4. Send guests a two-line update, and tell each supplier whose plans depend on guest arrival time, such as the photographer and the venue coordinator.

Step 3 matters because a regenerated FAQ can change more than the shuttle time. Wording that drifts between runs is harmless if you notice it and a nuisance if a guest does. Keep the approved version, compare, and put anything that isn't the change itself back the way it was.

A quick sum for the 96-guest wedding, chain by chain

These are illustrative figures for the example wedding, with 11 suppliers. Time your own next wedding and replace them.

On these placeholder figures the chains free up 262 minutes, a little over four hours. The FAQ chain gives the largest single saving at 90 minutes, just ahead of the vendor chain at 88, but the vendor chain has the smallest percentage gain, about 40 per cent against roughly 60 for the FAQ and 57 for thank-yous. That makes sense: a supplier's reply still has to be read by a person, and a conflict still has to be resolved by one. The time isn't the only gain. The florist conflict above surfaced a month before the day, and the same question asked on the day would have cost a lot more than 12 minutes.

What stays out of ChatGPT, and how to test the chains first

None of the nine prompts needs a guest's name. Keep these out of every chat:

• Dietary and medical detail tied to a named guest. Allergies are health information. Send the caterer the numbers through your usual channel, and give ChatGPT only categories ("some guests have dietary needs").
• Phone numbers, emails and addresses of guests, suppliers or the couple.
• Payment details and whole contracts. Paste the one clause a prompt needs.
• The couple's private messages and vows.

Settings help as well: personal plans have a privacy switch that keeps your chats out of model training, and ChatGPT Business content isn't used for training by default. The habit of keeping personal data out is still the more reliable protection. For a first trial, use a wedding you've already run. Build the master sheet from its contracts, run prompts 4 and 5, and compare the FAQ with the questions guests actually emailed you. Then run prompt 3 on an old supplier reply where something went wrong and see whether it spots what you missed at the time. If you already use a client-management tool, HoneyBook AI versus ChatGPT for wedding planners helps you decide which of the two should write the client-facing emails.

Questions planners ask about running the chains

Can ChatGPT remember my wedding details between chats?

Don't rely on memory. Put the master fact sheet in a ChatGPT Project as a file and start every chain from it. OpenAI's Projects also offer project-only memory, which stops saved memories from other chats leaking in and stops the project reading outside conversations. A file you control beats anything the tool half-remembers.

Should the couple approve the guest FAQ before it goes out?

Yes, every time. The FAQ speaks in their voice and states things on their behalf, such as children's policy and plus-ones. Send them the approved fact sheet and the FAQ together, ask for a written yes, and date-stamp the version guests see so a later change is easy to trace.

Is it fine to paste a supplier's email into ChatGPT?

Paste the message, not the person. Delete the signature, phone numbers and any personal chat about their staff or family, and keep to roles such as the florist or the caterer. Prompt 3 works from the content of the reply, so nothing identifying is needed.

Which of the nine prompts should I try first?

Start with prompts 4 and 5, the fact-sheet gap finder and the FAQ. They carry the least risk, and a wrong FAQ answer is cheap to correct before the day. They also show you how much discipline the fact sheet imposes, which is the habit the vendor and thank-you chains depend on.

Further reads

• Wedding Planner Software: What AI Adds to Client Portals and Invoices — What AI adds inside client portals and invoicing tools.
• Which Event Planning Tasks Should You Hand to AI First? — Which event planning tasks to hand to AI first.
• Event Planning Checklist: Build One Per Event Type With AI — Build a checklist per event type once the chains work.
• Event Planning Using AI After the Day: Feedback, Sponsor Reports, Debrief — After the day: feedback, reports and a team debrief.
• How Event Planners Use AI to Build Budgets and Run Sheets — Budgets and run sheets: the numbers side of the same events.
• Wedding DJ Questionnaire: Must-Plays and Timeline Built With AI — Collect a DJ's must-plays and timings before the day.
• AI Mistakes That Put Couples Off Your Wedding Business — Mistakes that put couples off a wedding business.
• 8 ChatGPT Prompts for DJs: MC Scripts, Toasts and Announcements — Eight fill-in ChatGPT prompts for wedding and party DJs: entrances, toast introductions, announcements and a pronunciation sheet, with sample lines.
• How Much Should a Wedding Planner Charge? Model Fees With AI — For planners setting their own fees: hours per wedding, flat against percentage at three budget levels, break-even, and a model built with AI.
• Does Dubsado Have AI? What to Use Alongside It for Client Admin — Dubsado lists AI form building, a call notetaker and email summaries. Here is what they do, what they cost, and what ChatGPT or Zapier adds beside them.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: OpenAI help pages on Projects in ChatGPT, including project-only memory (checked October 2026). Times, counts and minutes saved are illustrative, not measured.