RSVPs Not Accepting, Cannot Figure Out Why

Valentina Rodriguez

• November 08, 2025 14:18

RSVP is open; but the website is saying we are not accepting additional.

We have a custom plan that should not require an upgrade. Appreciate any support 

0

• Official comment

  

  RSVPify Support Team

  • November 08, 2025 16:40

  Hi Valentina 👋
  
  Thank you for reaching out!

  It sounds like your RSVP form is technically open, but your event website is showing the “We are not accepting additional RSVPs” message. This can happen if:

  • Your event capacity or guest limit has been reached, even if the form itself is marked as open.

  • The RSVP block or form section was duplicated or edited after publishing, causing the public-facing website to display an outdated status.

  • There’s a custom message configured for closed forms that’s still showing due to a cached or scheduled state.

  Here’s what to check first:

  1. Go to Form Builder → RSVP Block Settings → Capacity & Availability, and make sure the total guest or block capacity hasn’t been hit.

  2. Open your event website editor, and verify that the RSVP section or “RSVP Now” button is still linked to the live form URL (you can append ?view=Form to force the correct view).

  3. If you’ve scheduled your RSVP to open/close automatically, double-check the date and time in your Event Settings → Publishing → Schedule RSVP to Open/Close, sometimes the schedule overrides manual settings

     
     

     Schedule RSVP to Open / Close

      

  Because you’re on a custom plan, this isn’t a plan limitation; it’s almost certainly a configuration or sync issue. Try republishing your event website after confirming those settings.
• 

  Tylor Corwin

  • February 11, 2026 08:15

  Hi Valentina,

  This usually happens when there’s a limit or restriction set in the event settings, even if the RSVP is technically open. I’d recommend double-checking your capacity limits, ticket availability, and cutoff rules in the dashboard. Sometimes a hidden restriction can stop new responses.

  We ran into a similar issue while managing online form workflows for a sassa application process, and reviewing the form limits and submission rules solved it. Hopefully, checking those settings helps you resolve this quickly!

  0

Please sign in to leave a comment.