Flights, boots, after-parties. The AI handled the wedding questions.

The bride wanted something intimate. Outdoors. Nothing too elaborate.

The couple were both in their sixties, stepping back from businesses they’d spent years building. They wanted their favorite people around for the weekend. Plenty of time. Plenty of budget. My private working title was “old and rich.” (Not something I said to the clients.)

The setting was a private ranch tucked into the mountains of western Wyoming. The wedding lasted three days. Welcome dinner, outdoor ceremony, after-party, farewell brunch.

People have wildly different definitions of “nothing too elaborate.” Event planning has taught me that.

But honestly? Mountains behind a long dinner table, flowers everywhere—I was excited too. Making that picture actually happen is my job.

The catch was that her friends were flying in from all over the country. One gorgeous wedding came with a surprising amount of explaining.

Before the flowers came the questions

While I was working on the florals, these questions kept landing in the couple’s group chat:

• Which entrance should I give my driver?
• Do we go straight to the ranch or to the hotel first?
• Do we RSVP separately for Friday dinner and Saturday’s wedding?
• Black tie, on grass? What exactly am I doing about heels?
• Is the after-party in the same place? When should I book a car if I’m leaving after dinner?

Fair questions. I’d want to know too.

I’d also already written the answers. Several times. In messages and schedules. The bride was forwarding them to her friends.

I was planning the wedding and writing instructions the bride could pass along to her friends.

Old, rich, and making a weekend of it

This wedding had details.

• Friday: welcome barbecue at the ranch. Cowboy boots encouraged.
• Saturday: ceremony on the lawn. Black tie, with shoes that could handle grass.
• Dinner at a long table elsewhere on the property. Bring your bag when you move.
• After-party in the ranch’s glass greenhouse. A different building from the ceremony.
• Sunday: a pancake-truck brunch. Leave early for a flight if you need to.

The bride wanted a weekend where her friends didn’t have to worry about anything. Which meant somebody did. Hi. Me.

Friends booked cars and drivers or rented something themselves. Getting a car was less of a question than where that car should go.

The ranch had two entrances. Guests used the east gate. Flowers and catering used the service entrance. Sending a driver just the address could land them at the wrong one. We had valet at the main guest entrance, with pickups at the same gate afterward.

Everyone could pick their own boots. Somebody still had to tell them where to get out of the car.

I shared a guest-facing list

I made “Wedding weekend — guest guide” in thrw. Not my entire production checklist. Just the things guests needed to know.

I created a share link and opened the guest view. The list and item details were there, with an AI chat right alongside them.

I’d effectively made my own AI chatbot, one that could read my event guide and answer questions about it. Guests could use it right at that link. I hadn’t written a set of anticipated questions and answers.

Here’s the kind of information I put in the list.

Wedding weekend — guest guide
All times local to the venue

RSVP
Reply to the invitation email by June 1
Include which events you’ll attend and your invited guest

Arrival and transportation
Arrange your own airport, hotel, and venue transportation
Guest vehicles: east gate / valet on site
Service entrance: flowers, catering, and production vehicles only
Driver pickups also at the east gate

Friday welcome barbecue
5:45 p.m. arrival / 6 p.m. ranch dinner
Casual dress; cowboy boots welcome

Saturday wedding
3:30 p.m. guest arrival / 4 p.m. lawn ceremony
4:45 p.m. cocktails / dinner 6–8:30 p.m.
Black tie; grass-friendly shoes; a layer for the evening

Saturday after-party
9 p.m. in the ranch’s glass greenhouse
Optional; guests may leave earlier
Arrange your own return car; pickups at the east gate

Sunday brunch
9–11 a.m. at the ranch / arrange your own airport transfer

Dates, locations, vehicle access, what to wear. Each item had the details. The shared guide also included the ranch address and east-gate instructions.

The bride asked. Honestly, so did I.

During a meeting, the bride opened the shared link on her phone. I watched her type her first question:

