Default Booker's Role

Hey, Chili users! 

Ensuring that your Chili Piper queues have a properly user set as the Default Booker is one of the key points to have a functional queue. Let's talk a little a bit about this role and why it's important! Also, we're curious to know if you have any best practices about this configuration inside your company! 😄

The Default Booker is a setting that should be set in your Chili Piper queues and it's located inside the Online Booking URL section:


Inside Chili Piper the internal person scheduling a meeting is called the "Booker". Whenever a meeting is created, Chili Piper will attempt to use the credentials of the Booker to create a Salesforce Event (or an Engagement in HubSpot) when the meeting is created through Instant Booker. If the Booker is not connected to Salesforce/HubSpot or this user doesn't have the permissions to create an Event/Engagement, Chili Piper will fall back to the "Default Booker" permissions to get the Event created. This also applies to meetings created directly through the queue link or a Router. If the assignee selected doesn't have a calendar connection, we will fall back to the Default Booker's connection to create the calendar Event. 

This is why it is important to guarantee that the Default Booker set in your queues has a valid CRM and Calendar connection. You can learn a little bit more about this role here!

By default, the Default Booker user will receive a notification about every meeting being created within the queue, and for this reason, some companies adopted as a good practice to use one specific user as the default booker of all queues.

We are curious to know if you have any different best practices followed by your company or any tips about the users set for this role! 😊