Most wedding invitations are delivered in a chat thread now. Not in an envelope, not by post: a message on a phone, read one-handed, somewhere between two other things. That is mostly good news. It is instant, it costs nothing, and it reaches the aunt who has not opened an email since 2019. It also means your invitation arrives in the same place as delivery notifications and group chatter, and a few small decisions separate the guest who answers from the guest who means to.
Send a link, not a picture
The most common mistake is attaching the invitation as an image or a PDF. It fails in four ways at once. Chat apps compress photos, so the type you chose carefully arrives soft. Guests have to pinch and drag to read an address. Nothing can be corrected once it is sent, so if the venue changes, the wrong version stays in a hundred threads forever. And there is no way to answer from it, which pushes every reply back into chat.
A link solves all four. It stays sharp on any screen, it shows the current details because it is the current details, and it can carry the reply form itself.
Check the preview card before you send
Paste a link into a chat and WhatsApp fetches the page and builds a small card: a title, a line of description, a thumbnail. For most guests that card is the invitation. It decides whether they tap.
So look at it before anyone else does. Send the link to yourself first, in the “Message yourself” thread, and give it a second to load. The title should name the two of you, not read “Home” or the name of a website builder. If no card appears at all, the page has nothing for WhatsApp to read, and your invitation arrives as a bare blue string of characters.
Write a short message and let the page do the rest
The page carries the details. The message only has to make someone tap it, so keep it to a few lines. Three that work:
For family and anyone close:
We’re getting married on Saturday, March 14, and we would love you there. Everything is here, including the reply form: [link]. Could you let us know by February 1?
For friends:
We’re doing it. March 14, in Savannah. Details, directions, and RSVP: [link]
For a group thread, where the message is read by people at different distances from you:
Sharing our invitation with all of you: [link]. The date is Saturday, March 14. There’s an RSVP form on the page, and it helps us a lot if you can answer by February 1, even if it’s a no.
Two things worth including every time: the date, so it is legible without tapping, and the reply deadline. “Even if it’s a no” is not filler either. It measurably raises the number of people who answer.
Send it in the right order
Parents, siblings, and anyone in the wedding party get an individual message first. Nobody who is close to you should learn the date from a group thread. Give that first round a day to land before anything else goes out.
Then everyone else, individually where you can manage it. A message addressed to one person is answered far more often than the same words in a group of forty.
Groups last, and only where a group already exists for its own reason: the office, the neighbourhood, a family thread that has been running for years. Do not create a group for the wedding. It will fill with questions that belong on the page and stay noisy for months.
If you are sending to many people at once, a broadcast list is better than a group, because each person receives it as a private message and cannot see the others. One catch decides whether it works: a broadcast only reaches people who have your number saved in their contacts. Guests who have not saved you get nothing, with no warning to you. Use it for the crowd you know well, and send individually to everyone else.
Collect the answers on the page, not in the thread
If replies come back as chat messages, your guest list lives in fragments across thirty conversations, and you will be counting by scrolling at midnight. Some answers arrive as “yes!!”, some as a voice note, some as a maybe that never resolves.
An RSVP form on the invitation itself fixes the shape of the answer: a name, yes or no, how many are coming, a note if they want one. Every response lands in one list. State the deadline next to the form, not only in your message, because the message is scrolled past and the page is not.
Remind once, and only the people who owe you a reply
Send the invitation once. Then wait. About two weeks before your deadline, message the people who have not answered, individually, and only them. A second reminder to someone who already replied reads as though you did not notice.
A status update is the gentler option for a general nudge: it reaches everyone who has your number, and it pings nobody. Post the invitation there once, close to the deadline, and leave the direct messages for the people who genuinely have not answered.
Where Goldypaper fits
All of this assumes the link you send is worth tapping. That is what Goldypaper makes: you pick a theme, Elegant is the quiet classic, fill one form, and publish a single URL that is built to be opened on a phone from a chat. It comes with the preview card filled in, the details you can still correct after sending, and an RSVP form that puts every answer in one list. Building and previewing are free; publishing costs US$19, once. Start an invitation, or browse the themes first.