Use this page when registration is blocked
Registration problems can affect attendance fast. The goal is to identify whether the issue is with the event setup, the attendee form, checkout, capacity, or the link being used.
Do not ask attendees to send private payment details. Ask for the visible error, device or browser, and the step where they got stuck.
Troubleshoot the registration path
- 1
Open the public event link
Use a private window so you can see what an attendee sees.
- 2
Check registration state
Look for full, closed, waitlist, pending approval, sold out, or payment-required states.
- 3
Review required fields
Long or unclear custom questions can make attendees think the form is broken. Confirm required fields are visible and answerable.
- 4
For paid events, check checkout readiness
Make sure tickets are visible and payment setup is ready enough for checkout.
- 5
Collect support context
If the issue continues, send support the event link, attendee step, visible error, browser or device, and approximate time.
Likely causes
| Symptom | What to check |
|---|---|
| Button missing | Event may be draft, closed, full, cancelled, or viewed through the wrong link. |
| Form will not submit | Required fields, email format, duplicate registration, or validation errors. |
| Checkout fails | Ticket state, Stripe setup, payment method, or checkout handoff issue. |
| Attendee says they registered twice | Search by email in the attendee list and check duplicate or status behavior. |
Support details to include
Event link or slug.
Whether the attendee is trying free RSVP, waitlist, approval, or paid checkout.
The exact step where they got stuck.
Visible error message, if any.
Browser, device, and approximate time.
No full card, password, bank, identity, or private attendee data.
Event-day urgency
If registration is blocked right before a live event, say that in the first line of your support request.
FAQ
Should attendees create an account to RSVP?
Guest RSVP should not require a HereNow account unless the specific workflow says otherwise.
What if only one attendee has the issue?
Ask for their device, browser, step, visible error, and whether another browser works. Avoid collecting sensitive payment details.
What if everyone is blocked?
Check event status, capacity, visibility, registration settings, and payment readiness, then contact support urgently.
Was this guide helpful?
Your answer helps us keep product guidance clear and current.
Related guides
Collect RSVPs without requiring attendee accounts
Attendees can register as guests. Ask for only what you need, then manage the list from your event tools.
Read guideWhat attendees see after RSVP or payment
Attendees need to know whether they are confirmed, pending, waitlisted, paid, or need to take another step.
Read guideTroubleshoot paid tickets not appearing
Ticket display usually depends on event publish state, ticket settings, capacity, payment readiness, and page visibility.
Read guide