52 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
-
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 > ...
-
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.
-
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 :)
-
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
-
Create CP Form Fields without Linking them to Salesforce
Can it be possible to create form fields without having to link them to a field in Salesforce?1. The team wants to collect information that isn't always stored on a Lead or Contact.2. It's not scale-able for us to create a new field on Leads and Contacts for each data point the team wants to collect (i.e. Facebook URL, Facebook username, Facebook password, Twitter URL, Twitter password, EMR, etc).
5 votesNow available on the demand conversion platform with Data fields - More info here.
-
SFDC Account Teams Routing
We have customers like Shopify and Avalara moving away from multiple lookup fields to Account Teams and would like this to be supported in our routing/rules.
5 votes -
Monitor Multiple Fields for Triggers
Currently, the Distro Trigger can only monitor 1 field for "When a specific field is updated." Having the ability to monitor multiple fields would be a big lift for us. We have a Primary Field, which we are using, but being able to monitor multiple fields would be a very nice to have.
Through the Entry Rules, we can make sure only the right Leads/Contacts are routed, but with only a single Trigger field, it makes it difficult to capture the right Leads/Contacts.
Ideally it would be similar to the Field Update interface where you can add multiple fields to…
3 votesYou can now Trigger Distro with multiple fields! Gif attached.
-
Adjustable Booking Span for Start and End of Vacation Period
Currently, there is a standard booking span (ie. 4 days) for both before the start of vacation, and before the end of vacationFor example, having booking span set at 4 days means a rep will be removed from the round robin 4 days before they go on vacation, and they will re-enter the round robin 4 days before they return.It would be more convenient to set the time-frame individually at each end of the vacation period. ie. remove from round robin 2 days before the start of vacation, but re-join 4 days before the end.
3 votesAvailable in the demand conversion platform under Distribution settings.
-
Default Concierge cal language
Concierge header calendar language defaults to "what time works best for a quick call" above the date selector and then immediately under the date selector and above time selector is "what time works" this is awkward messaging and first one should default to "what day works"
3 votesNow customizable in router customizations on the Demand Conversion Platform.
- Don't see your idea?