Smart Booking Links

Here's a list of dynamic fields you can add to your "base" calendar links with examples below:

Example: https://mycompany.chilipiper.com/book/me/my-name?id=collin@hotaccount.com

The parameter above can be added to a base calendar link preceded by ?. If you add several parameters to a base link, your links will look like this:

[Base_Calendar_LINK]?id=prospect@email.com&type=demo&by=mary-joe

Note: If you are using these smart booking links in an email or marketing campaign and your marketing app supports "URL-encoding", please consider using this feature to ensure special characters are supported. For example, an email address with a "+" sign may introduce issues if it is not formatted correctly. For more information on this, please refer to your marketing app documentation.

The Base_Calendar_LINK can be: 

a. An individual calendar link. Find your calendar link from your Booking Links page in Chili Piper. The individual booking links for your team are under the Active Users screen.

b . Queue calendar links. You can find them within your queue's "Online Booking URL" section

c.  Inbound router URLs under the "embed for your form" section

Once you have identified your calendar “Base” link, you have many options to enhance this in your campaigns.

Use cases - examples 

1. Automatically identify your prospect

You want to do this to increase your conversion in email campaigns. 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=ID or [Base_Calendar_LINK]?id=email_address

Examples: 

Team booking links:

https://calendar.chilipiper.com/book/inbound-meetings?id={{email_address}} in Salesloft will automatically become

https://calendar.chilipiper.com/book/inbound-meetings?id=prospect@email.com

https://calendar.chilipiper.com/book/inbound-meetings?id={{email}} in Outreach will  become

https://calendar.chilipiper.com/book/inbound-meetings?id=prospect@email.com

For individual links is especially useful to allow your prospects to book a meeting with one click from your signature. It can be done in   Outreach, Pardot, Marketo, Salesforce, Salesloft, Intercom, and any other tool that allows you to pass an email ID.

2. Automatically pass on the booker ID

You’d want to do this for reporting purposes (to know who to give credit to) or make sure the booker is also part of the meeting.

You can do that by adding this parameter at the end of your link: ?by=full-name:

[Base_Calendar_link]?by=full-name

If you want to add two parameters together, you need to replace one ? with a “&”

[Base_Calendar_URL]?by=full-name&id=CRMID

Example:

https://calendar.chilipiper.com/book/outbound-meetings?by=alina-vandenberghe will log the meeting as booked by Alina Vandenberghe

3. Automatically pass the assignee calendar via a “team” booking URL

If you want to create a URL that only goes to a particular person in your queues, you can include it by adding their full name in the booking link.

[Base_Calendar_URL]/full-name

Example:

https://calendar.chilipiper.com/book/outbound-meetings/alina-vandenberghe would book a meeting with the prospect on Alina’s calendar

4. Specify the meeting template

To associate a different meeting template than the default one to a link, you can do so via ?type=meeting-name

[Base_Calendar_LINK]?type=meeting-name

Example:

https://calendar.chilipiper.com/book/outbound-meetings?type=demo would book a meeting of type demo as set up in our admin interface

5. Default to the calendar of the account owner if there is one in Salesforce

If you create a queue that is of type “Ownership” by selecting this algorithm:

And then add the correct rules for ownership. E.g.:

Then you can use this calendar URL to route your prospect to the correct owner by adding their email address or CRM ID via the ?id= tag described at the first point above

6. Automatically route your prospect to the correct resource

If you create a router, you can use that router URL to route the resource to the correct calendar based on all the rules you have set up in your queues.

You can have a few options in this case:

a. Automatically identify a prospect by passing the CRM ID or email ID. E.g

https://calendar.chilipiper.com/router/inbound-router?id=prospectID https://calendar.chilipiper.com/router/inbound-router?id=prospect@email.com

OR

b. Ask the prospect a few questions before you route them to the correct resource

Use the router URL, and make sure the form questions match your queue rules.

https://calendar.chilipiper.com/router/inbound-router

If you are looking to pre-fill your prospect's info into your web form, you can learn how to do this via Query string parameters for more information.

See our REST API documentation for additional URL Parameters, typically for use with our REST API.

7. Force a Contact to be created under a certain Account

Let's say, for example, that you're sending out a marketing email. You're 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 that you, 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://calendar.chilipiper.com/book/queue-name?accountId=001xxxxxxxxxxxx

This parameter works with:

• Personal Booking URLs
• Queue URLs
• Router URLs
• Chili Piper's marketing.js Concierge Javascript

Edge Case Handlers to be aware of:

a) 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

b) If a i.Lead or ii.Contact Exists, but the Contact is in another Account, create a net new Contact under the Account ID passed to us. (a purposeful duplicate)

c) If a single Contact already exists under that Account (by email), use that Contact and don’t create a new one.

d) If multiple Contacts exist with that email address, one of which is associated with the AccountId in question, then use the Contact ID from the accountId value passed