ChatGPT Forgets Your Guest List: Why an AI Chat Cannot Keep a Wedding Organized

The guest list is the one document every other part of a wedding depends on, and a chatbot is the one place it cannot safely live, because most AI tools don't carry information from one chat to the next. I've watched this happen to couples who are organized people. They build a beautiful list in a conversation in March, the conversation gets long and slow, they open a new one in April and paste the list in, and by June there are three lists in three chats and nobody is sure which one has the cousins' plus-one. I use Claude and ChatGPT every day. This is the job they're wrong for.

Why the list drifts

An AI chat is a conversation with a memory the length of that conversation. More than half of couples used AI somewhere in planning in Zola's 2026 First Look Report, so this is a common place for a list to start. Some tools now keep a loose memory across chats, a few facts about you, but none of them keeps a two-hundred-row table with a status per person that stays current when you change one cell. So every time you start a new chat, you're starting from whatever you paste in, and every paste is a copy. Copies diverge. The RSVP you recorded in the March chat never reaches the April one. The address you corrected in April isn't in the file you export in May. A guest list needs to be one thing, edited in place, and a chat is a stack of snapshots.

There's a second drift that's quieter. Ask the AI to reformat the list, or sort it, or add a column, and it rewrites the whole table, and somewhere in the rewrite a row goes missing or a plus-one becomes a guest. Models are good at prose and unreliable at copying two hundred rows exactly. Nobody notices until the caterer's count is off by four.

What staying organized actually requires

One list. One row per person, including children and named plus-ones. A household label so four people get one envelope. A group so the seating chart can use it. Each person's own email or phone, so a reminder goes to a person. An address on the row the envelope is addressed to. A plus-one status, an RSVP status, a meal, an age group, a table, and a notes field for the feud and the nut allergy. And a filter: show me everyone who hasn't answered, as of today. Why the list has to be right before anything else can be is here.

That is a database with a filter, and a chat window is the opposite of a database with a filter. It is very good at telling you what a guest list should contain. It cannot be one.

Where AI genuinely helps with the guest list

Deciding. Paste the long list from draft one into Claude and ask it to sort names into tiers by the rules you give it, and it'll do a fair first pass. Ask it to write the cutting rules so nobody has to defend a name. Ask it to draft the text to the aunt about the four uninvited kids, or the kind no to a coworker, or the RSVP chase message that gives people permission to decline. Ask it what to do about a divorced parent's new partner at the head table. Those are judgment and words, and the chat is excellent at both.

Then take the decision out of the chat and put it in the list. The chat decided; the list records. If you keep both jobs in the chat, the decision gets made twice and recorded nowhere.

The cost of getting this wrong

The guest count drives the catering bill, the rental order, the bar estimate, the seating chart, and the stationery order. Lose it, or let it drift into three versions, and every one of those is re-derived from memory three weeks before the wedding while you text a hundred people a question they already answered. It's the one data loss that reprices the wedding, which is why the RSVP chase is its own job. A chat loses it by design, because it was never designed to hold it.

Where Altessa fits

Altessa's guest list is the shape above: one row per person, with contact, address, group, plus-one, RSVP, meal, age group, table, and roles, a filter for no response, CSV import so the list you built anywhere comes in, and a one-click export so it leaves with you. A yes from the cousins adds two chairs at table nine on the floor plan and two plates on the catering line, because the list, the layout, and the budget share the same rows. It's a one-time purchase, free to start. Keep the chat open next to it for the words. Keep the list in the thing that was built to hold a list.

Questions people ask

Can I keep my wedding guest list in ChatGPT?

You can paste it there, but most AI chats don't carry it between conversations, and rewriting a long table drops rows. Keep the list in a spreadsheet or a planning app and use the chat for decisions and messages.

Does ChatGPT remember information between chats?

Some tools keep a loose memory of a few facts about you. None keeps a two-hundred-row guest list current across conversations. Each new chat starts from what you paste in.

What is AI good for with a wedding guest list?

Sorting names into tiers by rules you give it, writing the cutting rules, drafting the hard messages, and advising on etiquette questions. Then record the decision in your list.

What should a wedding guest list include?

One row per person with household, group, their own contact, address, plus-one status, RSVP, meal, age group, table, and notes, plus a filter for who hasn't answered.

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.