Chili Piper

Overview

Chili Piper is a B2B revenue acceleration platform that enables instant meeting scheduling directly from web forms, marketing landing pages, and inbound lead flows. Revenue operations teams deploy it to route qualified leads to the correct sales representative in real time, dramatically reducing time-to-meeting. Its JavaScript fires on form submission to qualify, route, and immediately book leads without requiring a separate scheduling step.

What This Script Does

Concierge Routing Script

The primary Chili Piper script (js.chilipiper.com/concierge.js) hooks into web form submissions on the host page. When a form is submitted, it intercepts the data, runs qualification logic against configured routing rules, and presents a calendar booking interface within a modal overlay — all before the form's native redirect fires.

Distro (Form Routing) Component

The Distro component handles intelligent lead distribution. It evaluates submitted form data (company size, job title, industry) against a predefined routing tree and assigns the lead to a specific sales rep's calendar. Assignment considers rep availability, territory rules, account ownership, and round-robin queues.

Cookies Set

• chilipiper_session — First-party session cookie. Stores the session context for the currently active routing flow. Duration: session.
• cp_visitor_id — First-party persistent cookie. Stores an anonymous visitor ID used for attribution and session stitching across visits. Duration: 6 months.
• cp_utm_data — First-party persistent cookie. Preserves UTM campaign attribution parameters from the visitor's original landing session. Duration: 30 days.

Domains Contacted

• js.chilipiper.com — Serves the Concierge and Distro JavaScript libraries.
• api.chilipiper.com — REST API for routing rule evaluation, availability lookup, and meeting booking.
• app.chilipiper.com — Hosts the calendar iframe rendered inside the booking modal.
• hooks.zapier.com / CRM webhooks — Chili Piper sends meeting booked events to connected CRM systems (Salesforce, HubSpot) immediately after booking.

Data Collected Per Interaction

• Form field values submitted (name, email, company, phone, job title)
• UTM source, medium, campaign, and content from URL parameters
• IP address for geolocation (used in territory routing)
• Browser user-agent and screen resolution
• Routing rule matched and rep assigned
• Meeting date, time, and duration selected
• CRM record IDs when CRM integration is active

Consent & Compliance

GDPR / ePrivacy: Chili Piper's script captures form data and routes it to sales representatives and CRM systems. The primary purpose is facilitating a meeting requested by the user, which can be justified under GDPR Article 6(1)(b) (steps taken at the request of the data subject prior to entering into a contract) or Article 6(1)(a) (consent via form submission). The session and attribution cookies require ePrivacy consent if they persist beyond the immediate interaction. UTM-preservation cookies are marketing-purpose and require consent.

CCPA / CPRA: Chili Piper processes personal information submitted via forms. When integrated with Salesforce or HubSpot, it shares that data with CRM platforms. Merchants should disclose Chili Piper as a service provider in their privacy notice.

EU-US Data Privacy Framework: Chili Piper is a US-based company. Organizations processing EU resident data with Chili Piper should confirm Standard Contractual Clauses are in place via Chili Piper's DPA.

Consent Category: Functional / Marketing (mixed). The booking and routing functionality is functional; the UTM cookie and visitor ID for attribution are marketing-purpose.

Should You Block This Without Consent?

Conditional. The meeting booking and lead routing components serve a functional purpose triggered by explicit user action (form submission). These may load without consent. However, the persistent visitor ID cookie (cp_visitor_id) and UTM attribution cookie (cp_utm_data) are marketing-purpose tracking elements that require prior consent under ePrivacy. A consent-aware implementation loads the form routing immediately but defers the attribution cookie writes until marketing consent is granted.