The day-of message: what to send your guests

Every message you have sent so far had to fight for attention — the invitation, the reminders, the requests to RSVP. The day-of message is the exact opposite: it is the one message your guests are actually waiting for. The wedding is today, the outfits are ready, and every guest wants three simple things — when to arrive, how to get there, and where they are sitting. That is why this message gets opened more than anything else you send — and why it is the worst one to get wrong.

What must the day-of message contain?

Four things: the exact arrival times, a navigation link, the guest's own table number, and the link to the shared photo album. Everything else is optional.

• Exact arrival times — not "in the evening" but when the reception starts and when the chuppah does. A guest who wants to catch the ceremony needs to know it is at 20:00; a guest aiming for the reception knows how much slack they have.
• A navigation link — one link that opens straight in Waze or Maps, not a free-text address to copy by hand at a junction.
• The personal table number — a guest who arrives already knowing where they sit skips the crowd around the seating board at the entrance.
• The shared-album link — guest photos start landing in one place from the reception onwards, with nobody to chase the morning after.

What does a good day-of message look like?

Short, warm, and all facts. Something like this:

Hi [name] 💚 We can't wait to see you tonight at [couple]'s wedding!

Reception: [time] · Chuppah: [time]

[venue], [city] — directions: [navigation link]

We saved you a seat at table [table number].

Caught a great moment? Upload it to the shared album: [album link]

See you tonight!

Notice what is missing: no emotional paragraph, no story, no requests. Your guests got all of that in the invitation — tonight they only need the details.

When do you send it — in the morning, or a few hours before?

On the morning of the wedding. Guests coming from far away build their whole day around the event: leaving work early, arranging a babysitter, working out who drives with whom. A message sent three or four hours ahead lands after all those decisions were already made — for a guest facing a two-hour drive it is simply too late. A morning message is read over coffee, and everyone plans the day around it. Where this message sits in the full messaging calendar — from the Save the Date to the final reminder — is a guide of its own; here it is enough to know it is the one that closes it.

Who gets it?

Only guests who confirmed. A cheerful "see you tonight!" landing with an aunt who regretfully declined weeks ago is the classic embarrassing mistake of the wedding morning — and it tells the guest your list is not really managed. Non-responders should not get an automated table-number message either: if you truly want them there, a personal phone call that morning does the job far better. The practical meaning: the list must be filtered by RSVP status automatically — not in a manual spreadsheet at eight in the morning of your wedding day.

Why can't it be one copy-paste broadcast?

Because the table number differs from guest to guest. One broadcast can carry the time and the directions, but not each guest's table — and writing "table numbers are on the board at the entrance" gives up exactly the detail guests need most. In practice the message is assembled per guest: their name, their table pulled from the up-to-date seating chart, and their personal album link. Doing that by hand for 400 guests is a full day's project; it is precisely a job for a system.

Why short and functional, not another emotional message?

Because this is a service notification, not an invitation. The emotion already happened — in the invitation, the reminders, the anticipation. On the day itself a guest is not looking for feeling in a message; they are looking for a time, an address and a table, ideally in a five-second glance while getting ready. Think of a boarding pass: every detail on it is there because it is needed. A long, emotional message buries the important information under text — and the guest hunting for the start time on the way out simply won't find it.

What happens to the album link after the wedding?

It keeps working — during the event and after it. Whoever shoots on the dance floor uploads on the spot; whoever remembers only the next day opens the same message and uploads from there. Everything lands in one event album instead of scattering across chats — no WhatsApp group, no manual collecting. How to run the album itself — how long to keep it open, what about privacy — is the full guest-album guide; what matters here is that the link travels in the one message everybody opens.

How do you actually send it?

In Weddigo the day-of message is built into the system: every confirmed guest gets a personal message on WhatsApp — through the official WhatsApp Business API — or by SMS, with their name, the times, the navigation link, the table number pulled straight from the live seating chart, and their personal link to the Snapigo album, which opens in the browser with no app and no QR code. The list is filtered by status automatically — whoever declined simply is not on it.

The invitation finished its job when you got an answer. The day-of message does its job when every guest arrives on time, sits at the right table — and leaves you the photos of the evening.