Role of the Default Booker

The Default Booker is a setting that applies to Queues. It can be found in individual Queue Settings under Online Booking URL. You can track the Booker of meetings by adding our Booked_By custom field to Salesforce. 

There are three roles in Chili Piper:

• Booker: Internal person setting the meeting
• Assignee: Internal person receiving the meeting
• Prospect: External person receiving the meeting (prospect or customer)

Chili Piper will attempt to use the permissions of the "Booker" to create a Salesforce event as well, when a meeting is booked via the Instant Booker. If the "Booker" has not connect his/her Salesforce account or the User does not have permissions to create a Salesforce event, Chili Piper will "fall back" to the permissions of the "Default Booker" to create the Salesforce event. 

Thus, it is very important that your "Default Booker" has connected Salesforce and has permissions to create Chili Piper Events and to write to the Chili Piper custom fields. For Google Calendar Clients, your "Default Booker" must also have a connected Calendar to their Chili Piper user. 

This article will cover the role of the Default Booker in the following scenarios:

• Default Booker: Concierge
• Default Booker: Queue and Other Links
• Booker: Instant Booker
• Set the Booker in Booking Links

Default Booker: Concierge

When you are creating a Queue, the creator of the Queue will automatically be set as the Default Booker. Online Booking URL must be on in order to set the Default Booker:

Concierge uses your webform to automatically book meetings [with a Prospect] for an Assignee. Therefore, there is technically no real booker setting the meeting. This is where the Default Booker comes in. We use the Default Booker as a proxy to book the meeting onto the calendar of the Assignee, therefore it is important that the Default Booker has their calendar connected to Chili Piper. We can define what this means in the Queue settings:

By default, the Meeting is created in: [the] Booker's calendar (assignee is invited). Since the Booker is the Default Booker, in most cases we will want to switch this so that the meeting is created in the Assignee's calendar, as shown above.

If you choose to check Booker Invited, then we will automatically invite the Default Booker to all of the meetings. If enabled, you will want to consider whether we should consider the Booker's availability when booking the meeting and/or if they should auto-decline when the meeting is booked:

Default Booker: Queue and Other Links

Queue Links

If you grab the Queue link from Online Booking URL to share in a marketing email, in a webinar, in a sales enablement cadence, etc the Default Booker will be considered the booker here as well. 

Router Links

The Queue a meeting was booked into determines the Default Booker

Meeting Type Links

These links are specific to a template and accessible by Workspace Admins and Master Admins. The user referenced in the link is the booker when a meeting is booked through meeting type links

Personal Booking Links

The owner of the link is the booker when a meeting is booked through a user's personal link

Default Booker: Instant Booker

You can use Instant Booker via Chili Piper's Chrome Extension to book meetings for yourself and others. There are two common use cases for Instant Booker:

1. An SDR or BDR booking on behalf of an AE
2. Booking meetings for yourself

When using Instant Booker, Chili Piper registers the logged in user of Instant Booker as the Booked By user

Set the Booker in Booking Links

You can pass a parameter in any Chili Piper link to specify a specific booker by using Smart Booking Links. You might choose to do this if a Router or Queue link are being used in a Sales Enablement cadence or a specific email campaign.

Example:

If we have this Round Robin URL: https://calendar.chilipiper.com/book/test and want to override the Default Booker to be a user, specifically Jeff Bezos, we can set this using a by parameter in the link: 

https://calendar.chilipiper.com/book/test?by=jeff-bezos

In enablement tools, you would use this same format with the dynamic merge fields for first name and last name.