Build and Manage an Event - Step 2

We recommend that you first fill in some basic details about the event before you continue to more advanced details such as the event agenda or accommodation.

Best Practices

Best Practice: Title

Title is the actual name of the event.

The title is what you would put on collateral and programs.

The title can be included dynamically in emails, websites, confirmations, etc.

The title should remain the same across communications.

Best Practice: Unique Code

Unique Code is generated automatically by the system unless you have a particular reason to do otherwise.

The unique code is the key for all the event's data.

The unique code keeps each separate event's data together.

Some organizations choose to select a unique code that reflects an internal tracking number used in other systems.

Best Practice: Location

Location is the place where the event will be held.

Select (or add) the location where the event will be held.

If the venue doesn't already exist in your account-level Suppliers database, add it as a new supplier.

Best Practice: Contact

Contact is the person who will receive all primary correspondence from attendees.

Select (or add) the person who will receive all primary correspondence from attendees.

Like suppliers, these contacts are maintained at the account level so that you can use them in multiple events.

If this is a team, we recommend establishing a generic email address such as registrationsupport@example.com.

Important: the email address must be working.

Best Practice: Plan > Configure > Options

Plan > Configure > Options is a navigation path.

Prompt User for Optional Notes After Each Change is a feature that will prompt you every time you change details in a registration or profile. We recommend leaving this feature switched off unless you need to track the actions of a large number of Certain users. During testing, keep the feature turned off.

Best Practice: Functional Areas

Functional Areas simplify the Certain interface during the event creation and management process.

We strongly recommend turning off those areas that you know for a fact you will not use.

For instance, if you do not process credit card payments for your events, disable the E-commerce functional area of the Financial Module.

By disabling unused functional areas you will simplify the interface you will use to set up and manage the event.

Best Practice: Plan > Event Setup > Attendee Types

Attendee Types can be used to charge fees, set inventories on certain types of attendees, and restrict people by passcode.

Also, keep in mind that the report on the Event Dashboard (Manage > Registrations), Completed Registrations by Attendee Type, will display a row of data per attendee type.

The Code should be short – this column will be seen frequently in reports, so it's best if it's concise.

Best Practice: Plan > Event Setup > Custom Statuses

Use the Custom Statuses section to define custom registration processes that cannot be easily handled by the built-in registration statuses.

Create statuses in order to track processes unique to your business.

For instance, you could create statuses that track speakers for the event like this:

Needs to submit abstract
Abstract under review
Speaker abstract approved

Best Practice: Step 3

Once you've entered basic event details, move on to Step 3: Create and Customize Registration Forms.

Note

Note: Help topics may include features to be released.

Related actions

Have more questions? Submit a request.

Build and Manage an Event - Step 4

Comments

0 comments

Please sign in to leave a comment.