My mom’s leaving after dinner. What time and where should she ask her driver to pick her up?

The AI pointed to dinner ending at eight thirty and the east gate as the pickup location. If her mom was leaving after dinner, she could arrange a pickup around then. The after-party was optional.

The bride had her message: “Leave after dinner if you like, Mom. Meet your car at the east gate.”

Being the bride didn’t mean having three days of transportation memorized. She needed the schedule too.

And, slightly embarrassing admission: so did I.

After a call with the florist, a seating-plan check, then a guest-arrival question, I could briefly forget whether arrival was three thirty or four. I’d planned it. The numbers were still starting to blur.

So I opened the same guide and asked the AI:

What time do guests arrive Saturday? Give me that and the ceremony start.

Three thirty arrival. Four o’clock ceremony. The two times I’d recorded, right there.

I’d made it for the guests and was already using it myself. “I just asked it that too” turned out to be a pretty good way to introduce it.

“I don’t land until Friday evening”

I went through the guide on a video call with the bride and one of her bridesmaids. The bridesmaid shared her screen and opened the link.

She looked through the list, then asked the AI on the right:

I’m landing Friday evening and probably missing the barbecue. If I’m only coming from Saturday onward, what should I check first?

The AI read the list and picked out what she needed.

• Include Saturday onward in her RSVP.
• Arrange airport-to-hotel and hotel-to-ranch transportation.
• Give the driver the east-gate instructions. If driving, use the on-site valet.
• Arrive for the 3:30 p.m. guest arrival time Saturday.
• Ceremony at four. Black tie, with shoes suitable for the lawn.

The instructions I’d already written came back in an order that fit her arrival.

Her next question:

Can I wear heels? What time should I book a car if I’m just staying for dinner?

The AI pointed to the grass-friendly shoe note, dinner ending at eight thirty, and the east gate as the return-car pickup location.

She laughed. “The dress was easy. The shoes were my problem.” Then she typed another question she’d been about to send the bride. For a moment, neither of us had to answer.

Shoes and an exit strategy. Honestly, fair questions.

I didn’t have to predict every question she’d ask. I had to write down the event information. She could ask about her own situation.

Less “It’s in the guide”

I don’t want to make guests the problem. After booking flights, taking time off, and finding a dress, I’d probably miss a detail too.

One person needs directions. Another needs the dress code. Another wants to know whether they can skip the after-party.

Same guide. Different reasons for reading it.

In thrw, they could scan the list and ask about what mattered to them. No copying it into another AI or explaining the wedding from scratch. The place to ask was right beside the information.

I maintained the guest guide. Guests read it or asked questions. The bride had fewer messages to relay between her friends and me.

That was much better than simply displaying a neat checklist.

Change the plan, update what my chatbot reads

Close to the event, we pushed the after-party from nine to nine thirty. A little more time to get everyone over after dinner.

I updated that item in the shared list. Instead of sending another PDF, I kept the current instructions at the same link.

If a guest opened it later and asked where and when to go after dinner, the AI could read the updated list and answer.

It didn’t answer everything. If I hadn’t put seating arrangements in the shared list, the AI couldn’t know them. I checked and answered those.

The AI beside the list doesn’t read my budget or private production notes. Guests can’t change the ceremony time by asking in chat. It answers from the guide I chose to share.

That role was plenty useful.

I still ran around at the wedding

Checked the valet arrangements, checked flowers, made sure nobody had misplaced a boot. Event planning had not suddenly become a serene profession.

But I didn’t have to keep rewriting the instructions for each guest. Late Friday arrivals, Saturday-only guests, people heading home before the party ended: same list, their own questions.

Not everyone at an outdoor wedding needs to know the same thing.

One link could lead to the answer each person needed.

I handled the flowers and the on-site logistics. The bride took pictures with her friends. The little AI chatbot reading my guide was there for their questions.