Editing Waiting List Forms
Updated over a week ago

Member Splash provides the ability to automate your waiting list signup and membership offer processes. While we typically set up the waiting list form for clubs as part of their initial onboarding process we describe below how to add one to your site or edit your existing one.

PLEASE NOTE: Your waitlist form is set up by your on-boarding technician based on your needs at setup. We highly discourage clients from altering a waitlist unless they have advanced Gravity Forms & Feed knowledge . The correct mapping of fields is critical to creation accounts and any incorrect alteration will keep accounts from being created.

Waitlist or Wait List? Actually It’s Waiting List!

Waitlist is a verb that means to put someone on a waiting list. Waitlist, or wait list, is a common but incorrect American shorthand for waiting list. So use Waitlist or Wait List as you like — neither one is right!

Establishing a New Waiting List Form

Your waitlist form is set up by your on-boarding technician based on your needs at setup. If you would like to try setting up a new waitlist form start by copying your existing form and giving it a new name. To do that hover over your existing waitlist form and select duplicate.

Editing a Waiting List Form

Once the Waiting List Application form exists on your site (or Wait List / Member Application — see above!) you can edit it by going to the Forms menu and hovering over the form name which will cause a list of editing options to appear below it.

The Waiting List or Member Application that Member Splash uses is designed to capture the minimum of information required to create a new account: The applicant’s name, address, email address and phone number. Club’s are welcome to capture / require as much additional info. as they choose but that information will only be captured in the form entry record, not the Member Splash account.

For example, if your club requires that prospective members be sponsored by a current member in good standing you might choose to require the sponsor’s name. That information will be accessible in the form entries but it will not be added to the pool account that is created.

The reason we currently only capture minimal account information is that for many of our client clubs the wait list is years long. Rather than collect information that may well be outdated if / when someone is offered membership we have them enter their current info. at the time the offer is made.

Each of the required fields is mapped to Member Splash account fields via the Advanced Tab on the field editor. Click on any form field and it will expand to show you the settings for that field:

Member Splash uses the dynamic population option to assign names to the form fields. In the case of the name field we assign first_name and last_name. That is what allows the system to capture those fields and use them to create the billing contact for the new Member Splash account. Each of the required fields is assigned a specific name this way.

  • First Name: first_name

  • Last Name: last_name

  • Street Address: street_address

  • City: city

  • State: state

  • Zip / Postal Code: zip

  • Email: user_email

  • user name*

  • Password*

In the case of the First and Last name you can look under the Advanced section of the Name field to see the parameter names used in the dynamic population of the fields

The account that is created is set to the account type that is your default account type, typically the waitlist account type. See Member Splash Setting for more details.

If you want to manually set the payment status of new accounts you can do that by adding an additional hidden field called Payment Status. Choose to allow it to be dynamically populated and set the field name to pay_status. Then put the status you desire as the default value — either paid or unpaid.

You can optionally elect to capture home, cell and work phone numbers. Those are mapped to Member Splash separately, via the User Registration settings as are the User Name and Password fields.

Did this answer your question?