51 results found
-
Record Ownership Capping
Allow admins to set maximum record limits per owner in Distributions. When an owner reaches their cap, records would be routed to the next available owner or a fallback queue. Use cases include: balancing workload across reps, preventing rep overload during high-volume periods, and supporting tiered capacity models.
5 votes -
Merit-Based Lead Distribution
Customer's would like to be able to route leads based on merit. Essentially rewarding better reps for performance.
Quota Attainment Pure performance against targets. Did you hit your number?
Efficiency Metrics Close rates by deal type, sales cycle length, and conversion rates at each stage. How effectively do you convert opportunities?
Quality Performance AI-powered analysis of pitch quality, demo effectiveness, and overall sales execution. How good are you at the craft of selling?
These scores combine to create a dynamic ranking system that determines pipeline allocation for the following month.
7 votes -
Customize/supress "Already Routed" error in Concierge
I'd like to have the ability to customize or suppress 419 "Already Routed" error modal in Concierge
2 votes -
Spam Checker for Distro?
I noticed we have spam checker filtering for Concierge; I would love to see this ability on Distro too!!!
2 votes -
Multi round-robin assignments
Concierge: offer multi round-robin assignment for users who don't schedule a meeting. This can automate the assignment to users on separate teams (ie: AM & CSM).
2 votes -
Native enrichment
Ability to enrich at the time of form fill natively within Chili Piper. Meaning customers don't need to have a separate relationship with a data enrichment vendor and can instead do it natively in Chili Piper.
4 votes -
AI Generated Flows
The addition of an AI agent that can intake a prose style description of routing pathways and outcomes and translate that into a router framework. Ideally across all routing products.
3 votes -
Enable routing based on User Object
There are data values from the User Object that would be helpful to use in routing rules. Things such as % attainment to pipeline, close rate, no show rate, etc, are all values that can be tracked in Salesforce. It would be fantastic to then have a way to turn those user insights into routing criteria when building rules.
5 votes -
Adding 'Call Rep' as a next step after both 'Contact Options' are not selected
Adding 'Call Rep' as a next step after both 'Contact Options' are not selected.
Currently, in the router set up if you select 'Display Contact Options' it will show (1) Request a Call, (2) Schedule a Meeting. In the worst case scenario neither option is selected, we'd like to insert a 'Call Rep' action to "autodial" all the leads that don't schedule.
The only option is to "redirect to". can we fix this?
1 vote -
Ability to manage Rules in a table and have them sync to Chili (maybe via API)
Rather than creating and managing Rules in Chili, the request is to be able to manage them externally in a table, such as Google Sheets, and then have a way to call and update them in Chili Piper.
2 votes -
Ability to duplicate routing paths in the Handoff Router
I'd like to have the same ability as the Concierge router to duplicate existing paths
6 votes -
Distro - Record Ownership Capping
Allow admins to set maximum record limits per owner in Distro rules. When an owner reaches their cap, records would be routed to the next available owner or a fallback queue. Use cases include: balancing workload across reps, preventing rep overload during high-volume periods, and supporting tiered capacity models.
1 vote -
Person-to-Lead - Related Lead Matching for Concierge
Current Situation
Lead-to-Related Lead Matching allows Chili Piper to route new leads based on existing lead records in Salesforce that share the same email domain.
Example:
Existing Lead: robbie@chilipiper.com
(owned by Rep 1)New Lead: sorin@chilipiper.com
Since both share @chilipiper.com, Chili Piper correctly identifies they’re from the same company and routes Sorin’s lead to Rep 1.
✅ This works only if robbie@chilipiper.com
already exists in Salesforce as a lead record at the time Sorin’s form is submitted.The Problem
If robbie@chilipiper.com exists as a lead record when sorin@chilipiper.com submits the form (but sorin@chilipiper.com does not), there’s no existing lead to…
2 votes -
AI Generated Rules
The ability to enter a prompt and have rules built by AI
1 vote -
Template for Slack notifications
Customers can add a Slack notification at the end of every assignment/path, and oftentimes, the message at the end of the path is the same. If someone has a flow with 25 paths, that's 25 places they need to update the Slack message any time they want to make a change.
In LeanData, you could point a your routing back to 1 Slack node (which had it's own problems), but that meant you only had to update it once.
The ideal state would be: I define one template for demo request, and I can apply it the same way that…
1 vote -
Interface to add new fields for enrichment within Enrichment Provider.
For integrated enrichment and form shortening in CP we only display certain fields from the enrichment provider out of the box. If a customer wants to add other fields from their provider to use, we should allow that to be handled within the enrichment interface.
1 vote -
Ability to route from Salesforce Enterprise Territory object
Integrate with and “read” Salesforce’s Enterprise Territory Management (ETM) object when routing, distinct from Account or Opportunity team assignments.
This enables routing logic for enterprise customers using ETM for sales alignment and expands support for complex enterprise orgs.
1 vote -
Ability to Test Distro Before Publish
Ability to Test before Publish. LeanData allows us to enter a test data and “run” through the journey to see which path it will take so we can do testing before we publish the update to real live environment. I know that we can spin up copies of Chilli Piper journeys and test it on our lower-level environments, but this is not as easy as being able to do it all inside a single tool
1 vote -
Add more than one Team to a Distribution.
Allowing to combine several teams in a distribution will ensure the necessary coverage when the teams are small.
2 votes -
Add a Description field/column to Router metadata
Simple request for 1 new field/column in the Router metadata so that we can add Description/Notes that are not feasible to capture in the Router Name alone
3 votes
- Don't see your idea?