Skip to content

Winglark

RSVP management

An RSVP is a promise. Manage it like one, and measure it against the door.

Replies, plus-ones, meal choices and the questions your event actually needs, collected on the same guest record that is scanned on the night — so the RSVP count and the attendance count can finally be compared by name.

RSVP management is more than a yes/no count. A reply carries a plus-one allowance, a meal choice, an allergy, a session or a transfer — and it changes: people who said yes fall ill, people who said nothing turn up. A tool that stores the reply apart from the guest list and apart from the door loses each of those facts at the point where it matters.

Winglark keeps the reply on the guest record. Every guest gets their own invitation link; their answer, their plus-ones and their choices land on that record, the latest reply counts and the earlier ones stay in the history. Silence is kept as its own state — “no answer” is never counted as “no” — because the people who never replied are exactly the ones a reminder is for.

On the night, the same record is what the door scans. That is what makes the attendance report honest: who promised and did not come, and who came without replying, by name.

What to look for in RSVP management.

The questions that separate a reply form from a reply record.

  • Does each guest reply from a link that is theirs, without creating an account?
  • Is “no answer” kept as its own state, or silently counted as a no?
  • Can a guest change their reply, and does the history stay?
  • Are plus-ones counted, asked the same questions, and given their own entry code?
  • Can the questions follow the event — meals and transfers for a wedding, sessions for a conference?
  • Does the reply live on the same record the door scans, so RSVP and attendance can be compared by name?
  • Can the whole thing be exported — replies, choices and attendance — to a spreadsheet or a PDF?

How it runs on Winglark.

  1. 01

    Set the questions for the event

    The event type brings its usual questions; add a free note field for anything else.

  2. 02

    Set plus-one allowances per guest

    None, one, several or open — a guest with an allowance names their plus-ones when they reply.

  3. 03

    Send the invitation with the reply block

    Each guest answers from their own link. The reply, the plus-ones and the choices land on the guest record.

  4. 04

    Watch replies arrive, and follow up the silence

    Coming, not coming, undecided, no answer — by segment if you tag guests; a reminder goes to those who have not answered.

  5. 05

    Read the gap after the door closes

    RSVPs against real attendance, by name, in both directions; export to CSV, Excel or PDF.

Questions

Which reply states are there?

Coming, not coming, undecided and no answer. The last is kept deliberately: silence is data, and it is never counted as a refusal.

Can a guest change their reply?

Yes. The latest reply counts and the earlier ones stay in the record, so you can see who changed their mind and when.

How do plus-ones work?

An allowance is set per guest. Each plus-one is named, counted, can answer the same questions, and gets a code of their own if the door is on — or the guest’s code carries the group and the door counts who arrived.

Can I ask my own questions?

Each event type brings the questions it usually needs — meal choice, allergies, transfer, session, attendance mode — and a free note field for anything else.

What about guests who never reply?

They stay “no answer”, a reminder can go to them before the event, and if they turn up anyway the door records them among those who came without replying.

Your first event is free.

Fifty guests, real invitations, real replies. No card required.

RSVP management for events · Winglark