Exploring some alternative registration use cases

When using a SpotMe registration page for your event, whether you are using public (open), private (RSVP), or a combination of public and private registration, it can occur that some of your registrants follow a slightly alternative approach when they register.

In this article we'll explore some of the most frequent use cases, and explain how the registration will take place.

Registrants can use the registration page to retrieve their existing registration if they have already registered to the event. This means that  (except for cancelled users). For registrants who register for for the event for the first time, there is no change

Previously RSVP registration was not possible for registrants unless they were specifically invited to do so first: only registrants accessing the RSVP page via a tailored link in their invitation email could respond to the RSVP and update their status. With this update, any registrant (whatever their invitation status) can now go to a registration page, follow the retrieve registration process that includes verification with the PIN code as described in this article, and reply to an RSVP invitation (without being specifically invited to do so / using a tailored link in an invitation email).

When setting up the registration page in your workespace and testing it (by registering to the event), please note that you will by default experience the retrieve registration with the request for accesss code. This is because you are already added as a user in the Users list in the workspace. Attendees who register to the event for the first time will not experience the retrieve registration, they will only experience it in the cases explained below.

When testing your registration page, we recommend that you register with a user with a new email address that does not match the user already present in the User list. You can for example use a "test" email address that can be "youremail+test@yourdomain.com", for example "john.doe+test@spotme.com", should your email provider support this type of alias usage, or any new email address that you have access to the inbox of.

Please be aware that the below described retrieve registration functionality will not work if the use of shared email addresses is enabled at the app level.

What happens if an attendee tries to register for an event that they have already registered for?

Your registrants may forget that they have already registered for your event, and may try to re-register for it.

Should this happen, this will be smoothly handled by the system, and the registration landing page will identify that the registrant's email address has already been used to register for the event.

In order to confirm that the registrant is indeed the owner of the email address associated with the existing registration, the system will send a unique confirmation code to that email address.

By accessing the email address, the registrant can receive and provide the unique code in order to retrieve their registration. This is process is explained in detail below.

STEP 1: The registrant enters their email address and clicks on Register now, or if they realize that they have already registered, they click on the Retrieve your registration link and the result is the same (they will be requested by the system to provide their email address):

STEP 2: Here the system recognizes that the email address has already been used to register to this event, and sends a unique code to the email address:

STEP 3: The registrant will receive and retrieve the unique 8-digit code in the inbox associated with the provided email address:

STEP 4: The registrant will now return to the registration page and enter the received unique code, in order to retrieve the existing registration:

STEP 5: The entered code is verified, and the registrant can access, edit (if enabled), and proceed with completing their registration, by selecting Next:

Note: If attendees are already logged into the registration page, for example by following a magic link in an email that includes authentication, they will not be prompted to receive an access code as described above. The access code is only used for attendees who are trying to log-in or access their profile via the registration page itself.

What happens if an attendee that is on the user RSVP list tries to register to your event via a public (open) registration page?

Remember that a registrant who has or will be invited to register to your event via a private RSVP invitation email (with a tailored "Will you attend" link) will already by default be added to the user list in the workspace.

If you are using a combined public (open) and private (RSVP) registration page, it can however occur that your RSVP attendees attempt to register via the event's public registration page (instead of responding via the RSVP invitation email link).

If this occurs, the registration landing page will identify that the registrant's email address is associated with an "RSVP" user in the event, and will send a unique confirmation code to that email address, exactly as explained above.

By accessing the email address, the registrant can access and provide the unique code in order to retrieve, respond to (or edit, if enabled) their RSVP registration ( with "Yes, I will attend"  or "No, I will not attend"), and pursue by selecting Next:

What happens if an uninvited invited person tries to register for an event that is only meant for RSVP invited participants?

As mentioned above, an attendee who is invited to register to your event via a private RSVP invitation email will receive an email containing tailored "Will you attend: YES / NO" RSVP buttons, as well as a link to the registration landing page.

As such, if the RSVP registration page link is shared, through forwarding the invitation email or by copying/pasting/sharing the registration page URL, the person will not be able to register for the event with an email address that is not on the invitee RSVP list, and will see the following:

How does this registration retrieval work if SSO (Single Sign On) is enabled?

If your registration page has SSO (Single Sign On) enabled, please see below the behavior for attendees who register. The below is applicable whatever the registration page type (hybrid or not):

Public (open) registration with SSO:

Attendee registers for the first time via the open (public) registration page using SSO.	User is registered.
Attendee who has already registered via the public (open) registration returns to the registration landing page and tries to register again using SSO.	User public registration is retrieved without having to provide the verification code.

 

Private (RSVP) registration with SSO:

Attendee registers for the first time via the private (RSVP) registration using SSO.	User is registered.
Attendee registers for the first time via the private (RSVP) registration using SSO. Attendee who has already registered via the private (RSVP) registration access the registration landing page and tries to register again using SSO.	User RSVP registration is retrieved without having to provide the verification code.