On this page (15)
Chili Piper connects to Salesforce to route inbound leads to the right rep and let qualified buyers book a meeting the moment they submit a form. Concierge handles form routing and instant scheduling, Distro routes Salesforce records such as leads, contacts, accounts, opportunities and cases with lead-to-account matching and round robin, and Handoff passes meetings from one rep to another. It adds the most value when speed to lead matters and native Salesforce assignment rules have become too complex to maintain.
What does each part do?
| Product | What it does | Where Salesforce fits |
|---|---|---|
| Concierge | Qualifies and routes web form submissions and offers qualified buyers a calendar to book immediately | Reads Salesforce data to decide ownership and writes the meeting and lead back |
| Distro | Routes Salesforce records with lead-to-account matching, round robin, weighting, SLAs and vacation handling | Works on standard and custom Salesforce objects; Chili Piper's package adds fields to report on routed records |
| Handoff | Lets one person, such as an SDR, book a meeting on another person's calendar using routing rules | Uses Salesforce ownership and field values to choose the right rep |
When is Chili Piper worth adding?
- Inbound demo requests wait hours for a reply, and you lose buyers who would have booked on the spot.
- Assignment rules, queues and flows have grown into logic only one admin understands.
- Leads from existing customers or target accounts need to reach the account owner, not the next rep in rotation.
- SDRs hand meetings to account executives and the handoff is manual.
If your volume is low, rules are simple and response time is already fast, native Salesforce lead assignment rules or Flow may be enough. Chili Piper's value is speed and maintainability as routing grows.
What to design before setup
- Ownership rules: when a lead matches an existing account, who owns it, and what happens for partners or open opportunities.
- Qualification: which form answers or Salesforce values make someone eligible to book immediately.
- Distribution: round robin groups, weighting by capacity, and out-of-office handling.
- SLAs: how fast a rep must follow up, and what happens when they do not.
- Data writeback: which Salesforce fields record routing and booking, so reporting works.
- Conflicts: turn off overlapping Salesforce assignment rules or flows so two systems do not reassign the same record.
How do you measure it?
- Speed to lead: time from form submission to first meeting or first touch.
- Booking rate: share of qualified form submissions that book a meeting immediately.
- Meeting show rate and conversion to opportunity.
- Routing accuracy: share of leads reaching the correct owner the first time.
How do you write routing rules people agree on?
Routing tools only automate decisions the business has already made. Before configuration, get sales, marketing and RevOps to agree on the rules in plain language, then build exactly that.
| Decision | Example answer | Who signs off |
|---|---|---|
| Who owns a lead from an existing customer? | The account owner, unless the account is unassigned | Sales leadership |
| Who gets new-logo leads? | Round robin within the territory team, weighted by capacity | Sales leadership and RevOps |
| Who can book immediately? | Companies above a size threshold in target industries | Marketing and sales |
| What happens when the owner is out? | Route to a named backup, then to the round robin | Sales managers |
| How fast must reps follow up? | Within a set time during business hours, with escalation if missed | Sales leadership |
| How are partners and open opportunities handled? | Route to the partner manager or opportunity owner | Sales and partner teams |
Common setup mistakes
- Routing rules that do not match the lead assignment rules in Salesforce, so meetings land with one rep and records with another.
- Round-robin pools that ignore time off, so prospects book with people who are out.
- No owner for the routing logic, so it drifts as territories change.
- Meetings booked without the source and form recorded on the Salesforce record, which breaks attribution.
- Turning on several routing tools at once, so records are reassigned more than once.
A launch plan
- Map every form and entry point that should offer a meeting, and which should not.
- Write routing rules in plain language, build them, then test each one with sample leads that cover every branch.
- Turn off overlapping Salesforce assignment rules or flows for the same records.
- Agree what counts as a held meeting and how no-shows are recorded.
- Build a report of booked, held and converted meetings by source before launch, so you have a baseline.
- Launch on one form or segment first, review results after two weeks, then extend.
How do you keep routing healthy after launch?
Review routing accuracy and speed to lead monthly. Check a sample of routed records against the rules, confirm out-of-office handling worked, and update round-robin pools when people join or leave. Treat routing changes like any other Salesforce change: requested, tested and recorded.
Frequently asked questions
Can Salesforce do this without Chili Piper?
For simple rules and moderate volume, yes: lead assignment rules, queues and Flow can route records. Teams usually add a dedicated tool when they want instant booking from forms, lead-to-account matching that is easy to maintain, or routing that business users can change safely.
How do we prove it worked?
Compare speed to lead, booking rate, show rate and conversion to opportunity before and after launch, using the baseline report you built first.
Who should own routing: marketing, sales or RevOps?
Usually RevOps, with sign-off from sales and marketing on the rules. The owner needs both the authority to change rules and the access to test them.
What breaks most often?
Overlapping assignment logic in two systems, round-robin pools that are out of date, and forms that collect the wrong fields for routing decisions.
A rollout timeline
| Period | Focus | Check |
|---|---|---|
| Weeks 1–2 | Agree routing rules, map forms, build a baseline report | Signed-off rules and a before picture of speed to lead |
| Weeks 3–4 | Configure and test every routing branch with sample leads | Each branch reaches the right owner in testing |
| Weeks 5–6 | Launch on one form or segment, review daily | Booking rate, routing accuracy and no-show handling |
| Weeks 7–10 | Extend to remaining forms and add handoffs between SDRs and account executives | Results hold as volume increases |
Glossary
- Speed to lead: the time between a form submission and the first meeting or touch.
- Lead-to-account matching: linking a new lead to an existing account so it reaches the account owner.
- Round robin: distributing records evenly, or by weight, across a group of reps.
- Handoff: one person booking a meeting on another person’s calendar under routing rules.
Routing is a business agreement first and a configuration second. When the rules are written, agreed and owned, the tooling becomes the easy part.

