Salesforce · Chili Piper · Lead Routing

Chili Piper Salesforce Integration: Setup, Routing and Reporting Guide

Chili Piper qualifies, routes and books the meeting. Salesforce decides who owns the buyer and keeps the record. The integration is where the two meet. Here is how it works in 2026: which products connect, what the connecting user needs, what gets written to Salesforce, how routing uses your data, and how to report meetings through to pipeline.

Key Takeaways

  • The Chili Piper Salesforce integration reads Salesforce to decide who should meet a buyer, then writes the result back: it creates or updates the Lead or Contact, logs the meeting as a Salesforce Event and can update ownership, fields and campaigns.
  • A Salesforce admin connects it through OAuth from Chili Piper's Command Center. Since September 2025, Salesforce also needs the Chili Piper connected app installed, or the connection fails.
  • Chili Piper's Salesforce field package adds the custom fields, 11 reports and a dashboard that make meetings, no-shows and reschedules reportable.
  • Routing quality depends on Salesforce data: clean ownership, lead-to-account matching and a catch-all path for everything the rules miss.
  • Most problems are duplicate records or Events, unmapped users, and validation rules or restricted picklists that block Chili Piper's writes.

What is the Chili Piper Salesforce integration? It is Chili Piper's built-in connection to Salesforce. When a buyer submits a form, books from a link or is handed off by an SDR, Chili Piper looks the person up in Salesforce, applies your routing rules, shows the right rep's calendar and books the meeting. It then writes the outcome back to Salesforce as a Lead or Contact update and an Event with Chili Piper fields, so every booked meeting is visible and reportable in your CRM.

We first published this post in 2024. This version is rebuilt from Chili Piper's current help center and product pages and from Salesforce's documentation, checked in November 2026. Chili Piper has renamed several products since then, and Salesforce has changed how connected apps are approved, so the setup steps have changed too. It is written for sales operations, RevOps and Salesforce admins at growing and mid-market companies that run inbound or SDR-to-AE meetings through Salesforce, and for the revenue leaders who need to trust the numbers.

Section 01 · Short Answer

What Does the Chili Piper Salesforce Integration Actually Do?

It turns a form fill or a booking link into a routed, booked and logged meeting, using Salesforce as the source of truth for who owns the buyer. Chili Piper checks Salesforce within seconds of a form submission, routes the buyer to the account owner or a fair round robin, and books the meeting. Then it writes the record, the Event and the routing details back to Salesforce.

Chili Piper product graphic showing a Salesforce contact card, a weekly calendar of booked meetings, and icons for the Gmail, Outlook, Outreach and Salesloft integrations
Chili Piper books meetings from the tools reps already use and records them against the Salesforce contact. Product graphic from 2022: current screens look different.

Route

Rules check Salesforce ownership, lead-to-account matches and field values, then send the buyer to the owner, a team round robin or a specific rep.

Book

The buyer sees the assigned rep's live calendar from Google or Outlook and books at once, with email or SMS reminders before the meeting.

Write back

Chili Piper creates or updates the Lead or Contact, logs a Salesforce Event with meeting fields, and can update the owner, other fields and campaign status.

Section 02 · Products

Which Chili Piper Products Connect to Salesforce?

All of them share one Salesforce connection, but each one uses it differently. Form Concierge routes and books inbound buyers. Distro routes Salesforce records with no meeting attached. Handoff lets SDRs book for account executives. ChiliCal is the rep's own scheduler. Orchestrator follows up when a buyer drops off. Pick the products by the job, not by the feature list.

ProductWhat it does with SalesforceTypical owner
Form ConciergeQualifies a form, in-app or link submission, routes it on Salesforce ownership or field values, shows a calendar and writes the Lead or Contact and the EventMarketing ops and RevOps
DistroRoutes any standard or custom Salesforce object when a record is created or a field changes, with lead-to-account matching, SLAs and record round robinSales ops and Salesforce admin
HandoffRoutes a prospect an SDR has selected to the right AE and books the meeting, including live handoff to a rep who is free nowSDR and AE leaders
ChiliCalReps' scheduling links (one-on-one, round robin, group and ownership-based) and a browser extension that works inside Salesforce, Gmail and OutlookEvery rep
OrchestratorActs on Chili Piper events such as Meeting Booked or Meeting Not Scheduled and can write to Salesforce, for example to create Contacts directlyRevOps

