Every guest gets their own
invitation, and you get a number.
Send one private link per person. They reply yes or no, say how many of their party are coming, name who they are bringing and answer your questions. You see coming, not coming, still waiting — and how many people to actually cook for.
Included in the Event Pass · $39 once · No subscription
The guest’s phone at /i/ plus their private token. The same invitation, one tap apart: declining adds a single optional note box, saying yes unfolds the party count, the plus-one names and your questions.
- 1
Declining grows one field. Tap “Can’t make it” and the page adds “Anything to add?” and the send button. No party count, no questions — a required question only ever binds a guest who is coming.
- 2
The party count is capped. The dropdown offers 1 up to the number you invited them for. The server re-clamps it too, so a hand-made request cannot confirm five people against an invitation for four.
- 3
Your questions, after yes. A free-text box or a dropdown that opens on “Choose…”, with a mint asterisk on the ones you made required. They appear only once a guest has said they are coming.
- 4
No login, no app. The private token in the address is the entire credential. The page opens with the guest’s name and the number they were invited for, and it is kept out of search engines.
An invitation that answers back
Not a card you email and then chase by text. A page per guest that takes their answer and files it where you can count it.
One link per guest, with their name on it
Everyone on your list gets their own address — /i/ plus a private token — and the page opens with their name on it and the number they were invited for. No app, no account, nothing to install.
Yes or no, in two taps
The reply is two large buttons. Everything else — how many are coming, who they are bringing, your questions — only appears after a guest has tapped yes, so declining takes one tap and nothing more.
How many of the party are actually coming
A guest invited for four can confirm two. They cannot confirm five: the reply is capped at the number they were invited for on the server, not just in the form. They can name the people they are bringing, which is what name cards need.
Your own questions, not ours
Ask what you actually need to know: a free-text box, or a list of up to 8 choices to pick from, 20 questions in all. Mark one required and a guest who is coming has to answer it before their reply will send — someone who is declining is never asked.
A reply date that closes the form itself
Set the date you need answers by. After it passes the form closes and tells guests to contact you directly. The deadline is enforced on the server, so a tab left open since last week cannot slip a reply in behind it.
A note straight to you
Every reply can carry a note — the allergy, the late train, the reason they cannot come. It arrives attached to that guest's answer instead of scattered across your text messages.
How it works, screen by screen
All four steps live on one tab of your event — Guests — beside the seating chart and the list of people who sent a photo.
Put your list in
Paste it from a spreadsheet or add people one at a time. Each guest gets their own invitation link the moment they are added, and the number you invited them for goes in beside them.
Left: the guest list before anyone is on it. Right: the paste box, the notice a good import leaves behind, and the refusal an oversized one gets instead.
- 1
Nothing to generate. Every guest gets their own invitation link the moment they land on the list. There is no separate “create links” step and no waiting.
- 2
Columns are worked out, not configured. Comma or tab separated, header row optional. Without a header the first column is the name, an @ decides the email, and a one or two digit cell is how many they are invited for.
- 3
Re-paste a corrected sheet. People are matched by email and updated in place rather than duplicated, and their existing invitation token is carried through — so fixing a typo in a name does not break the link you already sent them.
- 4
Too big means nothing imports. Up to 2,000 rows in one paste. Go over and the whole paste is refused with the count, rather than importing the first 2,000 behind a success message.
Fill in the invitation
Your message, where it is, what to wear, the date you need replies by, and any questions you want answered. There is no template gallery to choose from — it is a form, and the result is a clean page rather than a picture of a card.
The whole authoring surface: three cards and one Save. No wizard, no preview pane, no theme picker.
- 1
Your message, up to 2,000 characters. A counter runs underneath it. The location and the dress code are one line each, and any of the three you leave blank simply does not appear on the guest’s page.
- 2
Reply by, as a date and a time. After it, the invitation still opens but the reply buttons close — and the server returns the same refusal to anything that posts late.
- 3
Up to 20 questions. Each one gets a “Required” box and a “Pick from a list” box that reveals up to 8 options. They are asked only of guests who say yes.
- 4
One Save, no publish step. “Saved. Every invitation link shows this now.” There is no draft to promote and no second button — the links you already sent show the new wording.
Questions are optional. Leave the box empty and the invitation says so in as many words — “No questions yet. Guests will just reply yes or no.” — and your guests get a two-tap invitation with nothing else on it. A half-typed question is dropped when you save rather than blocking the whole form, and a pick-from-a-list question you emptied of options quietly becomes a text box again.
Send it out
Copy a guest's link from their row and send it however you already talk to them, or write to the whole list from inside Picsui. Every email carries that person their own link, so replying to a reminder is one tap rather than a hunt through old mail.
The composer, and what lands in a guest’s inbox. Five kinds of message, five audiences, five merge fields — and no link to paste, because the template puts each person’s own one in.
- 1
Five audiences. Everyone on the list, Still waiting to reply, Coming, Can’t come, Not arrived yet — each with its own count in the dropdown.
- 2
The number before you send. It is worked out with the same function the server uses, so the number on the button is the number that receives it. Anyone with no email address is named as skipped before the send, not discovered after it.
- 3
Each email carries that person’s link. There is no link merge field to paste, on purpose: the template injects it. The button reads “View your invitation”, or “RSVP now” on a reminder.
- 4
Then a per-person record. Sent, Delivered, Queued, Skipped, Bounced or Failed — one row per recipient, with the reason next to the ones that did not go.
Watch the numbers move
Invited, Coming, Waiting, Can't come — and People expected, updating as replies land. Chase only the guests who have not answered, then hand the expected number to the caterer.
The guest list with replies in and the first parties through the door. Five numbers, four of which are filters, over one row per invitation.
- 1
People expected is the fifth number. It adds up the confirmed party sizes of everyone attending. A guest invited for four who is coming alone adds one, not four. That is the number a caterer asks for, and it is the one tile that is not a filter.
- 2
Four of them are filters. Tap Waiting to see only the people who have not answered, then write to exactly them with the “Still waiting to reply” audience.
- 3
Three numbers that disagree on purpose. Invited for 4, 2 coming, 2 arrived — what you offered, what they accepted, who walked in. Collapsing them into one is what makes a door list argue with a seating plan.
- 4
The door is the same row. “Check in” becomes a mint “Arrived” as people turn up, and Export downloads the whole list as a CSV. Invitations, replies and the door are one panel, not three.
The one box you have to tick
Replies are off when an event is created. It is the single easiest way to send eighty invitations that nobody can answer, so here is exactly what it looks like from both sides.
Left: the first card of the invitation editor, before and after. Right: what a guest sees while it is off — the invitation, in full, with the reply buttons replaced by one grey line.
- 1
Off until you tick it. “Collect replies” ships switched off. Leave it and guests open a perfectly good invitation onto a grey box that tells them to contact you directly — the single most likely first-run mistake in this feature.
- 2
One box, and the buttons appear. Tick it and every invitation link you have already sent starts taking answers. You can turn it off again at any point and the invitation itself keeps working.
One link, and it keeps doing things
The address you send is not spent on the RSVP. It is the same page a guest comes back to when their plans change, and the same page that grows the rest of your weekend onto it — each part appearing only if you set it up.
Coming back to the same link. The heading is now “Your reply”, their answer is filled in, and the button reads “Update my reply”.
Further down the same invitation: the weekend schedule with its own replies, the gift registry, the photo gallery and “Find your table”. An invitation to a simple party shows none of it.
What the host sees
People expected, not invitations sent
Alongside Coming, Waiting and Can’t come, there is a fifth number: People expected. It adds up the confirmed party sizes of everyone attending, which is the number a caterer and a venue ask for and the one a count of invitations can never give.
What a guest’s row actually tells you
A badge for coming, waiting or not coming, and one grey line under the name: their email, the number you invited them for, the number they confirmed, and how many of them have walked in. Four facts that can all be true and all different at the same time.
The rest comes out as a file
Export downloads the list as a CSV with ten columns — name, email, phone, invited for, RSVP, confirmed, bringing, arrived, note and invitation link. The plus-one names and the notes live there rather than on the row.
Plans change, and that is fine
A guest who already replied sees their own answer under the heading “Your reply” and can change it until the reply date passes, with the button now reading “Update my reply”. Better a corrected answer on the invitation than a text message at eleven at night.
A guest list that is not a public page
Every invitation page is kept out of search engines, and its address is 24 bytes of random token rather than a name or a number — so one guest’s link reveals exactly one invitation and never the list it came from. A link that has been deleted and a link that never existed return the identical message.
Only you can open the host side
The guest list and the invitation editor are owner-only: both resolve the event against your own account, and no guest token opens either. Check-in is deliberately not a link you can forward, because a forwardable door link lets a guest check themselves in.
Included in the Event Pass, and it never locks you out
Invitations, replies and the door are part of the Event Pass at $39, paid once. A free preview event can open every one of these screens and read everything on them; what needs the pass is changing things — adding a guest, importing a list, saving the invitation, checking someone in.
The same rule protects you afterwards. If a pass lapses, nothing you collected is taken away or hidden: the list, the replies and the CSV export keep working, and only the edit buttons come back with a message. Locking a host out of data they already collected is not a paywall.
What a write looks like without a pass. Export — and the list behind it — is untouched.
What we have not built yet
All five of these are worth knowing before you buy, so they are on this page rather than in a support reply afterwards.
No template gallery
You fill in a message, a location and a dress code. There are no themes, fonts, colours or photo on the invitation, so the result is a clean readable page rather than a picture of a card. If a designed invitation is the thing you are shopping for, this is not that product yet.
No SMS
Invitations travel as a link you can send by any means you like, or as an email to your guest list from inside Picsui. Nothing here sends a text message, so anyone who needs texts should send the link from their own phone.
No bulk link copy and no per-guest QR
Links are copied one row at a time with the copy icon, or sent for you by the email composer. There is no “copy all links” button and no sheet of guest QR codes to print.
The answers to your own questions are not shown yet
Guests’ answers are collected and stored, and the reply itself is enforced against your required questions — but nothing in the dashboard displays them back to you, and they are not in the CSV export either. This is the honest gap in the feature and the next thing to fix in it.
No phone or tag field when you add one guest
A pasted spreadsheet can carry a phone number and tags such as a side or a group, and search matches those tags. The one-at-a-time form asks only for a name, an email and how many they are invited for.
Questions hosts ask
Do guests need an app or an account to reply?
No. The link opens a plain web page in whatever browser is on their phone. There is no download, no account and no password for a guest — the link itself is the way in, which is why each one is private to that person.
Do I have to turn RSVP on before sending invitations?
Yes, and it is the one thing worth checking first. “Collect replies” is switched off until you tick it. With it off, guests still see the invitation but cannot reply — they get a grey box reading “Replies are closed for this event. Please contact the host directly.” Tick the box, and every link you have already sent starts taking answers.
Can one guest reply for their whole party?
Yes. A guest invited for more than one chooses how many are coming and can name the people they are bringing. They can confirm fewer than they were invited for, and never more: that rule is held on the server, not only in the form.
What happens after the reply date passes?
The form closes itself. Guests who open the link after the deadline see where they stand — coming, not coming, or no answer given — and are told to contact you directly. The server refuses a late reply as well, so a tab left open since last week cannot slip one in.
Can I ask my own questions on the invitation?
Yes. Add up to 20 questions, each as a free-text box or a list of up to 8 choices, and mark any of them required so a guest who is attending has to answer before their reply will send. Someone who is declining is never asked, because nobody who cannot come should have to say what they would have eaten.
Can I see the answers to my own questions in the dashboard?
Not yet, and it is better said here than discovered later. Answers are collected, stored and enforced — a required question blocks a reply without one — but nothing in the guest list displays them back to you, and they are not in the CSV export. The names, the confirmed numbers, the notes and the arrival counts all are.
Can a guest change their answer later?
Yes, any time until the reply date. They open the same link, see the answer they gave under the heading “Your reply”, and the button now says “Update my reply”. The counts move with them.
How do I get my guest list in?
Paste it from a spreadsheet, or add people one at a time. A paste can be comma or tab separated, with or without a header row: without one, the first column is the name, an @ decides which column is the email, and a one or two digit cell is how many they are invited for. Up to 2,000 rows in a single paste.
What happens if I paste more rows than the limit?
Nothing is imported, and you are told how many rows it saw. That is deliberate: importing the first 2,000 and reporting success is how a host loses the back half of their list and only finds out at the door. Paste the rest in a second go.
What if I paste a corrected spreadsheet a second time?
People are matched by email address and updated in place rather than duplicated, and their existing invitation token is carried through unchanged — so correcting a typo in someone's name does not invalidate the link you already sent them. Guests with no email are always added as new rows.
How do the invitations actually go out?
Either way round. Copy one guest's link from their row and send it however you already talk to them, or use the message composer: pick a kind — save the date, invitation, reminder, update or thank you — pick an audience, write the body with {first_name}-style merge fields, and send. Every email carries that person's own link under the line “This link is yours alone. It has your RSVP on it.”
Is the guest invitation link the same as the invite link for helpers?
No, and they are worth keeping straight. A guest invitation lives at /i/ plus their private token: no login, no roles, just their RSVP. A collaborator invitation lives at /invite/ plus a token, offers a Viewer, Moderator or Admin role for helping run the event, and does require the person to log in.
Who can see my guest list?
Only you. The guest list and the invitation editor both resolve the event against your own account, so no guest link opens either one, and the same rule is enforced in the database. Door check-in is owner-authenticated for the same reason — a forwardable door link would let a guest check themselves in.
Are there limits on what I can write?
Yes, and they are the same numbers in the form and on the server: 2,000 characters for your message, 200 each for where and the dress code, 20 questions with up to 8 options each, 300 characters for a guest's answer and 500 for their note.
Are there invitation templates to choose from?
Not yet. There is no template gallery today: you fill in a message, the location and the dress code, and the invitation is a clean, readable page rather than a designed card. If a designed invitation is the thing you are shopping for, this is not that product yet.
Can invitations go out by text message?
No. Invitations go out as a link you can send by any means you like, or as an email to your whole guest list from inside Picsui. There is no SMS sending today, so anyone who needs texts should send the link through their own phone.
What happens to my replies if my Event Pass lapses?
You keep every one of them. Reading is never gated: the guest list, the replies and the CSV export all stay open. Only changes are held back — adding a guest, importing a list, editing the invitation or checking someone in — and the message says so plainly: everything you have already added stays exactly where it is.
What do digital invitations and RSVP cost?
They are part of an Event Pass at $39, paid once, with no subscription. The same pass covers the guest photo gallery, the digital guestbook and the live slideshow for that event, so the invitation and the photos afterwards are one purchase rather than two products.
Send the invitations, then keep the photos
The same Event Pass that carries your invitations and replies also collects every guest photo, voice message and guestbook entry from the day itself. One purchase, one link, from the save-the-date to the album.