61 results found
-
Distro for Hubspot
Use Distro for Hubspot
4 votes -
Allow for Distribution based on Busy/free availability of selected user
Allow for Distribution based on availability in Distro
Research says a lead has the highest intent within 7 seconds. Therefore, if Chili can be distributed within 7 seconds, it should be able to be distributed to only available reps.
Specifically, if the user is in a meeting at the time of routing route to someone else.
4 votesWe can route based on rep availability if they are out of the office and set fallback teams or users. But not yet the ability to do this based on specific meetings. IE if the rep is in a meeting during time of routing they will still be routed the lead at this time.
-
Add additional questions after routing with Concierge but before booking
Want to reduce friction by only asking for a couple criteria up front and then immediately showing the available times. After selecting a time, want to show additional questions BEFORE submitting. Basically the same flow as the standalone booking links, but with Concierge as well.
4 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.
3 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 -
Speed to lead tracker
Being able to identify how long it took a rep to reach out to prospects. We can track if they hit the SLA or not, but can't say it took 10,15,20 minutes etc. Having a way to track this on the lead and also show the average per rep.
3 votes -
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 -
Send a notification when the CRM actions are stuck in pending status
Send a notification to the Admin whenever the CRM actions of a Concierge record is stuck in pending for more than X minutes.
3 votes -
3 votes
-
Recognize invalid id= parameter in router
Right now if you provide an invalid value for the id query string parameter, the prospect books and fills out a form. But CP uses the bad id value to do the Salesforce lookup and an API error is generated. Would like CP to recognize this case and create the lead/contact instead
3 votes -
Add hide_x=true option to Marketing.js
When implementing Chili Piper across different pages, we would like to have the option to hide the X for some popups (e.g. when embedded in a DOM element), and not for others. Currently, this is only achievable using the REST API or with CSS for the entire workspace. It would be very useful to have a JS option for the JS API to hide the X.
3 votes -
Fallback mechanism for Chat
Have a fallback mechanism similar to what we have for Distro
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 -
Export Logs - Distro
Add export logs functionality to run the analysis per the routed lead.
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 -
Apply manual calibrations to all distributions in a group
Currently, any manual calibrations made to a queue are not automatically reflected in other queues across a group. An admin must instead add/remove meetings to every queue in a group manually to keep them balanced.
2 votes
- Don't see your idea?