--- title: "Custom Salesforce Fields" source_url: https://help.chilipiper.com/hc/en-us/articles/34424043095443-Custom-Salesforce-Fields article_id: 34424043095443 updated_at: 2026-04-22T15:06:58Z --- ## Who can use this feature? Available on All Products or Routing & Scheduling Available to Only Admins [Billing Center](https://fire.chilipiper.com/fire/admin/billing/overview) [Get a Demo](https://www.chilipiper.com/request-demo?utm_source=zendesk&utm_medium=help-center&utm_campaign=chili-hub) 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 the number of meetings booked per day/month/week or for syncing to other systems, such as Marketo, Salesloft, Outreach, Pardot, Hubspot, etc. Before we start, please note: * If you have previously installed Salesforce Custom Fields from Legacy, most of them stay the same, so no action needs to be taken for those. That said, you will mainly need to create new ones only. _**![warning-icon.png](https://help.chilipiper.com/hc/article_attachments/42092099400467)**_**Warning** Please note that some fields might not be available on the new platform like the Designated_Assignee_CP field. * * * #### Table of Contents * Activity (Event) Object: 11 Available Fields * Lead / Contact Objects: 3 Available Fields (Meeting Type, No Show, Booking Status) * Distro Specific Fields * Troubleshooting Tips: Fields Aren't Updating **Important:** The Salesforce integration user cannot be restricted by [field-level security](https://developer.salesforce.com/docs/atlas.en-us.securityImplGuide.meta/securityImplGuide/admin_fls.htm) 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. * * * ## Activity (Event) Object Custom Fields 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:** The Meeting Type's name of the one used to book the meeting. * Field Name: `Meeting_Type_CP` * Field Type: Text (set the max length to 255) * Field Label: Meeting Type --- **No Show:** Used to track if the prospect didn’t show up (_true or false_). Maps against the [no show button](https://help.chilipiper.com/hc/en-us/articles/33508186571667-Managing-No-Shows-in-the-Demand-Conversion-Platform) * Field Name: `No_Show_CP` * Field Type: Checkbox (by default false) * Field Label: No Show --- **Canceled:** Tracks if a meeting was canceled (_true or false_). A meeting is considered canceled if the cancelation happened through a public cancel URL or if the meeting was deleted/canceled in your calendar provider * Field Name: `Canceled_CP` * Field Type: Check box (by default false) * Field Label: Canceled --- **Booked by Prospect:** Mark a meeting booked by a prospect from an online booking link or from your website. It will be checked if the prospect themselves booked via an online link. It is unchecked if one of your users booked the meeting via ChiliCal or Chat. * Field Name: `Booked_By_Prospect_CP` * Field Type: Checkbox (by default false) * Field Label: Booked by Prospect --- **Team Name:** If you are working in the **Demand Conversion Platform** and installed our Salesforce package first time, you will notice this field comes by default. If you previously installed our **Legacy** package, you may need to create this one manually if you would like to use it. 1. The**Team Name** if the meeting was booked via **Ownership** OR 2. The **Distribution** Name if the meeting was booked via **Round-Robin** OR 3. The **Individual Name** if the meeting was booked via Concierge for an Individual * Field Name: `Team_Name_CP` * Field Type: Text * Field Label: Team Name --- **Workspace Name:** Tracks the Workspace a Meeting was booked from based on the Meeting Type. The value will be the Workspace name, or if booked from a personal booking link, it will contain "Personal Workspace". * Field Name: `WorkspaceName_CP` * Field Type: Text * Field Label: Workspace Name --- **Router Name:** Tracks the name of the **Concierge** or **Handoff** router from which the meeting came. * Field Name: `Router_Name_CP` * Field Type: Text (255) * Field Label: Router Name --- **Booked By:** Track which user booked a meeting * Field Name: `Booked_By` * Field Type: Lookup * Lookup Object: User * Field Label: Booked By * Field not included in the [Salesforce Package](https://help.chilipiper.com/hc/en-us/articles/7170317352467-Concierge-Handoff-for-Salesforce-Package). --- **Booked By Name:** Tracks which user booked a meeting, but this one is a Text field * Field Name: `Booked_By_Name_CP` * Field Type: Text * Field Label: Booked By Name --- **Rescheduled:** Tracks how many times a meeting was rescheduled * Field Name: `Rescheduled_CP` * Field Type: Number, Default Value= 0 * Field Label: # Rescheduled --- **Rule Name:** Writes the name of the matched rule – applies to Concierge, Handoff, and soon to Chat. If you previously installed our **Legacy** package, the Rule Name value will be written to your usual **Queue Name** field (below), and you may need to create the Rule Name one manually if you would like to use it. * Field Name: `Rule_Name_CP` * Field Type: Text (length: 255) * Field Label: Rule Name **Queue Name:** For those who have already installed our **Legacy** Salesforce package in the past, it originally tracks the **Queue Name** a Meeting was Booked from **Legacy**. For **Demand Conversion Platform meetings** , it writes the **Rule Name** , with the same logic as explained above. * Field Name: `Queue_Name_CP` * Field Type: Text * Field Label: Queue --- **Booking Source:** The name of the booking source in Chili Piper that the meeting was booked. Possible values include ChiliCal, Chat, Concierge, and Handoff. * Field Name: `Booking_Source_CP` * Field Type: Text * Field Label: Booking Source CP --- **Response Status:** Track if an Event is Accepted, Declined, NotResponded, or Maybe/Tentative. Field Name: Response_Status_CP Field Type: Text Field Label: Response_Status_CP Values: Accepted, Declined, NotResponded, Maybe (Google specific), Tentative (MS O365 Specific) Note: You do not need to add the Values above in your setup. * * * ## Lead/Contact Objects Custom Fields The following fields can also be added to the lead/contact object. They are particularly helpful in starting or stopping specific email campaigns or for automated triggers in Salesforce. In Outreach, Pardot, and SalesLoft, you can start or stop a particular email campaign when a meeting is booked or a guest fails to attend. **Meeting Type:** The Meeting Type's name of the one used to book the meeting. * Field Name: `Meeting_Type_CP` * Field Type: Text * Field Label: Meeting Type --- **No Show:** Used to track if the prospect didn’t show up (_true or false_). Maps against the [no show button](https://help.chilipiper.com/hc/en-us/articles/33508186571667-Managing-No-Shows-in-the-Demand-Conversion-Platform) * Field Name: `No_Show_CP` * Field Type: Checkbox (by default false) * Field Label: No Show --- **Most Recent Booking Status:** The following field writes either "Booked" or "Not Booked" depending on whether a meeting is successfully booked or not. * Field Name: `Booking_Status_CP` * Field Type: Text (set the max length to 255) * Field Label: Booking Status _Note**:** This field would only be relevant when using a _[_Chat Journey Route for Meeting_](https://help.chilipiper.com/hc/en-us/articles/27532198601107-Creating-a-Journey-in-Chat#h_01HSXX3M394YQS2PGHD9WAMSSS) _or_[ _Concierge Router_](https://help.chilipiper.com/hc/en-us/articles/28522554434323-Creating-a-Router-in-Demand-Conversion-Platform-s-Concierge) _. The value "**Booked** " will be written when the meeting is booked. The value "**Not booked** " will be written based on the timeout defined on Not Scheduled-related paths within your Router and if a rep is assigned (distributed) but not if a prospect is disqualified. "**Disqualified** " otherwise. _ --- * * * ## Distro Specific Fields The fields below can be added to the **Lead** , **Contact** , **Account** , **Case** , and **Opportunity** objects. **Distro Assigned:** Tracks if a record was routed via Distro. * Field Name: `Distro_Assigned_CP` * Field Type: Checkbox (by default false) * Field Label: Distro_Assigned --- **Last Distro Route:** Tracks when a record was routed via Distro. * Field Name: `Last_Distro_Route_CP` * Field Type: Date/Time * Field Label: Last_Distro_Route --- The field below is specific to the **Contact** object. **Distro Converted:** Tracks if a Lead was converted to a Contact; field automatically gets checked whenever Distro converts a Lead to a Contact for Reporting, Auditing, and Debugging purposes. * Field Name: `Distro_Converted_CP` * Field Type: Checkbox (by default false) * Field Label: Distro Converted --- * * * ## Troubleshooting Tips: Fields Aren't Updating * Ensure required users have Read/Edit permissions on the new fields. * Ensure no other validation or rule issues exist for Lead/Contact/Event creation. If Chili Piper has difficulty updating a Lead, we may fall back to not updating custom fields to ensure the Lead is still created. * Ensure 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.