If added to your HubSpot CRM instance, Chili Piper will write a handful of custom properties to allow you to track and report on all your booking data directly in HubSpot CRM. You can use this data to filter Contacts, syncing to other systems, or custom reporting.
With Super Admin permissions, we will automatically create these custom properties for you, grouped under Engagement Information on the Contact object upon connecting the HubSpot CRM integration.
Installation
If these properties were not created automatically, you could create them manually under the Contact as new "single-line text" fields. The field names are detailed below.
In Chili Piper, remember to "refresh fields" after this is done:
Contact Properties
The following properties are beneficial in starting/stopping email campaigns or automation and reporting. For example, you can often leverage these fields in marketing automation software to start/stop email campaigns when a specific meeting is booked or when a guest fails to show up for a meeting.
Meeting Type (as setup under your workspace Meeting Type List)
|
Router Name as defined by the name of the inbound concierge router used to book the meeting.
|
Prospect didn’t show up. Maps against no show button. True / False
|
Track if a meeting was canceled*
|
The following field writes either "Booked" or "Not Booked" depending on whether a meeting is successfully booked.
Note: This field would only be relevant when using "Concierge || Inbound Router". The value "Booked" will be written when the meeting is booked. The value "Not booked" will be written based on the timeout defined in Queues for prospects who didn't take action within your Router and if a rep is assigned (distributed) but not if a prospect is disqualified. "Disqualified" otherwise.
*You must have at least one queue in the "Queues for prospects who didn't take action" section of your router for the "Not booked" value to write to HubSpot CRM. If you have another system using this field to route and do not want to have Chili Piper distribute those leads who do not book, you can add a "dummy" queue into this section, with rules that will "never match". ie RelatedContact.Email = 123. |
Track the Response of an SMS Message - only used if using Twilio SMS Integration*
|
Track if a meeting is confirmed via SMS - only used if using Twilio SMS Integration*
|
The following field writes the date that the most recent meeting was created for this Contact.
|
They will appear similar to this within the Contact's properties:
Meeting Type & Outcome
Chili Piper now writes to the “Meeting Type” and "Outcome" properties on Meetings created by Chili Piper in HubSpot!
Meeting Type
The name of the associated Meeting Type in Chili Piper will now appear on newly created Engagements. This Meeting Type will match the "Meeting_Type_CP__c" property.
Outcome
When a meeting is marked as a "no show", canceled, or rescheduled, we will update the Engagement accordingly:
"SCHEDULED"
- This is the default behavior of HubSpot - when a meeting is created in the HubSpot UI it shows as “Scheduled”
"RESCHEDULED"
-
If the CRM Action to delete the meeting in HubSpot is OFF then mark the Engagement as
"CANCELED"
- If the CRM action to delete the meeting in HubSpot is ON then we delete the Engagement in HS so no need to mark it as “Canceled":