32 results found
-
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 -
Show version history and live version in routers
There needs to be a way to see what the live version of the router is and what the draft looks like similar to how in Zapier you can compare a live version vs a draft version. This is helpful in building potential staged changes to review before setting (publishing) them live.
1 vote -
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 -
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 -
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 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 -
Copy groups of nodes across routers
When building multiple routers, ideally we'd be able to copy certain groups of paths/nodes from 1 router, to reuse across other routers.
1 vote -
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 -
Auto-resetting Meeting Limit
When setting a meeting limit, the current functionality is that it will take folks out of the routing until the time resets. As an automated feature, it would be nice for the meeting limit to reset back once everyone has reached the initial meeting count. For example, once the entire team reaches 3 meetings, it would reset the meeting count or bump the number up to 6 meetings.
1 vote -
Declarative (code) flow descriptions
It would be very helpful—and in some cases game-changing—to provide a way to describe routing flows using code instead of the web UI. For complex flows with many routing rules and distributions (e.g., 10 sales teams in various regions or countries, speaking various languages), it's very inconvenient to maintain such a flow consisting of dozens of routing nodes.
1 vote -
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 -
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 -
Include form values in redirect URL as part of the URL instead of as Query Parameters
I'm trying to redirect to landing pages based off the locale of a user so they get redirected to a page translated to the correct language. The locale is typically part of the URL and not a Query parameter. It would massively reduce the complexity of our routing if we could simply specify a spot in the URL to place a value from the submitted form.
For example: https://ourwebsite.com/<locale_code_here>/thank-you
1 vote -
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 -
Can we removed Meeting Type that does not have schedule link from Handoff Router
Can we removed Meeting Type that does not have schedule link from Handoff Router
1 vote
- Don't see your idea?