For the family marking the years
For most events the invitation follows the announcement. For an anniversary it is the announcement. So the message that goes into the family chat should open on a page with the evening laid out and a reply button underneath.
A wedding invitation arrives after everyone has heard about the wedding. An anniversary invitation often carries the information itself: that it is the fortieth, that the children are doing something, that there is a restaurant booked on the far side of town and a coach nobody has mentioned yet.
That puts an odd demand on the message. It has to be the news, the invitation and the practical detail at once, which is why it usually ends up too long for a chat and too short on the parts people need. Then the questions come back separately to whoever sent it.
Splitting the job works better. Write a short line in the chat, and let the page underneath do the explaining. The headcount takes shape while you are doing something else, which is the correct way to organise an evening you are supposed to be celebrating.
Anniversary guests ask the same set of questions in a predictable order:
Anniversary is not one of the dedicated event designs yet; on the app it appears among the occasions still to come. What you get today is the same thing the platform puts behind any gathering, and for an anniversary it is enough: a shareable event page, replies tracked in one guest list, reminders to the people who have not answered, and a link you can forward without it degrading.
So the useful decisions are content decisions rather than design decisions. Decide what the page has to answer in one read, decide who the host name is, and decide the reply deadline, which for an anniversary is usually pinned to a restaurant booking or a venue minimum.
If the evening involves people travelling, keep that section short and specific: the arrival day, where you have put them up or recommended, and who they call if it goes wrong. Anniversary gatherings mix generations, and the eighty-year-old guest needs different information from the cousin driving an hour.
Three tones: the couple's own, the children's, and the long-married friend group.
Forty years, and we're not letting it pass quietly. Dinner at the Riverside on Saturday 3 October from seven. Everything, including where to park and who to ring, is on this page. Please reply there so we can confirm the table.
We're throwing an evening for Mum and Dad's anniversary on the 3rd. The Lindqvist family are all in, and we'd like the old friends there too. Address, timings and a reply button are on the page. Keep it from them until they arrive.
Silver anniversary, forty of us, one restaurant. The page has the date, the address and the dress note. Put your name down by the 20th and tell us what you eat.
Guests upload pictures through the QR code on the table, so the evening's photographs come back to one gallery rather than nine chat threads the family group will never find again.
A moderated guestbook collects what people want to say about the years. You approve before anything shows on the page, which is worth having when three generations are typing.
A livestream link slot on the page lets someone join the toast from a hospital bed or another continent, without becoming a technical conversation in the chat.
A countdown sits on the page while the date approaches, which keeps the evening in mind for the people who meant to reply and got on with their week.
How it works
Tell Jitabi what is being celebrated, the date, the venue and who is hosting. It drafts the page from your chat messages, so the notice can go out the same evening the idea does.
Directions, parking, transport or hotel notes, and the one contact number for the day. Anniversary guests span ages, so write the arrival detail for the least confident traveller.
Switch on the reply form with meal choices and allergies, cap plus-ones as the table needs, and pick a closing date that lands before the restaurant needs a number.
Publish so the link opens for guests, post it in the family chat, then send reminders to the outstanding names. Watch the headcount arrive instead of assembling it by memory.
Questions
Not yet. Anniversary is listed among the designs still to come. Today you build on the general event page, which carries the sections an anniversary evening needs, including timings, venue and directions, the dress note, the reply form and the gallery afterwards.
Yes, and it often works better than splitting them. One page, one date, one guest list, with the wording clear about both occasions and both names on the invitation. If the celebration stretches over a weekend, a multi-day timeline handles it.
Whichever name guests would think to call. When adult children arrange the evening, saying so on the page answers the question of who is hosting and who collects replies, and stops the couple being asked about the catering.
The page helps but cannot do it alone. An unpublished draft is invisible to guests, and password protection limits who gets in once you send the link. Beyond that it depends on the family chat, which is a matter of trust rather than software.
For a dinner, yes, and it is worth asking on the page rather than at the table. Meal choices and allergies come back attached to each reply, so the booking you make with the restaurant is based on real numbers.
Get Started
Put the evening on one page, send it into the chat where the family already are, and let the replies build the headcount while you get on with the celebrating. Start free.
