For hosts who read the room before they hit send
Group chats, forwards, relatives who take offence: the unspoken rules for sending an invitation by message. Keep them and the channel stops being the topic. The occasion is.
Every digital invitation eventually gets forwarded — a cousin passes the group message to a partner, a friend shares it with the work table. That is not malice; it is enthusiasm, and punishing it looks worse than the leak. The etiquette answer is to decide the matter in advance: keep a named guest list on your side, so the invitation quietly carries its own boundary. Someone forwarded a link can see the occasion and all its detail; whether they are invited is answered by the list you manage, not by the accident of who saw the message.
Guests who understand this stop worrying about leaks, and you stop worrying about forwards. The page is the pub; the list is the guestbook behind the bar.
The courtesies that keep an invitation-by-message from ruffling anyone:
Same event, three messages, each correct for its guest:
Anna — you and Piotr should be there. We're keeping it smaller than expected, but it isn't the occasion without you two. Everything is in the link, and just tap reply once you've had a look. Love, Marta and Tom
Good morning everyone — Marta and Tom are getting married on the twelfth of September in Utrecht. The invitation page here has the timing, the venue and how to let us know. Do please reply on the page rather than in this chat, so nobody's answer gets lost in the noise.
Dear Aunt Sofia — we would be very glad if you and Uncle Henrik could come to the wedding. All the details are on this page, and if it's easier, just ring me and I'll talk you through everything and note you down myself. With love, Marta
Older relatives often reach an occasion through a proxy — the niece who watches the family chat, the son who reads things aloud. Etiquette for them is the same courtesy with one addition: name who is answering. A single message addressed to a whole extended family lets one person decide for everyone, and the headcount arrives lumpy. Send each household its own link, say plainly that anyone in the message can reply on the page, and if the household answers as a bloc, accept that as the bloc's answer.
A guest types a warm yes in the chat and never touches the link. Resist the urge to quietly count them from the chat message — that is how double-counts and forgotten answers are born. Respond to the warmth, then send the link once more with a line saying the only thing left is a tap. The page exists so the yes lives in one place you can count, rather than in a chat you would have to re-read the whole week before the event.
How it works
Start free and put the detail on the page: timing, venue, dress, the questions relatives always ask (an FAQ section absorbs them), and a reply button with the deadline on it.
Close guests, group friends, older relatives — you already know who needs which kind of message. Jitabi can draft the wording so each circle gets a line that fits it.
Individual messages for the people who matter most, one group post for the casual circle, a call plus a link for anyone a chat would pass by.
Near the deadline, a reminder goes from the host side only to those who have not answered — a quiet nudge instead of a public re-ask in front of everyone.
Questions
For casual gatherings, no — that is where friendship lives these days. For weddings and milestone events, a blast to people who matter reads as an afterthought. Post to the group if you like, but back it with individual messages to everyone important, and ask for answers on the page rather than in the chat.
Match the effort to the relationship. Best friends and family get a message written for them. Colleagues and the wider plus-one tier are honestly fine with the group line. The rule: nobody close to you should ever feel they were messaged in bulk.
Nothing dramatic. Your named guest list decides who is invited; a forwarded reader sees the occasion, and that is the same as a card glimpsed on a kitchen counter. If they ask directly, be warm and honest — a genuine note about keeping it small ends the matter.
A casual birthday: two or three weeks. A wedding: several months, earlier still if guests must travel. Whatever the occasion, put the reply deadline inside the invitation so nobody has to guess how long they have, and the forwarded copies carry it too.
At least a few of them will try. Accept the warmth, then point to the page once — the answer needs recording in one place for the count to mean anything. A yes typed in chat and scrolled past is not an answer yet; on the page, it is.
Get Started
These rules are only ever about letting people know they were thought of individually. Build the page once, send each guest the message their relationship deserves, and let the reply button handle the rest.
