Locked RSVPs on Free
Over the Free plan's monthly limit, RSVPs are still accepted. Their details are hidden until you upgrade.
WhoComing never turns a guest away because of your bill. On the Free plan, once your organization reaches its monthly RSVP limit (see plans and limits), the next RSVPs are locked:
- The guest sees the normal success message and gets the normal confirmation email, with their manage link.
- Counts stay accurate. Capacity and the waitlist work as usual.
- You can see that the RSVP exists, but not who it is.
What a locked RSVP looks like
Everywhere you read RSVPs (the API, webhooks, the dashboard and CSV exports), a locked RSVP has locked: true and no personal details:
{
"id": "rsvp_...",
"event_id": "evt_demo0000000000000001",
"mode": "live",
"name": null,
"email": null,
"status": "going",
"guests": 1,
"answers": null,
"source": "embed",
"locked": true,
"checked_in_at": null,
"created_at": "2026-11-20T18:02:11Z",
"updated_at": "2026-11-20T18:02:11Z"
}Your code should treat name, email and answers as nullable anyway: they are also null after the retention period.
Unlocking
Locks clear when you upgrade to Starter or Pro, or at the start of the next month. Nothing needs to be re-sent: the RSVPs were already confirmed.
GET /v1/usage reports how many RSVPs are locked this month in rsvps.locked.
Test mode is never metered, so test RSVPs are never locked.