The 30 small asks every guest makes, and how to track them all

You don't need a bigger spreadsheet. You need somewhere to dump every small ask, the vegan aunt, the Saturday-only friend, the Sinatra playlist note from your father-in-law, into a single place that lets you ask, in your own words, what each guest needs. Save it, forget it, ask for it later.

It's a Tuesday night in June. Your phone has eleven open chats. Aunt Lisa just texted, "oh by the way Sebastian went vegan in March, is that ok?" Your maid of honor sent a Telegram voice memo about Cousin Marcus, who can only fly in for Saturday and needs the ceremony time confirmed. Your father-in-law forwarded a Spotify link with a note saying "maybe for the first dance section?" Two minutes later your photographer asks if Grandma uses a walker, because the aisle pavers are uneven near the arbor. You forward, screenshot, star the message, and tell yourself you'll move it into the spreadsheet tomorrow. Tomorrow becomes Thursday. By Saturday, three of them are buried under a registry argument.

Why the spreadsheet model breaks at ask #17

Open any wedding-planning-spreadsheet template on the first page of Google. You'll find columns for name, plus-one, RSVP, meal choice, table assignment, maybe gift received. Useful. Real. But none of those columns hold the actual ask. "Sebastian went vegan in March" fits nowhere. Neither does "Marcus can only Saturday", or "play the Sinatra version, not the Sammy Davis one", or "do not seat near Uncle Ron".

You make a notes column. The notes column becomes a wall of run-on sentences. By guest #40 it's unreadable. So you start a second sheet, then a Google Doc, then a Notion page, then the Telegram saved messages folder for the voice memos. Each guest now lives in four places, and the question "what did Aunt Lisa actually ask about Sebastian's meal" takes nine minutes to answer.

Most weddings draw enough guests that even a third of them making one specific ask leaves you with dozens of rows of free-form text your spreadsheet was never designed to hold.

