An event RSVP page is a web page where guests confirm attendance, choose options such as a meal or session, and get a confirmation. With an AI builder you describe the event, the questions and the capacity. It stores responses, stops at the limit, shows a live count and can sell tickets through your Stripe account.
- Ask only for answers that change a decision: headcount, meals, sessions and access needs.
- A hard capacity limit needs a seat count that updates in one step, so the last place goes to exactly one guest.
- Check guests in by a short code. An exact code lookup stays fast at any list size; name search only suits small lists.
- Emails and paid tickets run on your own email (SMTP) and Stripe accounts and stay off until you add the keys under Integrations.
- Free WisyLink links last 30 days, so for an event further out, move to a paid plan before the invitations go out.
What an event RSVP page should collect
Three terms get mixed up, and the difference decides what you build:
- RSVP page
- A free reply form for invited guests: yes or no, how many, and a few details such as meals.
- Event registration page
- A sign-up for a public or semi-public event, usually with a capacity limit and sometimes session choices.
- Event ticketing page
- Registration that takes payment and issues a ticket for each paid order.
Apply one rule to every field: if the answer won't change what you order, print, seat or prepare, don't ask it. Long forms lose replies, and every answer is personal data you must look after.
- Name and email. Email sends the confirmation and lets guests change their reply later.
- Attending: yes or no. Leave "maybe" out; nobody can cater for a pile of maybes.
- Party size with a name for each guest. Named plus-ones give you a seating list and badges, not just a number.
- Meal choice as fixed options, so the caterer gets a clean count per dish.
- Dietary needs and allergies as free text, kept with the guest's name so the kitchen knows who has what.
- Session choice for conferences and meetups, each with its own limit if rooms differ in size.
- Access needs, phrased as "Anything we should know to make the day work for you?"
Skip phone numbers unless you will send texts, postal addresses unless you mail something, and birth dates always.
Build it in one prompt
The fastest route is one complete message. Write down the facts a builder can't guess: event name, date, start and end time with timezone, venue address, capacity, RSVP deadline and a contact for questions. Then fill in this template:
Build an RSVP page for [Mia and Leo's wedding] on [Saturday 12 June 2027], [4 pm to 11 pm, UK time], at [venue name and full address]. Capacity is [120] guests.
Ask each guest for: name, email, attending yes or no, number in their party (up to [2]) with a name for each person, a meal choice ([beef, fish or vegetarian]) per person, dietary needs or allergies, and [a song request].
Count every person in a party against capacity and never accept more than [120], even if two people submit at the same moment. When full, offer a waitlist. Show "[X] places left" on the page.
Give each guest a short confirmation code and a private link to change or cancel their reply until [15 May 2027]. Add an admin area with all replies, totals per meal, the waitlist, a check-in screen for the door and a Download CSV button. Send a confirmation email, and a reminder one day before the event, once I add my email settings. Style: [warm evening tones, deep green and gold, elegant serif headings]. Keep the site out of search engines.
- Send the prompt in a new WisyLink chat on the web or in the mobile app. If something material is missing, Wisy asks one short question; otherwise the build starts.
- Watch the build. A live task list shows the work, and the page goes live at its own
https://<id>.wisylink.comaddress when it finishes. - Read the final note. It tells you how to reach the admin area and which settings are waiting for you, such as email or a password.
- Add credentials under Integrations, never in the chat. Until you do, the features that depend on them stay off.
- Test as a guest on your phone. Reply, change the reply, cancel it, then fill the event with test entries and confirm the next guest lands on the waitlist.
- Clear the test data in the admin area, or ask in the chat to remove those exact records.
- Share the link on your invitations, or as a QR code on printed cards.
On the free Community plan, Wisy keeps each build to a lean first version, with one build per 5-hour window. If the first build skips the waitlist or the check-in screen, ask for it next, and group related changes into one message. For more prompt patterns, see these AI website builder prompt templates.
Capacity limits and a waitlist with no overbooking
Yes, you can limit the number of guests, and the limit holds. Form tools and shared spreadsheets oversell for a simple reason: two people read "1 place left" at the same second, both submit, and both get in. WisyLink's data layer changes the count and checks the limit in a single step, so when two replies race for the last place, one succeeds and the other is told the event is full.
Decide three things before you build, and put them in the prompt:
- Parties at the edge. If two places are left and a party of three replies, should the page refuse, or accept two and waitlist one? Refusing is simpler and avoids splitting families.
- How the waitlist moves. Automatic promotion emails the next person the moment someone cancels, which suits free meetups. Manual promotion, a button in the admin area, suits weddings, where you choose who fills a gap.
- Offer deadlines. If a promoted guest must confirm within, say, 48 hours, a background job releases unclaimed places. Those jobs run every 30 to 60 minutes, so a released place reappears within the hour, not to the second.
Make capacity an admin setting rather than a number fixed in the page. If the venue adds a room, you change one field, with no rebuild. Events with several time slots work like a booking system with one limit per slot; our guide to building a booking website with AI covers that setup.
A live attendance count and a door check-in list
The public "places left" line updates by itself: saved data reaches visitors within about a minute of each reply, without a rebuild. Admin pages are never cached, so a refresh always shows the current list. At the door you need more than a list:
- Look guests up by code, not by name. The data layer matches exact values but has no free-text search, so a code lookup stays instant at any size. Typing part of a name only works for lists small enough for the browser to filter, roughly 100 guests; for bigger lists, ask for an A to Z filter by last name.
- Show the code as a QR code on the confirmation page and in the email, with a scan screen for volunteers' phones. Test the scan on those phones, in the venue's lighting, before the day.
- Give volunteers a narrow role. A "door" role can check people in without seeing emails or dietary notes.
- Keep two entrances in sync. Ask for live updates, so a guest checked in at one door shows as checked in at the other within seconds.
- Print a backup. Venue signal is often poor. Download the CSV and print the list before doors open.
Confirmation and reminder emails
A built app sends email through your own SMTP account, entered once under Integrations. Until then, email steps send nothing and the rest keeps working: guests still see an on-screen confirmation with their code. Three details decide whether emails arrive and help:
- Send from your own domain. Use an address such as hello@yourevent.com and add your email provider's SPF and DKIM records to the domain's DNS, or invitations drift into spam.
- Time reminders realistically. Reminders run as a scheduled job every 30 to 60 minutes, not at an exact clock time; "one day before" goes out on the first run after that point. Schedules have no timezone of their own, so give the hour in UTC or state your offset.
- Plan for big lists. Each run sends a small batch, so a reminder to several hundred guests spreads over several runs, and your email provider's sending limits apply too. Schedule it a day or more ahead.
A good reminder carries the time, address, a map link, the guest's code and a cancel link; every early cancellation frees a place for the waitlist. Ask for an "Add to calendar" file on the confirmation page too.
Paid tickets through your Stripe account (optional)
To charge for entry, ask for checkout through your Stripe account. Payments go straight to that account, which WisyLink never holds, and checkout stays inactive until you add your Stripe keys under Integrations, where the setup steps and the webhook address to register in Stripe appear.
The flow that keeps the count honest: when a guest starts checkout, the app writes a pending order and holds their places. The ticket is issued only when Stripe's signed webhook confirms the payment, never because the guest reached a "thank you" page. Stripe's guide to fulfilling Checkout orders explains why: a customer can pay and lose their connection before that page loads. Abandoned holds are released by a background job that runs every 30 to 60 minutes, so near sell-out the page can briefly show "full".
Refunds are issued from your Stripe Dashboard. Stripe's refund documentation states that processing fees from the original payment aren't returned, so set your refund policy with that in mind, and ask for a "refunded" status in the admin area that frees the place.
| Question | Free RSVP | Paid ticketing |
|---|---|---|
| Add to your prompt | Capacity, questions, waitlist, confirmation code | All of that, plus ticket types, prices, currency and Stripe checkout |
| When a place counts as taken | The moment the reply is saved | Held at checkout, confirmed when Stripe's webhook arrives |
| Owner setup | SMTP for emails (optional) | Stripe keys and webhook, plus SMTP for ticket emails |
| Cancellations | Guest cancels with their link; the place frees at once | You refund in Stripe and mark the order refunded |
| Best for | Weddings, parties, free meetups | Workshops, classes, paid community events |
Private events: a password gate or invite codes
A wedding or staff party shouldn't be open to anyone who finds the link. Two tools combine well:
- Password gate. One shared password protects every page. You set it under Integrations, and the site stays open until you do, so check from a private browser window that the gate appears.
- Invite codes. Each household gets its own code. Entering it shows that household's names and allowed party size, so a forwarded link can't add strangers. Attach your guest list as a CSV and explicitly ask Wisy to load the households with their codes during the build.
Also ask to keep private pages out of search engines. Public events want the opposite: event details in Google's Event structured data format. Google supports it only for events at a physical location that the general public can book, and doesn't guarantee they'll be shown.
After the event: export and follow-up
Plan the week after the event before you build:
- Download the attendance CSV: who replied, who came, who waited.
- Thank attendees by email, and send no-shows the slides or recording instead.
- Ask two or three questions in a short feedback form while memories are fresh.
- Collect photos through an upload page. Each file can be up to 25 MB and counts against your plan's storage.
- Delete what you no longer need. Dietary and access notes are sensitive; after export, ask in the chat to remove them.
Check the calendar against your plan. Free Community links stay live for 30 days, then spend one more week marked for deletion, and are deleted with their data unless you upgrade. Invitations often go out weeks or months ahead, so build and test for free, then move to a paid plan before you send them. On a paid plan, from $7 a month, links don't expire while you're subscribed. Your own domain works on any plan; see how to connect a custom domain.
Start your RSVP page today
Write down the event facts, paste the template, and test the page as a guest before you share it. If you are gauging interest before a date is fixed, a waitlist landing page is the better first step. Browse the use cases for other event formats, and compare plans when the link needs to outlive 30 days.
Describe your event in one message and get a live link: start free on Community, no card required.
F.A.Q.