66 results found
-
Strict Round-Robin Distribution Option
Would prefer the option to show ONLY the calendar for the next rep in the queue. Classic round-robin distribution instead of combined availability of all reps in queue. rep1-rep2-rep3-rep4, then back to rep1-rep2-rep3-rep4. If a meeting no-shows or cancels, it is the rep's responsibility to get the meeting back on the calendar themself .
58 votesWe now have strict distributions available on the Demand conversion platform! More details here!
-
Fuzzy Matching for Account Matching
Adding the ability to search on multiple factors for Account Matching in addition to just email domain. This would solve for situations where companies have multiple accounts for the same company (typically different country locations).An example would be searching based on email domain + another field such as country.This would also allow for matching to accounts for public email domains as well.
37 votes -
Improvements to "Default Booker" of a Meeting Queue
Long-winded lead-in:I am an admin user and my company primarily uses Chilipiper for Concierge purposes. As a best practice, we want to use the credentials of a system/not-actual-people users as the primary means of integrating SaaS services together (e.g. Salesforce <> ChilIPiper). This future-proofs our tools for when people leave the company or go on vacation etc.We have done that for Salesforce, but I also wanted to specify that the Default Booker in our meeting queue as that same system user. However, the email address associated with the system user is a Google Group alias (we generally do not…
19 votesThe default booker is no longer apart of the Demand Conversion Platform and thus should resolve the issues mentioned!
-
More Than a Single Router Re-Direct
We have the need for more than one router redirect if the appointment request is a current client and if the client is international and we do not service their area yet.
15 votesWith the flow view in Concierge, you can now set up a redirect per path. So redirects are now customizable!
-
Route Leads from Spreadsheet Upload
After a conference, ability to use Chili Piper to upload a list of lead-scans to be distributed to reps via Chili Piper's routing logic.
14 votesAvailable in Distro Fire - More details here
-
Don't include reps on vacation for unbooked round robin
Chili can detect when a rep is on vacation and not book meetings for them during that time, but that rep will still receive unbooked leads via the round robin. Ideally, someone on vacation wouldn't receive these either and the only way around this is to manually remove people from the queues.
14 votesThis is resolved on the Fire platform – 'Prospect/Record' distributions used in the 'unbooked' paths in Concierge (plus Distro and Chat) will respect vacations.
-
Custom Object Routing
Being able to route custom objects via Chili Piper would be incredible!
14 votesThis is available for all products on the Demand Conversion Platform!
For Distro, you need to go to "Object" and enable the Object to trigger from there.
For the other products, you have access to other objects through the rule builder in explicit mode
Lead > Custom Object > ...
-
Search all open opps for matching criteria
Search all open opportunities for a match to Queue criteria rather than just last modified.
13 votesThis is possible on the Fire platform in the Matching Hub. The Match to Opportunity tab has the option to change the filters (e.g. show Closed Won opportunities not just open for post-sales use cases) and tiebreakers (e.g. prioritise based on the created or close date instead of last modified). https://help.chilipiper.com/hc/en-us/articles/33532253394323-Matching-Leads-Contacts-to-Opportunities-and-Cases-with-Chili-Piper
-
Conditional Redirects with Concierge
As of today, Chili Piper can redirect upon specific actions - a meeting being scheduled, a prospect being DQ’d, etc. It would be great to be able to conditionally redirect based on their form-filled values.
13 votesWith the flow view in Concierge, you can now set up a redirect per path. So redirects are now customizable!
-
Prevent rep from manually selecting queue
Want admins to be able to limit reps ability to select alternative queues or non-matching queues.
12 votesThis feature has been released as of Feb 8th 2024. The setting exists at the top of the "Workspace Settings" tab. When the setting gets unchecked, it hides the "Unmatched" queues to prevent the Booker from selecting that queue.
-
Make Ownership Based Routing Strict within Instant Booker
Reps are picking other Sales People in my Ownership Routing Queues. I need to be able to make Ownership based routing queues strict.
11 votesThis feature has been released as of Feb 8th 2024. The setting exist at the Queue level under the "Ownership" Option in the "Algorithm" tab.
-
Create Lead to Lead (L2L) Routing
Prospects and Customers love the Chili Piper L2A matching routing capabilities. Routing based on the website domain or the email domain is a highly valued feature that gives Chili Piper a competitive advantage. It will be amazing if Chili Piper can route with the same logic for Lead to Lead (L2L) routing. This would allow a Lead to be routed to the owner of another Lead that has the same domain. It could use the same logic of matching by website domain or individual email domain.Lean Data and other routing softwares' offer this. It would be great if Chili Piper…
11 votes -
10 votes
No longer an issue on the Demand Conversion Platform!
-
Allow Default Meeting Type at Router Level
Having a default meeting type set for each queue means that queues have to be duplicated for each meeting type even though the rules are the same. It would be much less overhead if the meeting type could be configured at the Router level so that queues could be used with multiple different routers. With dozens of queues, duplicating them for every meeting type isn't scalable at all. Having a default meeting type for the queue would be fine as long as it could be overwritten by the meeting type set at the queue level (if one is set).
9 votesYou can achieve this using our newly released feature to pass Meeting Type via Router URL and via JS API.
-
Allow Admins to see which users are in which queues from queue list
Its frustrating and difficult to have to click into each queue to see who is in it. You can see queue membership on the USER level by hovering over those users. Why not see membership from the queue level?
8 votesTeams and distributions allow you to easier see and group users. Available in our Demand Conversion Platform.
-
Specify meeting type when booking a meeting through ROUTER url
Smart booking links https://help.chilipiper.com/hc/en-us/articles/360053021254-Smart-Booking-Links makes it possible to specify the Meeting Type as a URL parameter for meetings.. but not for Routers. The Router meeting link should accept the Type parameter and then over-ride the default meeting type.
7 votesWe now allow passing of meeting type via the Router URL and via options in the JS API :)
-
Ability to Change Team in Distribution after Publishing
When creating a distribution on the Fire Platform, we assign a team, but then it is not possible to change the team without re creating the whole distribution.
We need to be able to change the team in the distribution
6 votesYou can now swap out the team in a Distribution without rebuilding it from scratch. This makes it easier to respond to org changes while keeping your routing logic intact. Once you update and re-publish, your stats will reset for a fresh start.
-
Greater/less than date field rules in Distro
Currently it is not possible to create a rule in Distro where "Date Field is greater than X Date." You have to create a formula field in Salesforce to calculate the UNIX date and then reference that field in your Distro rules. Being able to reference date fields directly opens up a lot of doors for routing and simplifies the process.
6 votesAvailable in the rules asset.
-
Manually rearrange distro team order
Currently you cannot rearrange the order of members in a distro team. New team members are put on top of the team list. We should be able to order the team members using either arrows (like queue arrangement) or via drag and drop functionality so each team doesn't have to be rebuilt when new members are added. This is specifically for Distro
6 votesUsers can be reordered in Teams asset
-
Adjust Current Level calibration
If a queue is built out with weighting, lets say one rep is 5 meetings for everyone elses 1, when calibration "current level" resets to zero, as soon as they take one meeting we bump the other person up next in the queue because the person set to 500% is at .2 level which is higher than zero. Customers (home depot for example) want the reps set to 500 to take 5 meetings before allowing the other rep to take one. we should set calibration up to understand this
6 votesThe specific example shared is resolved on the Fire platform. Previously the 'Current Level' always started at zero, which could not be multiplied nor divided by the weighting percentage. Therefore, everyone body received one meeting at the start of a reporting cycle before the weightings kicked in. On Fire, everyone starts at 1, which enables higher weighting for senior reps (e.g. 1/200% = 0.5) or decreased weighting for junior reps (e.g. 1/50% = 2) on day one of the cycle.
- Don't see your idea?