Where the small asks actually live (and why that's the real problem)

Run the audit. Open your phone. Where did each of the last fifteen wedding-related messages land?

The bridesmaid group chat is on Telegram, because that's where you all moved after the third group fled WhatsApp. Your mom prefers iMessage with photos attached. Your three college friends DM through Instagram. Two voice memos sit in your Telegram saved messages folder, the kind you start when you can't find a real notes app fast enough. The caterer emails. The DJ texts. Your future spouse drops links into a shared Apple Note that neither of you opens after week two.

This is the part the guest-list-template never solves. It assumes a single intake form. Real life isn't a form. Real life is your father-in-law forwarding a Spotify link at 11:47pm on a Wednesday with no caption, and you needing to remember, five months later, what that link meant.

The save isn't broken. Telegram saved everything. You can prove it. The retrieval is broken. You can't find the right thing on demand, because searching by keyword fails when you can't remember exact words anyone used.

The 30 asks, sorted by where they actually arrive

Sit down with a coffee and write them out. Most couples land somewhere between twenty and forty. Here's the rough texture from real weddings:

Dietary: vegan, gluten-free, kosher, nut allergy, shellfish allergy, pescatarian, low-FODMAP. Mobility: walker, wheelchair access, stairs to avoid, hearing-loop seat. Timing: Saturday-only flights, Friday-only flights, redeye arrivals, kids with bedtimes, religious observance windows. Logistics: car service from the Marriott block, ride from the airport, baby formula on hand, pumping room. Seating politics: do-not-pair-with, please-pair-with, ex-spouse separation, the divorced parents row. Music and toast: requested songs, songs to avoid, toast volunteers, toast vetoes. The gift: registry receipt, monetary gift to acknowledge, donation in lieu of gift, the great-aunt's silver candlesticks.

You write thirty rows. Most are one sentence. None of them fit a spreadsheet's column structure. Each one arrived on a different surface: Telegram for voice memos, iMessage for screenshots, Instagram for late-night DMs, email for the caterer chain.

What "tracking" actually means when the ask is fuzzy

Forget the spreadsheet for a second. The caterer calls on a Thursday in October, six weeks out. She needs final meal counts by Monday. You have three minutes between meetings.

What you want: type "who has dietary asks" or "what did Lisa say about Sebastian" and see the answer. Not the row in the spreadsheet. The actual message, with the date, with the original wording. "Sebastian went vegan in March, is that ok?"

This is the gap. Saved messages folders, screenshots of texts, voice memos labeled "Lisa-Sebastian-vegan-v2.m4a" (you didn't really label it that, you forgot to label it at all). The information exists. The retrieval doesn't.

The fix isn't a better spreadsheet. The fix is being able to ask in your own words and get the answer back, without remembering whether you saved it to Telegram, screenshotted it, or wrote it down on the back of a wedding venue contract.

Building a one-place capture habit

The capture habit costs only a few seconds per ask, if you let it stay simple. Three rules that hold up under stress:

Send everything to one place. Pick one destination and stick to it. The Chrome extension, the Telegram bot, or the web app at dessence.ai all land in the same archive, so use whichever sits closest to where the ask arrived. The point is one destination, not the right destination.

Speak the guest's name in the message. Not as a tag, not as a column. Just naturally: "Aunt Lisa says Sebastian went vegan in March, ok for catering?" Then attach the original screenshot or voice memo. The name in the text is what lets you find it later.

Skip the categorization. No folders, no tags, no organizing. The vegan-aunt ask doesn't need to live in a "dietary" folder. It needs to be findable by "Sebastian" or "Lisa" or "meal" or "vegan" or "March". The way to do that is to write enough of the actual scene that any of those words could pull it back.

If you've ever opened your screenshot folder and found five thousand photos you'll never sort, you already know the failure mode. Save with no plan to retrieve, and you've built a private archive of things you'll never see again: the browser bookmark graveyard, but for wedding logistics.

Honest about dEssence

A few things to know if you're considering moving the wedding-asks pile into dEssence specifically.

It's in beta. The product works, but the paid pricing isn't finalized yet, and there's a cap on archive size for the free tier. Heavy savers will hit that cap.

No native iOS or Android app yet. Capture happens through the Chrome extension, Telegram bot, or the web app at dessence.ai, three co-equal save surfaces. If your in-laws live in iMessage and you want a Share Sheet button, that isn't here yet.

No team or shared-collection features. You can't co-own the wedding archive with your future spouse inside dEssence. For now, one of you owns the brain, the other gets read-outs.

If those tradeoffs are dealbreakers, Notion or a well-loved Apple Notes folder will hold the line. They won't search by meaning, but they will hold the data.

Frequently Asked Questions

Q: How do I track wedding guest asks across Telegram, iMessage, and email?

Pick one destination for every ask, no matter where it arrived. Forward iMessage screenshots into a Telegram chat, drop emails into the same chat, voice-memo your own thoughts into the same chat. The destination doesn't matter as much as the rule that there's only one.

Q: How do I make sure I don't lose a dietary restriction my aunt mentioned in March?

Write the guest's name and the substance of the ask in plain words when you save it. "Aunt Lisa says Sebastian went vegan in March" is searchable. A screenshot with no caption is not. Capture the context inside the message itself so future-you can find it five months later.

Q: Are wedding guest list spreadsheets worth using at all?

Yes, for what they're built for: name, RSVP, meal choice, table, gift received. Use them for the structured columns. Don't try to force free-form asks into a notes column, because that's where the system breaks.

Q: What if I get a request weeks after the seating chart is locked?

Save it the same way. Late asks are normal: a guest develops an injury, a flight changes, a kid's school schedule shifts. Capture in the same single destination and re-run the question when you do the final walkthrough with your planner.

Q: Do I really need a separate tool, or will Telegram saved messages be enough?

Telegram saved messages is enough if you keep the rule that every ask gets a written-out caption with the guest's name. Without that, the folder turns into a wall of forwards you can't search. Whatever tool you pick, the discipline is what works.

None of this requires new software. A Telegram chat with discipline beats most paid tools that promise to organize your wedding. If you'd rather not maintain that discipline, dEssence keeps the same one-place habit across the Chrome extension, Telegram bot, and web app, and adds search by meaning, so "who has a meal restriction" pulls Aunt Lisa's March message even when you've forgotten the wording. It's free during beta, no card, capped on archive size, and the iOS app isn't built yet. Save it, forget it, ask for it later.