November 4, 2026 · 5 min read
A Chatbot Has No Buttons: The RSVP Site, the Floor Plan, and the Exports an AI Cannot Give Your Wedding
A chatbot is a box you type questions into, and a wedding needs a handful of things that are nothing like that: a page where two hundred guests click yes, a canvas where you drag a table away from a doorway, and a file your venue can print on the morning of. AI is extraordinary at answering. It has no buttons. I built a planning app, so I have a stake in this, and I also use Claude every day for the questions. This is about the other part.
The RSVP page
Guests need somewhere to go. A link on the save-the-date that opens a page with the date, the address, the hotel block, and a form that writes a yes or a no into your list. A chatbot can write the copy for that page, well, in under a minute. It cannot host it, cannot give it a URL, cannot put a form on it, and cannot catch the answer when your aunt taps submit. Someone has to build the page and own the list behind it, and the chat is neither. What the site should contain, and when to build it, is here.
The floor plan
This is the one I care most about, because I spent nine years walking into reception rooms the morning of a wedding. A room is geometry. Ten rounds of eight either fit with a dance floor and room to walk, or they don't, and the only way to know is to draw it: the walls in feet, the tables at their real sizes, the bar, the DJ, the path to the bathrooms. A chatbot can tell you that a 60 inch round seats eight and needs about five to six feet to the next table. It cannot draw your room, and it cannot show you that table fourteen is in the doorway. Ask it for a seating chart and you get a numbered list of tables with names under them, which is a spreadsheet wearing a different font.
A layout builder is a canvas. You draw the room to scale, or import the venue's PDF. You drop tables from a palette with real dimensions. You drag a guest from your list onto a seat. When the cousins say yes late, you drag two more chairs to table nine. Then you export a PDF the venue tapes to the wall. Every step of that is a button, and a chat has none of them. The calm method for deciding who sits where is here.
The exports
The plan has to leave the tool, in a form other people can use. The caterer needs a list by table with meal choices. The venue needs the floor plan. The rental company needs a table count. Every vendor needs the day-of timeline with their own arrival time. Your planner, if you have one, needs all of it, and your mother needs the guest list as a spreadsheet so she can stop asking. A chat can produce text you copy and paste into something else. It can't hand you a PDF with the floor plan and a card per table, or a ZIP with every record as a spreadsheet, or a timeline sent to each vendor with only their rows. The monthly export I'd run with any tool only works if the tool has an export.
The buttons, listed
A form guests submit. A canvas you drag on. A calendar push. A filter for no response. A field for a deposit and a field for a balance with a due date on each. An import for the CSV you already have. A download for everything. A send-to-vendor for the timeline. All of them are interface, and interface is the part a chatbot structurally doesn't have in 2026, no matter how good the model gets. It's a conversation. A wedding plan is a set of things you can click.
Where AI genuinely helps here
Writing the website copy and the FAQ answers. Drafting the vendor emails that go with the timeline. Explaining what a venue's floor plan PDF means when it says load-in door and fire lane. Suggesting a seating approach for the divorced parents. Turning a caterer's contract into three payment lines you then type into the budget. The chat is a brilliant assistant to the person with the buttons. It isn't the buttons.
Where Altessa fits
Altessa is the buttons. A one-page wedding site at a link you choose, with the schedule pulled from your run of show and an RSVP form that finds each guest's invitation by name and files the reply beside your guest list. A guest list with one row per person, CSV import, and a no-response filter. A budget with a deposit and a balance per vendor, each with a due date. A timeline that pushes to Google Calendar. A run of show that sends each vendor their own copy. A layout builder that draws the room to scale and seats guests at the seat, with a PDF for the venue. And a one-click export of everything with no email gate. One-time purchase, 80 dollars for Core and 120 for Premium with the layout builder, free to start. Keep the chat open beside it for the words.
Questions people ask
Can ChatGPT make a wedding website with RSVP?
It can write the copy. It can't host a page, give it a link, or collect RSVPs into a list. You need a website tool or a planning app with a site for that.
Can AI make a wedding seating chart?
It can suggest who sits together and list tables with names. It can't draw your room to scale or let you drag a table away from a doorway. A layout builder does that.
Can ChatGPT export a wedding plan to send to my planner?
Only as text you copy. A planning app exports a floor plan PDF, a guest list spreadsheet, and a vendor timeline, which is what a planner or venue actually uses.
What can a wedding planning app do that ChatGPT can't?
Host an RSVP page, hold a guest list edited in place, track vendor deposits and balances with due dates, push deadlines to your calendar, draw a to-scale floor plan with seating, and export all of it.
Armin Korsos is a filmmaker who spent nine years shooting weddings before building Altessa (altessa.studio), an all-in-one wedding planning workspace that replaces the spreadsheet.
More for this stage
12+ months: budget, venue, guest count
See your whole wedding in one calm place.
Budget, guest list, timeline, and a to-scale floor plan that update each other. Try every Premium tool free, and pay once only when you are ready to save your work.
Try Altessa Premium freeNot ready for an account? Grab the free budget template. No signup, no email.
Comparing options? Altessa vs. the spreadsheet · vs. The Knot · vs. Zola