Chili Piper
How Spara integrates with Chili Piper.
Last updated
How Spara integrates with Chili Piper.
Last updated
Spara's AI can intelligently push leads to schedule a call with your sales team.
For example, Spara may be tasked with ascertaining the number of employees at a lead's company. Once discovered, if the lead is at a company with >100 employees, Spara can prompt the lead to schedule a call. If the lead is at a company with <100 employees, Spara can instead prompt the leads towards a self-service sign up flow.
Spara can show a Chili Piper scheduler during as part of a conversation. This allows Spara to prequalify a lead before letting them schedule a meeting, or to determine which calendar link to use for each lead.
Provide your customer success representative with the a) domain, and b) router of your Chili Piper Concierge calendar widget. This will be embedded within Spara's interface. For example:
Domain: acme-corp, Router: sales-round-robin
You will also need to enable Chili Piper's JS API for inbound routing with Concierge. This enables Spara to load your Chili Piper concierge calendar as an embed. Make sure that "Third party form is Submitted" is selected as the trigger.
To redirect from a Chili Piper Concierge scheduled to Spara, you will need to set up Chili Piper to redirect to a URL containing form values in the redirect URL. This provides Spara with the information you lead just submitted to Chili Piper.
In the Redirect To settings, select "Enabled" for Include Form Values in Redirect URL - this ensures that Chili Piper includes lead data via query parameters for Spara to ingest. You can then map those query parameters inside the Spara Platform - see our Query Parameters guide for more information.
Provide your customer success representative with the full URL of your Chili Piper (Legacy) calendar widget. This will be embedded within Spara's interface. For example:
https://yourdomain.chilipiper.com/book/me/firstname-lastname
See Chili Piper's documentation for full instructions:
See Chili Piper’s documentation:
