One link opens a real event page — RSVP in a tap, ask CakeBot anything, reserve a gift, and check in with a QR pass. No app to download, no account to create, no password to lose.
They open one link and get their own schedule, a QR pass for the door, and CakeBot to ask anything — no app to download, no password to remember.
Everything you need, on one page.
Every guest gets their own concierge, but you keep one operational view — RSVPs, tasks and risks — with CakeBot keeping it current so you're not chasing updates.
60 guests · registration open
The same link carries a guest from invitation to check-in to the photos afterward — on whatever phone they already have.
No app, no account, no password. They tap once and they're on the list.
Timing, dress code, directions — answered from what the organizer shared, any hour, without pinging them.
Their pass lives on their phone. Scanned on the day — no printed list, no queue.
A nudge before a deadline closes or a moment they don't want to miss — sent once, not five times.
Reserve something from the registry so nobody doubles up, or pool a contribution by UPI.
Everyone's photos land in one place, uploaded by a magic link — no sign-up, again.
The page adapts to what you're running — so nobody gets a wedding RSVP for a hackathon.
Conference — registered, badged, in the right hall. Hundreds of people, several tracks running at once, and nobody at the door holding a printed list.
Your custom questions — role, company, anything you need.
Every session, every room, every day.
On their phone. Straight through the door.
Answered before they ask you.
Room change at 11am? Everyone knows at 11am.
Hackathon — 36 hours, everything on their phone. A running schedule that changes, and a few hundred people who need to know the moment it does.
Stack, team, t-shirt size — whatever you ask.
Kickoff, checkpoints, submissions, demos.
Deadline moved, judging starting — pushed to everyone.
Know exactly who actually turned up.
Capped out? They're notified when a spot frees up.
Team offsite — no more chasing the group chat. Sizes, diets, who's actually coming — collected without a single follow-up email.
T-shirt size, dietary needs, travel — stored against them.
Day by day, session by session.
Vote on dates, destination or the dinner.
Contribute by UPI, no spreadsheet.
Everyone's camera roll in one place.
Wedding — three days, one link. Mehendi, sangeet and reception each have their own time and place. Guests stop asking which is where.
Each with its own time, venue and dress code.
Recorded once, against their name.
They set the number themselves, up to your limit.
Reserve a gift so nobody doubles up, or chip in together.
Their photos go in afterwards, by magic link.
Community — invite the whole society. Hundreds of families, one link, and contributions that don't involve knocking on doors.
Even for the people who never use apps.
Chip in from the same page. No cash collection.
One message, the whole list.
They can see the turnout — if you make it public.
Regulars carried over to the next edition.
Birthday — send one link, get a real answer. No group-chat polls, no "so who's actually coming?", no duplicate gifts.
Going, maybe, can't make it. Done.
Kids and partners counted properly.
Reserve it, or everyone chips in for one big thing.
With directions, so nobody calls you at 4pm.
All in one album, uploaded by everyone.
After they've RSVP'd or registered, they get CakeBot on the event page — to ask about the event and manage their own details.
It starts after they're in. CakeBot appears once someone has RSVP'd or registered — they always do that on the event page itself, never through CakeBot.
Now it goes to CakeBot — which actually knows the answer.
So it doesn't. The wording follows the kind of event you're running.
Describe your event — every guest gets their own concierge from the first link you send.
Start now →To give everyone a world-class event planner.