Product scope comes from Chili Piper's Form Concierge, Distro and Handoff pages and its ChiliCal glossary.

Names that changed since 2024

Chili Piper's help center calls the current platform the Demand Conversion Platform and labels older setups Legacy. Three changes matter if you are reading older guides, including the first version of this post:

  • Instant Booker is now ChiliCal. Booking from inside Salesforce, Gmail or a sales engagement tool is done with the ChiliCal scheduler and extension. The old Instant Booker help articles have been removed.
  • Queues are now Rules. The rule that matched a booking is written to Salesforce where the queue name used to go.
  • Concierge is marketed as Form Concierge, and Chili Piper now describes itself as an agentic marketing platform, with chat, spam checking and meeting-prep agents around the same routing core.
Section 03 · Data Flow

How Does a Chili Piper Booking Flow from Form to Salesforce?

In five steps: look up, route, show a calendar, book, write back. Chili Piper checks Salesforce for an existing Lead or Contact within seconds of the submission. Known buyers go to their owner. New buyers go through your other rules to a team or rep. After the booking, Chili Piper creates or updates the record and logs the Event.

1. Look up the buyer in Salesforce.
→ On form submission, Chili Piper searches Salesforce for an existing Lead or Contact, and matches leads to accounts if lead-to-account matching is on.
2. Apply ownership rules first.
→ If a team member already owns the Lead, Contact or Account, the buyer is routed to that owner.
3. Route everyone else on their data.
→ Net-new buyers, or records you choose to redistribute, go through rules on Salesforce values and form answers, ending in a catch-all path.
4. Show the calendar and book.
→ The buyer picks a time from the owner, the team round robin or a named rep; the invite goes to the buyer and the rep straight away.
5. Write back to Salesforce.
→ Chili Piper (or your existing lead process, depending on the router settings) creates or updates the record, then logs the Event and any field, owner or campaign updates.

The sequence follows Chili Piper's data flow article. One timing detail matters for reporting: if Salesforce rejects the Event, Chili Piper retries automatically, starting a few minutes after the booking and continuing for about two days. A meeting can therefore appear in the rep's calendar before it appears in Salesforce.

Section 04 · Prerequisites

What Permissions Does Chili Piper Need in Salesforce?

A dedicated integration user with API access, user and role visibility, and read and edit rights on the objects you route. It also needs Create on Leads and Contacts if Chili Piper creates them, rights to manage Events, and full access to the Chili Piper fields. A Salesforce admin makes the first connection through OAuth from the Integrations page in Chili Piper's Command Center.

