Skip to main content

Here is an example of my issue.

Any idea of how to workaround it?

Let's say I will open a time slot for 20 people tomorrow at 08:00. a parent with 2 kids will only be counted as 1 with 19 remaining places and I need to be counted a 3 with 17 remaining places.

I don't wont the parent to make 3 separate reservations

Hi gayaland,

Right now there is no perfect way to do this. However, some workarounds might help. Additionally, I’ve marked this as a good idea in our system and will make sure our Product Team sees this request. 

Firstly - the workaround of a parent making multiple reservations with a Group Event Type, is not what you are looking for, but is a workaround we suggest. I know this is less than desirable, but it works. 

Secondly - with one-on-one event types you can toggle on an ability for the person booking to add guests when doing so. They enter multiple email addresses and all of those are invited to the one-on-one event type. 

With this in mind - perhaps you can set up two event types. One for those that wish to sign up with a group, and one for those that wish to sign up individually. The event types would be “backwards” - you’d use a one-on-one for those that wish to sign up with a group so that they can add guests and sign up everyone at once. Then, you’d use a group event type for those that wish to sign up individually. Make sense? 

You can also use routing to help make this more seamless. Routing forms let you request information such as industry, company size, specific interests, etc. from website visitors and automatically direct them to a specific scheduling or web page based on their responses. It's great for screening and qualifying sales leads on a website or matching clients or students to the booking page of the right subject-matter expert based on their interests, program, or other criteria. You can read more about setting up routing forms, here!

In your use case, you’d ask a question on the routing form, such as, “Do you plan to sign up as an individual or as a group?” and based on their response have them routed to the appropriate event type - avoiding user (invitee) errors!