Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Bookings made by a non-attendee "booker"? | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › Bookings made by a non-attendee "booker"?

Bookings made by a non-attendee "booker"?

Posted: October 24, 2013 at 8:26 am

Viewing 1 reply thread


Emily Petch

October 24, 2013 at 8:26 am

Hi,

We are looking at starting to use Event Espresso for our system but just wanted to check that it does meet all our needs. This may be an obvious question but could a “booker” book attendees onto an event without them booking themselves to attend? We often have delegates booked in this way but need an auditable trail of who made all of our bookings (i.e name, contact details, etc for the booker as well as delegates).

Many thanks,

Emily


Dean

  • Support Staff

    •

October 25, 2013 at 3:52 am

Hi Emily,

What you could do is set up the Primary Attendee (always the first person being registered) to have a group of questions related to who is arranging the booking. That way you can gather your info trail but the person doesn’t need to register themselves.
Viewing 1 reply thread

The support post ‘Bookings made by a non-attendee "booker"?’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Status: closed

Updated by Dean 11 years, 4 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server