Help Documents - Version 5 Add Registrant TypesHow do I test my Registrant Type displays?

How do I test my Registrant Type displays?

No matter how simple or how complex your registrant type definitions become, you need to thoroughly TEST EACH ONE because the registrant type determines what combinations of data capture fields, questions, sessions and ticket purchase options are presented to the registrant.

Does your Admin Dashboard have Menus or Buttons?

rsvpBOOK has 2 versions of the Admin Dashboard. Which one do you have?

Does your Admin Dashboard have Menus or Buttons?

If Menus, your Registrant Type display tools are located here ...

You can test your registrant type displays on the Admin Dashboard, upper left corner. You have 2 ways to test your Registrant Type display combinations:.

  1. Click the View Event button - Registrant will be able to select the registrant type in a dropdown menu on the landing page
  2. Click the Event URL button - Registrant will NOT be able to select the registrant type because the landing page is pre-populated with the registrant type already selected

View an example of each of these 2 methods below.

 

If Menus, your Registrant Type display tools are located here ...

If Buttons, your Registrant Type display tools are located here ...

You can test your registrant type displays on the Admin Dashboard, upper left corner. You have 2 ways to test your Registrant Type display combinations:.

  1. Click the View Event as Registrant button - Registrant will be able to select the registrant type in a dropdown menu on the landing page
  2. Click the View Registrant Type URLs button - Registrant will NOT be able to select the registrant type because the landing page is loaded with the registrant type already selected

View an example of each of these 2 methods below.

 

If Buttons, your Registrant Type display tools are located here ...

1. View Event as Registrant or View Event button

Your Landing Page will open and display a dropdown menu containing your registrant types. The registrant may change the registrant type selection at any time.

1. View Event as Registrant or View Event button

2. View Registrant Type URLs or Event URL button

Opens a screen with a list of all of your registrant types along with a link to that registrant's Landing Page. Clicking the Open in New Window link will open and display your landing page as that registrant type would see it.

Each Registrant Type has a unique URL assigned to it. If you use the Registrant Type URL in an invitation and when clicked, a landing page will open with the registrant type already selected and cannot be changed by the registrant. This is useful for eliminating problems created by registrants selecting and registering under an incorrect registration type. It requires time for you to sort out and resolve these problems. If you use a registrant type URL embedded into an invitation, all recipients of that invitation will ONLY be able to register under that type. Therefore, you shouldn't "mix" registrant types in a contact list.

Landing page displays with the registrant type pre-selected

The Landing Page will open and display the registrant type ALREADY SELECTED, and, it cannot be changed by the registrant - they are locked into this registrant type.

This is useful when you send invitations to various groups, such as Attendees, Exhibitors, Sponsors, Vendors, etc. Registrant types cannot view other registrant type's options.

Landing page displays with the registrant type pre-selected

Testing each registrant type ...

Using either method, dropdown menu (PUBLIC) or unique URL (PRIVATE), display the registration page for each registrant type and visually make sure it is correct.

Are the correct About You fields, Questions, Sessions and Ticket options displaying for that registrant type? You must visually verify that all registrant type options are displaying correctly.

Do this for EACH of your registrant types. TEST, TEST, TEST. - this is the rsvpBOOK mantra; memorize it.

0 Comments

Add your comment

E-Mail me when someone replies to this comment