For the one keeping the secret
The hard part is the secret, not the cake. A password-protected page, replies that do not tip anyone off, and careful wording keep the surprise standing until the door opens.
A surprise depends on many people staying quiet, and WhatsApp is a machine for accidentally not doing that. A screenshot lands in the wrong chat, a well-meaning cousin types party into the family group, and the whole thing dies in a notification. The logistics are easy; the secret is the part that fails.
The rule for this guide is one sentence: move the plan out of the messages and onto a page. Details, replies and reminders live behind a link, and the group chat carries nothing sharper than a date and an address.
Work these decisions off before a single invite goes out:
Three messages, each with a different job.
Lukas turns 30 on Friday. The actual party is a surprise at 7, but tell no one outside this chat. Details and a password are on the page here: [link]
Keep Friday free for a quiet dinner, just us. No need to plan anything. I will book the table.
Arrive between 6:30 and 6:50, not after — the plan runs on the Lindqvists' walking time. Reply on the page if your timing changed: [link]
The invitation page sits behind a password you share inside the secret group. The guest of honour being handed the link by accident reveals nothing; there is no page to open without the word, and the chat itself never has to say more than a date.
Every yes or no lands on your live list instead of in the family group, where a stray reply is a spoiler. Nobody types celebration into the wrong thread because the wrong thread never needed a word.
A countdown and a reply deadline on the page tell guests when to arrive, which keeps late questions out of the chat. Anyone still silent as the deadline passes gets one host-triggered reminder — from you, quietly, not from the group.
Surprises leak; plan for it. Because the page is a proper birthday invitation, not a fake one, the fallback is gentle: change the page's arrival time, delete the surprise line, and it becomes the party you were always going to have, just announced two days earlier. Nothing about the link, the list or the reminders goes to waste when the twist fails.
No tool sends the invite for you, reads your chats, or hides messages from the guest of honour's phone — those claims belong to someone else. The page only keeps the plan and the count. The secret lives in the boring places: a private group you chose, a password you hand out deliberately, and wording that never says the word surprise where a notification might.
How it works
Build the birthday invitation in the web app, or message Jitabi on WhatsApp with the plan: a surprise 30th, Friday, doors at 6:30, the party proper at 7. Keep it unpublished until the guest list is final — an unpublished page is invisible to everyone.
Switch on password protection. Write the timing so it carries both halves: the arrival window for guests and the moment the guest of honour walks in. Leave a line of wording plain enough to survive being read over a shoulder.
Publish, then post the link in the secret group with the password sent alongside it. Ask everyone to reply on the page and to keep the group free of spoilers from this moment on.
Watch the live guest list fill, remind the non-repliers as the deadline passes, and on the evening follow the arrival window yourself. The cake, the lights and the timing are yours; the counting is handled.
Questions
Three layers do the work: send the link only in a group they are not in, keep the page behind a password, and make the chat wording harmless in case a screen is glanced at. A bare link plus no password plus no spoiler words is a dead end for a curious partner.
Say it once in the invite: replies go on the page, not the chat. Then send the reminder to non-responders from the page instead of asking the group again. Most leaks are just people being enthusiastic in the wrong room, and a clear rule keeps the room tidy.
No. Birthdays are a dedicated event type with a real template library, and a surprise uses exactly that machinery plus a password. The surprise is the logistics, not the design.
Set the plus-one limit on the reply form before publishing, so extra places only exist where you allow them. If a guest brings someone anyway, the door person improvises — but the list will tell you exactly how far off plan you drifted.
For a house surprise, roughly two weeks gives people time to protect the evening without letting the secret age. The page never adds risk by existing early: it stays unpublished until you decide, and then password-protected.
Add your co-conspirator as a collaborator with an access level you choose — one of you editing details, the other watching replies — so nobody is locked out at six o'clock holding a password they cannot find.
Get Started
Build the birthday page, lock it with a password, and let the replies land quietly. Your job on the night is the lights and the timing — not the hundred messages that could have given it away.
