--- title: "Smart Scheduling Links" source_url: https://help.chilipiper.com/hc/en-us/articles/32118298275603-Smart-Scheduling-Links article_id: 32118298275603 updated_at: 2026-07-01T20:08:27Z --- ## Who can use this feature? Available on All Products or Routing & Scheduling Available to Admins or Workspace Managers [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) You can embed smart parameters in your Chili Piper URLs for different use cases, such as automatically identifying a prospect or crediting a booker for a booked meeting. In this article, we will cover which parameters can be used and how they can help you. This article is dedicated to users who have upgraded and are working with our Demand Conversion Platform instance. * * * #### Table of Contents * Which Smart Parameters are Currently Available? * UTM-related Parameters * How do I embed a Smart Parameter in my URLs? * Smart Link Builder in App * Use Case Examples * * * ## Which Smart Parameters are Currently Available? Here's a list of dynamic fields you can add to your "base" calendar links with examples below: `id` | **email address** | Pass the prospect's email address as an ID if the prospect is in your CRM. ---|---|--- | **CRM ID** | Pass prospect CRM ID (both Lead & Contact objects work for Salesforce and only Contact for HubSpot) `by` | **firstname-last name (Unique Chili Piper link)** | The booker's full name (if they want to get notified and get credit) `assignee` | **User (Unique Chili Piper link)** | Specifies an assignee while using a scheduling link. If you have more than one distribution (multi-round robin), you can use assignee1, assignee2. For example, the Scheduling Link below would assign the meeting being booked to John Doe: `opportunityId` | **SFDC Opp ID** | The SFDC ID of the Opportunity that the meeting should be related to. This also determines which opportunity to route in rule execution (aka tiebreaking). `caseId` | **SFDC Case ID** | The SFDC ID of the Case that the meeting should be related to. This also determines which case to route in rule execution (aka tiebreaking). `objectId` | **SFDC Custom Obj ID** | The SFDC ID of a Custom Object that the meeting should be related to. This also determines on which custom object to route in rule execution (aka tiebreaking). `accountId` | **SFDC Account ID** | The SFDC ID of an Account. Creates a Contact under the Account passed to us. `campaignId & status` | **SFDC Campaign ID / Status** | The SFDC Campaign Id to be associated to the prospect and the campaign member status value. `meetingTypeId` | **Meeting Type ID** | Passes a specific meeting template (Meeting Type) to the meeting being booked, even if the Scheduling Link is associated with a different one. _Note: Anywhere that specifies the user's first-last name, we retrieve this from their user slug. Admins can find this or edit it in the User Table._ ![](https://help.chilipiper.com/hc/article_attachments/46219093756691) ### UTM-related Parameters In Chili Piper, there are default UTM Data fields that will be created automatically. If you are passing one of them, there is no need to create the UTM; you can just edit it. By default, you will find the UTM-related fields below for use. **How it works:** Original fields are first populated and not overwritten, and Recent fields are overwritten. You can choose among the following standard slugs for UTM-related Chili Piper Data Fields: `utm_content` | Original UTM Content Recent UTM Content ---|--- `utm_source` | Original UTM Source Recent UTM Source `utm_medium` | Original UTM Medium Recent UTM Medium `utm_term` | Original UTM Term Recent UTM Term `utm_campaign` | Original UTM Campaign Recent UTM Campaign [**Please check this article**](https://help.chilipiper.com/hc/en-us/articles/38267589273363-Passing-UTM-in-Scheduling-links-and-Concierge-Router-Links) for more details about the benefits of passing such parameters and more details about how to configure it. * * * ## How do I embed a Smart Parameter in my URLs? The parameter above can be added to a base calendar link preceded by `?`. If you add several parameters to a base link, you can separate them using `&`. If you add several parameters to a base link, here's one example of how a link would look like: `[Base_Calendar_Link]?id=prospect@email.com&by=mary-joe` The Base_Calendar_Link can be: * **Personal Links:** The user's Unique Chili Piper URL, which can also be associated with different Meeting Types. Admins can find end user's links in the Command Center ([click here to check how](https://help.chilipiper.com/hc/en-us/articles/29408315469459-End-User-Personal-Settings)), and end users can find their links either in their [Personal Settings](https://help.chilipiper.com/hc/en-us/articles/29408315469459-End-User-Personal-Settings), or [Meeting Types page](https://help.chilipiper.com/hc/en-us/articles/27994909516563-Meeting-Types-in-ChiliCal). * **Group, One-on-One, Ownership** and**Round-Robin Links:** These can be found under "Scheduling Links" in the left-hand side menu, under ChiliCal's section. [Click here for more details](https://help.chilipiper.com/hc/en-us/articles/29763780952467-Scheduling-links-in-ChiliCal). * **Concierge Router links:** Admins can find a Router link in the "Embed tab for each Concierge Router, specifically in the "In Emails" option. If needed, check [this article](https://help.chilipiper.com/hc/en-us/articles/29434325732755-Demand-Conversion-Platform-s-Concierge-Router-Deployment) for more details. * * * ## Smart Link Builder in App #### ChiliCal Scheduling Links When you are building out a Scheduling Link, you have the option to create a Smart Link directly in the editor. This will add the correct parameter for the tool you are using to send the scheduling link. Currently, the **id** parameter is available in this builder. For example, if you send an Ownership Scheduling Link through a Hubspot Email campaign, you can instantly get the correct link with the id parameter, allowing for one-click booking experience. ![](https://help.chilipiper.com/hc/article_attachments/40626960954131) #### Concierge Router Links The same builder is also available in Concierge Router Links. Instead of using a Scheduling link as a base, you can use a Concierge Router link, which may have more routing rules built out inside it. You can find this builder in your **Concierge Router > Embed tab > In Emails dropdown > Smart Router Link**. Currently, the **id** and **by** parameters are available. ![](https://help.chilipiper.com/hc/article_attachments/40626960955667) * * * ## Use Case Examples Here are some everyday use case examples where the smart parameters can help you achieve different goals. ### Automatically identify your prospect (id=) You may want to do this to [increase your conversion in email campaigns](http://www.chilipiper.com/meetings-booked-in-one-click-in-your-email-campaigns/) by using a CRM ID or a dynamic tag that includes your prospect/client’s email via `?id=` in your booking link structure: `[Base_Calendar_Link]?id=CRMID ` or `[Base_Calendar_LINK]?id=email_address` For **ChiliCal's Scheduling Links** , you also need to have the "Skip the Form when possible" setting enabled in the associated [**Meeting Type**](https://help.chilipiper.com/hc/en-us/articles/27994909516563-Meeting-Types-in-ChiliCal) so the form can be skipped appropriately when an ID is identified in your CRM: ![](https://help.chilipiper.com/hc/article_attachments/32422757414803) For **Concierge Router Scheduling Links** , the form will **not** be displayed by default, whether or not an email or CRM ID is found in your CRM. **Practical Examples:** In [Salesloft](http://www.chilipiper.com/book-more-meetings-with-salesloft-cadence/), the following link `https://Base_Calendar_Link/shared/john-doe/support-call?id={{email_address}}` will automatically become [`https://Base_Calendar_Link/shared/john-doe?id=prospect@email.com`](https://Base_Calendar_Link/shared/john-doe?id=prospect@email.com) In [Outreach](https://www.chilipiper.com/integrations/outreach), `https://Base_Calendar_Link/shared/mary-doe/demo-call?id={{email}}` will become `https://Base_Calendar_Link/shared/mary-doe/demo-call?id=prospect@email.com` These are also especially useful for allowing your prospects to book a meeting with one click from your signature. This can be done in [Outreach](https://help.chilipiper.com/hc/en-us/articles/360053022754), [Pardot](https://help.chilipiper.com/hc/en-us/articles/360053020574), [Marketo](https://help.chilipiper.com/hc/en-us/articles/360053800433), [Salesforce](https://help.chilipiper.com/hc/en-us/articles/360053798073), [Salesloft](https://help.chilipiper.com/hc/en-us/articles/360053023334), and any other tool that allows you to pass an email ID. * * * ### Automatically pass on the booker ID (by=) You would want to do this, for example, for reporting purposes, knowing who to give credit to a specific meeting, or ensuring the booker is also part of the meeting. You can add this parameter at the end of your link: **?by=firstname-lastname** , which will be the user's Chili Piper Unique URL. Here's one example `https://Base_Calendar_Link/shared/mary-doe/demo-call?by=john-doe` Within this example, we would book a meeting using Mary's link, crediting John as the meeting's booker. If you want to add the two parameters (by and id) together, you can separate them with `&`. For example: `[Base_Calendar_URL]?by=full-name&id=CRMID` If you are using a router link, you can benefit from our Concierge Router's Embed page to automatically build the link for your colleagues. [Click here to learn how](https://help.chilipiper.com/hc/en-us/articles/29434325732755-Demand-Conversion-Platform-s-Concierge-Router-Deployment#h_01HY0S51QQXEH9YJ8EKWNZX4PA). * * * ### Specify an Assignee (assignee=) for a Round-Robin Scheduling Link If you want to create a URL that only goes to a particular person in your [Round-Robin Scheduling Links](https://help.chilipiper.com/hc/en-us/articles/34959473865491-Round-Robin-Scheduling-Links), you can include it by adding their Chili Piper Unique URL to the Scheduling Link. You can add this parameter at the end of your link: **?assignee=firstname-lastname** , which will be the user's Chili Piper Unique URL. Note the assignee you are specifying in the URL needs to be part of the [Distribution](https://help.chilipiper.com/hc/en-us/articles/29260564275603-Workspace-Assets-Distributions) associated with the [Scheduling Link](https://help.chilipiper.com/hc/en-us/articles/34959473865491-Round-Robin-Scheduling-Links). For example, the Scheduling Link below would assign the meeting being booked to John Doe: * * * ### Automatically relate the booking to an SFDC opportunity (opportunityId=) You can do that by adding this parameter at the end of the booking link: **?opportunityId=** to associate the Salesforce Event to a specific Opportunity**.** Here's one example: `https://Base_Calendar_Link/shared/mary-doe/demo-call?opportunityId=0061U000004opKiQAI` With the example above, we would book a meeting using Mary's link and relate the meeting with the prospect to the opportunity ID: 0061U000004opKiQAI Let's look at another one: `https://Base_Calendar_Link/concierge-router/link/demopage-router?opportunityId=0061U000004opKiQAI` With this example above, we would book a meeting using a router link and relate the meeting with the prospect to the opportunity ID: 0061U000004opKiQAI Note that, while using Concierge Router links, if there is no Event Creation Node in your Concierge Router, we will not relate the Event with Opportunities. * * * ### Automatically relate the booking to an SFDC case (caseId=) You can add this parameter at the end of the booking link: **?caseId=** to associate the Salesforce Event to a specific Case. Here's one example: `https://Base_Calendar_Link/shared/mary-doe/demo-call?caseId=5000W00001DS2Pm` With the example above, we would book a meeting using Mary's link and relate the meeting with the prospect to the opportunity ID: `5000W00001DS2Pm` Let's look at another one: `https://Base_Calendar_Link/concierge-router/link/demopage-router?caseId=5000W00001DS2Pm` With this example above, we would book a meeting using a router link and relate the meeting with the prospect to the opportunity ID: `5000W00001DS2Pm` Note that, while using Concierge Router links, if there is no Event Creation Node in your Concierge Router, we will not relate the Event with Cases. * * * ### Force a Contact to be created under a certain Account Let's say, for example, that you are sending out a marketing email. You are worried that someone may forward the email with the booking link to a coworker who may not exist in Salesforce. Still, in this case, you want to ensure that the person who ends up booking gets created as a Contact in Salesforce under the Account the initial Contact you were emailing is a member of. You can use the`accountId` Smart Booking parameter to achieve this. For example, if you have an Account in Salesforce with ID = 001xxxxxxxxxxxx, you can set this value at the end of the booking URL to ensure that if a new Prospect fills out the form, Chili Piper will create a Contact under that Account. `https://Base_Calendar_Link/concierge-router/link/demopage-router?accountId=001xxxxxxxxxx` Edge Case Handlers to be aware of: * If no record exists (Lead or Contact) by email when the meeting is booked, then Chili Piper will create a Contact in SFDC under the Account that was passed to us * If a Lead or Contact Exists but the Contact is in another Account, we will create a net new Contact under the Account ID passed to us. (a purposeful duplicate) * If a single Contact already exists under that Account (by email), we will use that Contact and not create a new one. * If multiple Contacts exist with that email address, one of which is associated with the accountId in question, then we will use the Contact ID from the accountId value passed. * * * ### Automatically pass the Salesforce Campaign Id and the Campaign Member Status value You can now pass the Salesforce Campaign ID that you want your prospect to be associated with and the Campaign member status value like the example below: `https://Base_Calendar_Link/concierge-router/link/demopage-router?campaignId=7014x000001CWxt&status=Responded` * * * ### Automatically pass a Meeting Type to book a meeting You can also "force" a meeting template to be used in your booked meetings, even though you have a different one associated with the Scheduling path being used. Be careful, as all settings associated with the Meeting Type you intend to use will also be taken into consideration during the booking process. `https://Base_Calendar_Link//concierge-router/link/inbound?meetingTypeId=d35e9467-6160-4e0a-8047-ad4d9b560432` To get your Meeting Type ID to be used, navigate to the Meeting Types page under the Assets menu and open the Meeting Type you want to use. You will be able to find the Meeting Type ID in the browser's URL: ![](https://help.chilipiper.com/hc/article_attachments/37594081612307) * * * ### Pass UTM Values Passing UTMs in your Booking URL can be used to track the performance of your marketing campaigns. They help identify where traffic comes from, measure engagement and conversions, support A/B testing, track ROI, and ensure consistent data across platforms. **Practical Example for UTM Content:** https://yourdomain.chilipiper.com/concierge-router/link/router_name?utm_content=ebook **Practical example for UTM Source and UTM Content on the same link:** https://yourdomain.chilipiper.com/round-robin/link_name?utm_source=linkedin&utm_content=ebook