Once you have added these fields to your Salesforce instance, Chili Piper will dynamically write a handful of custom fields to allow you to track and report on all your booking data directly in Salesforce. You can use this data to make Dashboards on a number of meetings booked per day/month/week or for syncing to other systems, such as Marketo, Salesloft, Outreach, Pardot, Hubspot, etc.
- Activity (Event) Object: 11 Available Fields
- Lead / Contact Objects: 3 Available Fields (Meeting Type, No Show, Booking Status)
- [Distro] Add Fields to the Lead/Contact/Account/Case/Opp
- Refresh your Salesforce fields
- Troubleshooting: Fields Aren't Updating
Important: The Salesforce integration user cannot be restricted by field-level security access to the fields within the above objects or any other limiting field permissions. Ensure this user has full read/write permissions for these fields and objects.
Add new fields on the Activity object
The following fields allow you to track advanced data for your Activity Reports. You can add them all as Activity Object Custom Fields, which can be added to the Event object layout. While field names are important (copy-paste the values from below), for field labels, you can use any text you'd like.
|
Meeting Type (as setup under your workspace Meeting Types List)
|
|
Prospect didn’t show up. Maps against no show button
|
|
Track if a meeting was canceled*
|
|
Mark a meeting booked by a prospect from an online booking link or from your website. It will be checked if booked by the prospect themselves via an online link. It is unchecked if the meeting is booked via the Instant Booker by one of your users.
|
|
Track the Queue a Meeting was Booked from
|
|
Track the Workspace a Meeting was Booked from based on the Meeting Type. Value will be the Workspace name, or if booked from a personal booking link, "<full name> personal workspace".
|
|
Writes the value of the user within the queue who was Next Up within the Queue if a Round Robin. When the current assignee was Next Up, this field will not be populated.
|
|
Track the Router a Meeting was Booked from. This value only writes when a meeting is booked via Concierge "Inbound Router". Otherwise, the value will be null.
|
|
Track which user booked a meeting
|
|
Track how many times a meeting was rescheduled
|
|
Track if an Event is Accepted, Declined, NotResponded, or Maybe/Tentative.
Values: Accepted, Declined, NotResponded, Maybe (Google specific), Tentative (MS O365 Specific) Note: You do not need to add the Values above in your setup. |
|
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*
|
|
Track that an Event was booked via a Meeting Series - Optional for Meeting Series Use-Case*
|
Add fields on lead and or contact
The following fields can also be added to the lead/contact object. They are particularly helpful in starting or stopping certain email campaigns. Or for automated triggers in Salesforce. In Outreach, Pardot, and Salesloft, you can start or stop a certain email campaign when a specific meeting is booked or when a guest fails to show up for a meeting.
|
Meeting Type (as setup under Meeting Types - Templates)
|
|
Prospect didn’t show up. Maps against no show button
|
|
The following field writes either "Booked" or "Not Booked" depending on whether a meeting is successfully booked or not.
Notes: This field would only be relevant when using "Concierge || Inbound Router". The value "Booked" will be written when the meeting is booked / event created in Salesforce. The value "Not Booked" will be written based on the timeout (7 min, 10 min, etc.) defined in Queues for prospects who didn't take action within your Router. |
[Distro] Add Fields to the Lead/Contact/Account/Case/Opp
|
Track that a record was routed via Distro
|
|
Track when a record was routed via Distro
|
Refresh your Salesforce fields
On your admin-level Integrations page, make sure you click “Refresh Fields”:
That's it!
Troubleshooting: Fields Aren't Updating
- Be sure to refresh the salesforce fields per the info above. This is required for any new field added to Salesforce, including these custom ones.
- Ensure all users have Read/Edit permissions on the new fields.
- Ensure there are no other validation or rule issues for Lead/Contact/Event creation. If Chili Piper has difficulty updating a Lead, we may fallback to not updating custom fields to ensure the Lead is still created.
- Make sure the fields are set up as defined above. For example, if you make a field a "restricted picklist" where it should be text, and the value provided by Chili Piper doesn't match, this can prevent the field from updating.