Express Registration

Intro

Everybody has walk-ins. We want that to be as painless for all involved as possible.

Pain, though, sometimes is subjective. Pushing folks through the full public registration process is perceived as work. Express reg cuts out absolutely everything non-essential to the registration process. If it is imperative that you capture more than what ER allows, push registrants through the full process instead.

When SHOULD I use express registration?

1. When you know you'll be getting a nonzero number of people attending ONE event

2. When you can reasonably expect them to have a phone or tablet

3. When you're OK with a very skinny registration record

When should I NOT use express registration?

1. When you suspect people will end up wanting to sign up for multiple activities.

2. When the crowd isn't always online

3. When you want to maintain invite-only access

4. When you really need all of the custom or nuanced registration fields captured

How does it work?

1. You'll create one or more express reg configs - one per event that you wish to offer this service for.

2. Prospective participants can scan an event-specific QR code and add themselves (and guests) to the event.

The intent here is to reduce the demand on event staffing that would otherwise have to handle manual registration walk in entry.

This cannot ever be fully eliminated, however. Express registration helps but cannot solve - because humans will be humans.

What is captured for an express registrant?

1. First name

2. Last name

3. Email address (required for primary, optional for guests)

4. Pref class year (if applicable)

All registrants will come in as adult registrants. Maximum simplicity means minimum choice.

Configuration

Setup > Org Configuration > right side "Express Reg Config"

Select the org you want to build a config under and tap "Create Express Config"

At the conclusion of an express registration, all members of a party will be signed up under the package you select in the build. For this reason we STRONGLY suggest creating a very a la carte package (applicable to all registrant types) for this purpose.

Field	Purpose/Comments
is active	whether this ER flow is available for administrative and/or public use
is published	whether this ER flow is available to public registrants
enforce unique registration	when active, we'll look to see if there's an active registrant with the same XID and if so redirect them to self mod
do checkin	upon completion of express registration should we check the party in for the event? the answer depends entirely on whether you're scanning at the event or not
custom confirmation	after ER is complete should we show the usual registration group confirmation or do you want the registrants to see a custom message unique to this flow?
locked to	making it clear that anyone traversing this flow will be assigned to this org and registration group
package	VERY IMPORTANT consideration here that you assign the registrants to a very flexible/accommodating package (can even be unpublished). Typical users are casual participants who may want to add more on later - make sure there's plenty of flexibility here for both admins and registrants.
event	MOST IMPORTANT - which event is it we're trying to get access to veryfast? Once specified it cannot be altered.

Where does it show up?

Admin-facing ER flows appear when creating a new reservation.

Public-facing ER flows are not linked from any public webpages. You can grab the direct URLs to each ER flow from the setup screen as well as a handy QR code (which we encourage you to put on posters at the event) that will initiate the public-facing ER flow.