Skip to main content
Free Auto Planning Tools|Proudly serving all 50 U.S. states, and beyond

Guests, RSVPs & Check-In

Build your RSVP form

Start from a template, add the questions you need, set a deadline, and preview it before anyone sees it.

On this page

What it is

The form your guests fill in. You choose the questions, their order, whether each is required, and the settings around it — deadline, welcome message, confirmation message, language and more.

When to use it

Before you share anything. The link you send points at this form.

Who can use it

The event owner, and platform staff.

Where to find it

  • Open an event → RSVP Forms
  • The finished form lives at /rsvp/ plus your event name

Before you start

  • An event. A guest list is helpful but not required — anyone with the link can reply.

Step by step

  1. Open your event and choose RSVP Forms.

  2. Pick a starting template: Wedding, Corporate, Birthday, Gala, or Custom to start from scratch.

    A template is only a set of starter questions. Delete or rewrite any of them.

  3. Add fields. Ten types are available: short text, long text, email, phone, date, number, yes/no, multiple choice, checkboxes, and dropdown.

  4. For each field, write a clear label, mark it required if it truly is, and add help text where the question could be read two ways.

  5. Open Settings and set the RSVP deadline, a welcome message, and the confirmation message guests see after replying.

  6. Preview the form and fill it in yourself once.

  7. Save.

What you should end up with

A form at your event's RSVP link that collects exactly what you need, and replies that land in Guest Management.

Options and settings

Deadline
After this moment the form closes and shows a closed message instead of accepting replies.
Welcome message
Your words at the top of the form. Use it to say what the event is and when to reply by.
Confirmation message
What a guest reads after submitting. A good place to say what happens next.
Plus-one limit
Caps how many extra people one guest may bring.
Maximum guests
A total cap on replies for the event.
Waitlist
Once the cap is reached, later guests join a waitlist instead of being turned away, and are promoted if space frees up.
Accessibility needs
Adds a question asking whether a guest needs anything to attend comfortably.
Sub-events
Lets guests reply separately to parts of a multi-part event, each with its own capacity.
Reminders
Automatic nudges a set number of days before the deadline.
Language
The form's own labels and buttons in English, Spanish or French. Your question text is shown exactly as you wrote it — it is not translated.
Conditional questions
Show a field only when an earlier answer matches, so guests are not asked about the dinner they are not attending.

Common mistakes

  • Sharing the link before saving, so early guests see the template questions.
  • Marking everything required. Guests abandon long compulsory forms; require the name and the yes/no, and little else.
  • Adding questions after replies have started. Early repliers never answered them, and those answers stay blank.
  • Setting a deadline in the past, which closes the form immediately.
  • Writing question text in another language and expecting the language setting to translate it. That setting only changes the form's own buttons and labels.

If something goes wrong

Guests say the form is closed.
The deadline has passed, or the maximum-guests cap is full. Extend the deadline or raise the cap and ask them to try again.
A conditional question never appears.
Check the rule points at the right earlier field and the value matches exactly, including capitalisation.
The form saved but the public link still shows the old version.
Reload the public page. If it persists, open the builder and save once more.
A sub-event refuses a reply with a capacity message.
That part of the event is full. Raise its capacity or leave it — the guest can still reply to the other parts.

Worth knowing

  • Fill your own form in on a phone before sharing it. Most guests will.
  • Ask for dietary needs as a free-text field rather than a fixed list — someone always has a requirement your list did not imagine.

Still stuck? Tell us what you were trying to do and what happened instead.

Contact support