51 results found
-
QA/UAT Environment Setup for Concierge Routers Testing
We currently have 20+ advanced concierge/routers and need a dedicated QA/UAT environment to test them under the same conditions as in the production workspace.
Issue:
• The application does not support copying between workspaces, requiring us to rebuild everything manually, which is inefficient and time-consuming.Request:
• Enable a QA/UAT environment where concierge routers can be tested exactly as they function in production.
• Provide a solution to copy configurations between workspaces to streamline testing and deployment.3 votes -
3 votes
-
Export Logs - Distro
Add export logs functionality to run the analysis per the routed lead.
3 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 -
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 -
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 -
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 -
Convert Lead and relate the Contact to a non-matched Account
We're looking at switching to a Contacts-only model in SFDC and want to convert leads in one of two ways:
- If there's a matched account, you convert the record under that account.
- If there's no match, it's still converted but under a specified placeholder account instead.
We do not want to create a new Account if there's no match.
2 votes -
Job feature within Distro
Would love to replenish accounts for an AE/SDR who has less than 150 accounts. (e.g. if an SDR has <150 account in "working", then we route them more accounts"
2 votes -
Names for groups in rules
When you have several branches of logic, it's hard to know what each group is used for. Helpful to be able to name the group so it's easier to update later. For example, Group 1 name could be US Territory.
2 votes -
Do not consider inbound meeting count if booked on a weekend/extra hours in the day
There is a situation in our org where the sales persons work extra hours/weekend currently with the round robin routing they will have to wait for others to catchup weightage that's no bounty for the extra effort for the sales people.
Is there a way to build a system that only consider round robin for the office working hours and extra hour/weekend meetings aren't counted?
2 votes -
Ability to automatically load balance meetings between reps POST BOOKING (and automatically reassign meetings)
Currently we use weights to try to ensure reps are load balanced from a schedule perspective, however, we've found this to be insufficient and end up needing to manually reassign meetings between reps. We'd love for Chili Piper to be able to automatically reassign meetings between a pool of reps as schedules firm up.
2 votes -
Sales Level Agreements across the platform
We did a demo of distro and my biggest takeaway was the SLA actions tool. We've been working on that in our org separately and the tool accomplishes a couple of things that would be useful on their own or tied to concierge as well. The time dependent actions can be really difficult to set up inside a CRM on its own and that would really simplify that process. Also being able to schedule slack reminders would be a huge benefit for everything we currently use.
2 votes -
Make Round Robin reset override per distribution
Currently the ability to reset Round Robin Fairness calculation resides in the Workspace settings. It would be fantastic if you could set an override on individual queues to make the reset happen more frequently, or less.
2 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 -
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 -
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
- Don't see your idea?