Collect RSVPs online with a page guests can answer in a minute
An RSVP page works when a guest can open the link, answer in under a minute and close it, with no account, no app and no password. The rest is question design: ask only what you'll act on, word it so the answers can be counted, and send each reply somewhere you can sort it.
No accounts, no friction
Every step you add costs replies: a sign-up, a confirmation email, a code to type. Guests who'd happily say yes put it off and then forget. An RSVP website on Anticode is a public page with a form; guests type their answers and press send. Nothing is asked of them beyond the questions themselves.
That openness has one consequence: anyone with the link can reply. For most parties, reunions and community events that's fine. If you're worried about strangers, ask for a name that you can match against your guest list, and treat unmatched replies with suspicion.
The questions to ask
| Question | Better wording | Why |
|---|---|---|
| Attending? | "Will you be there?" with Yes and No as the only answers | "Maybe" leaves you unable to plan |
| Name | "Your name, as on the invitation" | Lets you match replies to your list |
| Plus-ones | "Names of anyone else in your party" | A number isn't enough for place cards or a door list |
| Dietary needs | "Any dietary needs or allergies we should know about?" as free text | Tick boxes always miss someone's need |
| Access | "Anything that would make the day easier for you?" | Gets step-free and seating needs without singling anyone out |
| Contact | Email, if you'll send updates | Only ask if you'll use it |
Leave out questions you'll answer for guests anyway, like "Will you need parking?" if parking is unlimited. Every field you remove is a reply you're more likely to get.
Handling plus-ones
If only some guests may bring someone, don't put the rule in the form. Say it on the invitation, and on the page write "If your invitation includes a guest, add their name below." It's kinder than a form that refuses, and you can follow up the rare mistake by hand.
Setting it up in Anticode
Describe the event and the questions together: "an RSVP page for the Hartley Road street party on 21 June, asking name, attending yes or no, names of others in the party, dietary needs, reply by 1 June". The built-in forms have fixed fields, so a form with your own questions is a custom form tied to a site function: up to 30 plain-text fields, with your own heading and message on the thank-you page ("Thanks, see you on the 21st"). Check the preview to make sure the form asks exactly those questions, and ask for a change in a sentence if it doesn't. Put the reply-by date next to the button, not only at the top.
Each reply is saved in your dashboard and sealed at rest, and you can have each one emailed to you. A site that collects data can't be published until the account owner and the person publishing have two-factor sign-in on, so if someone else publishes for you, they need it too. The dashboard also keeps a log of the last 200 reads, exports and deletes of form data.
Sending replies to a Google Sheet
A spreadsheet turns replies into a headcount. Add the Google Sheets connector from the dashboard; it posts each reply as a row through a small Apps Script web app you add to your sheet. Then a filter gives you the yes list, and a column count gives you meals. Two practical notes: each reply is sent once with no retry, so the dashboard is the complete record; and if you edit the sheet's columns after connecting, check a test reply still lands where you expect. The Google Sheets guide has the setup steps.
The free plan's allowance
On the free plan a monthly allowance of submissions is visible to you (100 by default); replies beyond it are still saved but held until you upgrade. For a party of forty that's comfortably enough. For a large event, or one where many guests reply in the same month, check the allowance against your guest list before you send the link, and see /pricing.
Limits
- No reminders. Anticode doesn't email guests who haven't replied. Compare the sheet with your list and chase the gaps yourself.
- No edit link for guests. A guest who changes their mind sends a new reply; note it in the sheet.
- No capacity limit on the form. It won't close itself when you're full.
- Public page. Don't put private details, such as a home address, on it.
Questions people ask
Can guests reply without making an account?
Yes. The form is on a public page and asks for nothing beyond your questions.
What if someone replies twice?
Both replies are saved. Keep the later one; sorting the sheet by name makes duplicates easy to spot.
Can I use this for a wedding?
Yes, and the wedding website guide covers the rest of the site guests will want: travel, dress code and places to stay.