AreaMinimum accessWhen
System permissionsAPI Enabled; View Setup and Configuration; View Roles and Role Hierarchy; View All UsersAlways
LeadsRead, Edit, View All, plus Create if Chili Piper creates LeadsAlways (read is needed for lookups even if you don't use Leads)
Contacts and AccountsContacts: Read, Edit, View All, Create if used. Accounts: Read, Edit, View AllAlways
EventsView All and Modify All on the related objects (recommended), or Modify All DataAlways
Opportunities, Cases, CampaignsRead on Opportunities and Cases; Read, Edit, View All on CampaignsIf used
DistroPushTopic Create, Read, Edit, and Streaming API enabled in SetupDistro only
Chili Piper fieldsFull read and write, never restricted by field-level securityAlways

The list comes from Chili Piper's Salesforce integration configuration guide. Build it as a permission set rather than a cloned admin profile: our guide to Salesforce profiles and permission sets explains how.

Three details that catch teams out

  • The connected app must be approved. Since early September 2025, Salesforce restricts uninstalled connected apps. Before connecting, an admin installs the Chili Piper connected app under Setup › Connected Apps OAuth Usage. The alternative is to give the integration user the Approve Uninstalled Connected Apps permission. Without one or the other, the OAuth login fails with an approval error.
  • The API-only licence comes second. Chili Piper connects only through a browser login, so a user on Salesforce's Integration User licence cannot make the first connection. Connect with a standard licence, then move the user to the API-only licence and re-grant every permission through permission sets. Chili Piper advises testing that switch in a sandbox.
  • Users map by email. Each rep's Chili Piper login email is matched to the identical email in Salesforce. A rep whose emails differ stays unmapped and cannot own routed records or meetings.

Chili Piper's documentation does not list which Salesforce editions it supports. The stated requirement is a user with API Enabled, so confirm API access in your edition with Chili Piper before you buy.

Section 05 · Setup

How Do You Set Up the Chili Piper Salesforce Integration?

Prepare Salesforce, install the field package in a sandbox, connect the sandbox, build and test the routers, then repeat the connection in production. The connection itself takes minutes. The time goes into the routing design and testing. Working in a sandbox first keeps test meetings, Leads and Events out of production reports.

  1. 1

    Create the integration user and permission set from Section 04, and install the Chili Piper connected app in Salesforce.

  2. 2

    Request and install the Salesforce field package in your sandbox, for all users. Chili Piper sends the install link after you request access in its package article. Distro has its own package. The install fails if any Chili Piper field already exists, so check for fields someone created by hand.

  3. 3

    Finish the Salesforce side: give the integration user read and write on the new fields, add the fields and buttons to the Event, Lead and Contact layouts, and map the Lead fields to Contact fields so the values survive lead conversion.

  4. 4

    Connect the sandbox. Ask Chili Piper for a sandbox tenant, open its integrations page with ?isSandbox=true at the end of the URL, then click Connect to CRM so the login goes to test.salesforce.com. Without the parameter, the connection defaults to production.

  5. 5

    Connect calendars and map users. Each rep connects Google or Outlook, plus up to six extra read-only calendars for busy time. Check that every rep is mapped to a Salesforce user.

  6. 6

    Build teams, rules, distributions and routers, then test every path with real-looking data: known owner, matched account, new lead per territory, disqualified domain and catch-all.

  7. 7

    Go live in production: install the package, connect without the sandbox parameter, rebuild or move the routers, and watch the logs daily for the first week.

Section 06 · Data Written

What Does Chili Piper Write to Salesforce?

A Lead or Contact, a standard Salesforce Event and a set of custom fields. Chili Piper creates a Lead by default when the buyer is new, or a Contact when an account already matches, and updates the existing record rather than duplicating it. Meetings are standard Events, not a separate meeting object, so they work in normal activity reports.

WhereFields (API names end in __c)What they tell you
EventMeeting_Type_CP, Booking_Source_CP, Booked_By_Name_CP, Booked_By_Prospect_CPWhat kind of meeting, which product booked it (Concierge, Handoff, ChiliCal, Chat), who booked, and whether the buyer self-booked
EventRouter_Name_CP, Rule_Name_CP, Team_Name_CP, WorkspaceName_CPWhich router, rule and team produced the meeting, which is how you audit routing
EventNo_Show_CP, Canceled_CP, Rescheduled_CPOutcomes: no-show and cancellation flags, and a count of reschedules
Lead and ContactMeeting_Type_CP, No_Show_CP, Booking_Status_CPWhether a form submission ended Booked or Not Booked, useful to start or stop a sales sequence
Lead, Contact, Account, Opportunity, CaseDistro_Assigned_CP, Last_Distro_Route_CPWhether Distro assigned the record, and when it last routed it

Field lists come from Chili Piper's package articles and its custom Salesforce fields reference. You can also create the fields by hand instead of installing the package. Beyond the fields, router actions can do four more things:

  • Relate the Event to the Account, the most recently created open Case, the Opportunity with the nearest close date on the buyer's account, or a Campaign. By default it relates to the Lead or Contact.
  • Update fields on the Lead, Contact, Account, Opportunity or Case, on the Scheduled, Not Scheduled or Disqualified path.
  • Update ownership so the record owner becomes the rep who got the meeting.
  • Add to a campaign with a chosen Campaign Member Status, for marketing attribution.
Section 07 · Routing

How Does Chili Piper Route Leads Using Salesforce Data?

Through rules of two kinds, evaluated in order: CRM ownership rules and rules without ownership. Ownership rules send a buyer to the rep who owns the Lead, Contact or matched Account. The other rules route on Salesforce field values and form answers to a team round robin, an assignment table or a named rep. Every router ends with a catch-all path.

SettingOptionsUse it when
Meeting round robinStrict: shows the rep with the fewest meetings. Flexible: shows combined availability and picks the least-booked free repStrict for fairness; Flexible for more time slots and faster bookings
Record round robin (Distro)Strict, or Working Hours, which favours reps currently workingWorking Hours when speed to first touch matters across time zones
CalibrationWeights, credit and skip, capping with a fallback owner, and crediting reps back for no-showsRamping reps, part-time reps or uneven territories
Assignment tablesOne routing path that looks up the owner by territory or segmentMany territories that would otherwise need many paths
Matching (Distro)Lead-to-account, duplicate and custom matching, plus Opportunity and Case ownersAccount-based teams where a new lead belongs to an existing account owner

Options come from Chili Piper's distributions, Concierge flow and Distro router articles. Two behaviours are worth knowing before go-live. A buyer who matches an owner without a Chili Piper licence cannot book and lands in Not Scheduled. Round robins skip unlicensed users.

Chili Piper or Salesforce lead assignment rules?

Salesforce's own lead assignment rules are free and run on manual, Web-to-Lead and import-wizard leads. Entries are checked in order, the first match wins and only one lead rule can be active. They assign an owner or queue but do not book a meeting, balance workload by meetings held, or check calendars. Many orgs keep a simple Salesforce rule as a safety net and let Chili Piper own inbound meeting routing. Decide which system owns lead assignment, though: if both set the owner, they will overwrite each other.

Distro also keeps a routing log of every decision. Our guide to reading and fixing Chili Piper Distro logs walks through each status and error.

Section 08 · Reporting

How Do You Report on Chili Piper Meetings in Salesforce?

Start with the package's 11 reports and dashboard, then connect meetings to revenue with a "Booked through Chili Piper" flag on opportunities. Meeting reports use the Tasks and Events report type with the Chili Piper fields. Pipeline reports need the flag carried from the Lead to the Contact and Opportunity at conversion.

  • Out of the box: the package adds reports for meetings, meetings by team and by router, booked-by-prospect, cancellations, reschedules, no-shows, no-show rate by assignee and by booker, and cancellation rate by assignee and by booker, plus a Chili Piper Activity Dashboard. Distro's package adds a records-assigned report per object.
  • Meetings booked: a Tasks and Events report grouped by created date and assigned rep, excluding no-shows and cancellations, shows meetings that actually happened per rep.
  • No-show and cancellation rate: sum No_Show_CP and Canceled_CP and divide by the record count, grouped by assignee or booker.
  • Pipeline and revenue: add a read-only "Booked through Chili Piper" checkbox, set it with a record-triggered Flow when a Chili Piper meeting exists, and map it from Lead to Contact and Opportunity. Then an Opportunities report can compare pipeline sourced through Chili Piper with the rest.

Chili Piper's Salesforce reports article gives the report recipes. It still suggests Process Builder for the checkbox, which Salesforce has retired; use a record-triggered Flow instead.

Getting no-shows into Salesforce

No-show data is only as good as the habit of marking it. Reps can mark a no-show on the past event in Google Calendar, in the Chili Piper app, or from a custom button on the Salesforce Event. That button calls Chili Piper's API with a token a Chili Piper admin generates. It sets No_Show_CP on the Event and the related Lead or Contact. A reschedule resets the flag and adds one to the reschedule count.

Section 09 · Troubleshooting

What Are the Most Common Chili Piper Salesforce Problems?

Duplicates, blocked writes and unmapped people cause most of them. Chili Piper shows a failed Salesforce action as an error in its Concierge and Distro logs, where an admin can retry it. The fix is almost always on the Salesforce side: a rule, a picklist, a permission or a second tool writing the same data.

1. Duplicate Leads or Contacts. Chili Piper updates a matching record rather than creating a new one, so a DUPLICATES_DETECTED error usually means two systems create the same Lead at once, such as Chili Piper and a marketing automation or Web-to-Lead process. Let one source create the record, or exclude the Chili Piper user from the duplicate rule.
2. Duplicate Events. Chili Piper does not create duplicate Events by default. A second copy usually comes from Einstein Activity Capture's event sync, or from tools like Outreach or Salesloft logging the same meeting. Tell them apart by the creator and the Chili Piper fields, then turn off the other sync or filter it out. Chili Piper advises against disabling its own Event creation.
3. Validation rules and restricted picklists. A required field Chili Piper does not fill, a validation rule, or a picklist value that does not match blocks the write. Chili Piper may skip custom fields so the Lead is still created. Align the values, or exempt the integration user from rules meant for people.
4. Unmapped or unlicensed owners. A rep whose email differs between the two systems is unmapped, and an owner without a Chili Piper licence cannot be booked. Both send buyers to Not Scheduled or the wrong path.
5. You want Contacts, not Leads. Chili Piper creates Leads by default. Its Contacts-only guide lists four options: middleware, an older auto-convert Flow, Distro's Lead Conversion step, or Orchestrator. It recommends Distro or Orchestrator for new setups.
6. Expired connection or API pressure. An expired token or changed password stops every write until an admin reconnects. Chili Piper's calls count toward Salesforce's org-wide daily API allowance. Find them in the API Usage Last 7 Days report under the client ID "Chili Piper / Demand Conversion Platform", as Chili Piper's API calls article explains.

The full error list, from missing required fields to invalid relations, is in Chili Piper's common Salesforce API errors guide.

Section 10 · Alternatives

How Does Chili Piper Compare with Other Salesforce Scheduling Options?

Chili Piper is built for inbound routing and booking at volume. Lighter tools cover scheduling with some routing. Calendly and HubSpot Meetings handle scheduling and round robins well. Salesforce's own tools assign owners or book service appointments. The right choice depends on how much routing logic you need before the calendar appears.

OptionRouting on Salesforce dataBest fit
Chili PiperOwnership, account matching, field rules, round robins and record routing for any objectTeams with real inbound volume and more than one path to a rep
CalendlyRouting by Salesforce account or opportunity owner on the Enterprise plan, with Salesforce Enterprise edition or higherTeams that mainly need scheduling links, with simple owner-based routing
HubSpot MeetingsRoutes on HubSpot data rather than Salesforce; round robin can prioritise the HubSpot contact ownerTeams whose CRM is HubSpot rather than Salesforce
Salesforce lead assignment rulesOwner or queue assignment on record criteria; no bookingOwner assignment with no meeting step
Salesforce SchedulerMatches appointments to resources by policy and operating hoursService or branch appointments, on Enterprise or Unlimited edition

Sources: Calendly's Salesforce routing help, HubSpot's round robin availability article and Salesforce's Scheduler overview. If Calendly is the better fit, our Calendly Salesforce integration page covers that path.

On cost, Chili Piper's pricing page listed, in November 2026, a Growth plan from US$1,250 a month with 15 seats and a Scale plan from US$3,500 a month with 30 seats. ChiliCal alone was US$12 per user per month with a 200-seat minimum, and has no routing. Prices change, so check the page before you budget.

Section 11 · Plan

What Does a Good Chili Piper Salesforce Implementation Look Like?

It starts with the routing model in Salesforce, not with the booking widget. Chili Piper can only route as well as your ownership, territories and account matching allow. Fix those first, design the paths on paper, then configure, test in a sandbox and roll out by segment. In our experience, a straightforward first deployment takes four to six weeks.

PhaseDecisions and workDone when
1. AuditOwnership model, territories, duplicate and account-matching quality, existing assignment rules and lead sourcesKnown gaps are listed and owned
2. DesignRouting paths, round-robin type, catch-all and disqualification rules, which system creates records, field mapping, reports neededA signed-off routing map
3. Build and integrateIntegration user, connected app, field package, layouts, routers and distributions, in a sandboxEvery path tested with sample records
4. Roll outProduction connection, segment or region at a time, rep enablementLogs show no unexplained errors for a week
5. TuneWeekly log and no-show review, distribution balance, report checksLeaders report meetings and pipeline from Salesforce

This is the sequence our Chili Piper integration services follow, whether the job is a first deployment, fixing an existing setup, or custom Flow and Apex for rules the product cannot express. We are not a Chili Piper reseller, so we will also say when routing volume or data quality does not yet justify it. Rebuilds on a messy account model take longer than the typical timeline.

The same principle drove a published Salesforce sales operations and lead management case study for a UAE luxury real estate group. We built custom routing in Salesforce by property type, region, live workload and specialisation, with SLA dashboards. The case study attributes 2× faster lead response times to that routing and SLA work. It was a Salesforce-native build, not a Chili Piper project, but the routing design questions are the same. For the wider revenue process, see our revenue operations services.

Section 12 · Bottom Line

The Bottom Line

The Chili Piper Salesforce integration works best when Salesforce holds a clean ownership model and Chili Piper turns it into fast, fair meetings that are logged back where leaders report. Twopir Consulting implements, rescues, optimizes and integrates complex CRM and revenue systems, including Chili Piper with Salesforce, from routing design and field mapping to reporting and support.

  1. 1

    Fix ownership, territories and account matching in Salesforce before you build routers.

  2. 2

    Connect with a dedicated integration user, install the connected app, and give it full access to the Chili Piper fields.

  3. 3

    Install the field package in a sandbox first, and connect with the sandbox parameter.

  4. 4

    Decide which system creates Leads and sets owners, and stop the others from doing the same.

  5. 5

    Report from Salesforce Events and a Booked through Chili Piper flag, and review the logs every week.

Ready to Start

Route Every Buyer to the Right Rep, and Prove It in Salesforce

Tell us how leads reach your reps today and what your leaders need to see. We will map the routing model, the Salesforce setup and the reports your team needs.

Schedule a Discovery Call

FAQ

Frequently Asked Questions

Yes. A Salesforce admin connects Chili Piper through OAuth from the Integrations page in Chili Piper's Command Center. Chili Piper then reads Leads, Contacts, Accounts and other objects to route buyers, and writes Leads or Contacts, Events, field updates, ownership changes and campaign membership back to Salesforce. An optional field package adds custom fields, reports and a dashboard.

Not by itself. Chili Piper updates an existing Lead or Contact when it finds a match. Duplicates usually appear when a second system, such as marketing automation or Web-to-Lead, creates the same Lead at the same moment. Let one source create records, or exclude the Chili Piper integration user from the duplicate rule.

Only after the first connection. Chili Piper connects through a browser login, which an API-only user cannot complete. Connect with a standard licence first, then move the user to the Integration User licence and re-grant every permission through permission sets. Chili Piper recommends testing the change in a sandbox.

Yes. Ask Chili Piper for a sandbox tenant, open its integrations page with isSandbox=true added to the URL, then click Connect to CRM so the login goes to test.salesforce.com. Without that parameter the connection defaults to production. The field package can be installed in a sandbox too.

As standard Salesforce Events related to the Lead or Contact, and optionally to an Account, Case, Opportunity or Campaign. With the field package, each Event carries the meeting type, booking source, router, rule, team, booker, and no-show, cancellation and reschedule data, so meetings work in normal Tasks and Events reports.

Form Concierge routes a buyer who has just submitted a form and lets them book a meeting on the spot. Distro routes Salesforce records with no meeting attached, triggered when a record is created or a field changes, for any standard or custom object. It adds lead-to-account matching, SLAs and record round robins.

Chili Piper's documentation does not list supported editions. Its stated requirement is an integration user with the API Enabled permission, plus object and field access. Enterprise, Unlimited and Performance editions include API access; on other editions, confirm API availability with Salesforce and Chili Piper before you buy.

In November 2026, Chili Piper's pricing page listed a Growth plan from US$1,250 a month with 15 seats and a Scale plan from US$3,500 a month with 30 seats, with Enterprise pricing on request. ChiliCal alone was US$12 per user per month with a 200-seat minimum and no routing. Check the pricing page for current figures.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Chili Piper, Outreach and other revenue tools connected to Salesforce, for 500+ clients over 12+ years.