Booker is now able to view an Assignee’s Calendar Free/Busy Slots via Handoff* when the Assignee’s Calendar is not connected. Supported for both Google Calendar and O365 Calendar Integrations 

Where to find the Global Calendar Connection: 
Admin Center → Integrations →  Calendar 

Example in Context:
An SDR is booking a Meeting for an AE via Handoff, but the AE’s Calendar is disconnected from Chili Piper or has not logged in to connect Calendar.

Before:

• The SDR would not be able to view the AE’s available times properly, often viewing a blank calendar view, which could result in a double booking.

After Update:

• The SDR is able to view the up-to-date times where the AE is available.

• When the meeting is booked, Chili Piper will use the SDR’s Calendar to create the meeting and invite the AE and the Guest. 

  • Handoff Scheduler view will also denote this if the settings are set to create the meeting in the “Assignee’s Calendar”.

Applicable to:

• Viewing the Assignee’s Calendar in Handoff Scheduler for Instant Booking, Suggested Times, & Inserting Links via Chrome Extension.

• When you add an internal additional guest to the Invite who has not connected their calendar, both in Handoff and ChiliCal view.

What it does not do:

• It is not applicable to Concierge and doesn’t serve as a “Fallback User”

• It is not applicable to ChiliCal when using “My Team’s Link”.

• We will not create the meeting using the Global Calendar Connection, only view.

  • Note: This uses sharing permissions, meaning the connected user must be able to view their co-workers' time slots within the actual calendar system for it to work with Chili Piper.
    
     

🚀 Person to Lead/Contact Matching – Compare Fields on the Incoming Person

Filters and tiebreakers in person to lead/contact matching can now compare fields on the incoming person record – bringing it up to parity with lead/person to account matching.

Background:

Until now, filters and tiebreakers could only look at fields on the existing record. So you could say "lead status must equal qualified" – but you couldn't compare a field from the incoming person to a field on the existing lead or contact.

How it works:
In the Matching Hub, filters and tiebreakers now support comparisons like:

• Lead Company is equal to Person Company Name

• Contact Support ID is equal to Person Support ID

Why:

• Personal email addresses: If someone submits a form using mary@gmail.com, you can't be certain they still represent the same company. By comparing the company name on the form to the company name on the existing lead, you can confirm it's the same Mary before matching.

• Support ID verification: A customer wanted to ensure that when someone submits a support form, they provide a Support ID that matches the existing contact. If it matches, treat them as the same contact. If not, create a new record for a different use case.

🚀 HubSpot Contact to Company Matching – Additional Domains Fallback

HubSpot customers can now match incoming contacts to companies using additional domains, not just the primary domain.

Background:

Until now, when matching an incoming contact to a company in HubSpot, we only checked the company's primary domain. This meant contacts coming from an additional domain – even one listed on the company record wouldn't match.

How it works:
When a new contact comes in (via Concierge, Chat, or a ChiliCal link), we check for company matches in two ways:

• Look for existing contacts with the same domain and extension

• Match to a company's primary domain – or fall back to additional domains if no primary match

If we match to multiple companies:

• We pick the one with the most contacts

• If still tied, we pick the most recently updated