60 results found
-
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 -
Rules Validation
Be able to either test either an existing or new lead contact in SFDC against your routing criteria and display a visual of what criteria that lead does or does not meet.
4 votes -
Assign team members to Routes within a distribution
I'd like to create a meeting queue, say, "Home Tour". This queue routes to different salespeople based on the user's location which we pass to Chili Piper. I'd like to be able to assign different team members to each location all within the queue.Something like the screenshot attached. This would be much cleaner for us than having to create 10+ queues for each market we are in and then add rules within each queue. As we expand, it's going to become a nightmare to look at and understand.
4 votes -
Write related Account to Lead in Distro
Stamp related Account/Contact to a field on the Lead Object.
3 votes -
Write to Salesforce custom field when matched L2A
Would love the ability to match a Lead to an Account and not route to the Account owner.
Being able to write to a field on the Lead object which indicate it's matched to a certain account but hasn't been routed yet.3 votes -
Add Details to Email Notifications to Assignees
It would be so helpful if we could see the kind of record Chili Piper is routing in the notification emails, maybe by including the name of the router responsible. We are using Chili Piper for a few different use cases, so being able to differentiate would be so helpful.
3 votes -
Distribute to the same rep the calendar was shown through DTA
When the calendar loads after filling out the form of an Inbound Router through Concierge, we start the ownership update upon the lead creation at this moment for the rep the meeting will be booked with.
However, if the prospect takes longer to book the meeting, they can be reassigned to a different rep through the QFPWDTA.
The goal is that if the same queue is enabled on the Scheduling Queues and QFPWDTA, we should assign and distribute the lead/contact to the same rep.3 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.
3 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.
-
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 -
Distro/Form Concierge - Path Branching
It would be fantastic to build out more customization in routers rather than always having to go in a straight line by rules. More complex routing options like A) branching (based off a single rule or if/then criteria) would make the organization and rule building within routers much easier to follow (and educate others on).
Also, that ability to have rules trigger or route after another rule would be helpful. So basically first it checks for something like A) market segment and then B) checks territory. You could then build the secondary logic under the first branch to better understand…
2 votes -
Mark held meetings that were unqualified to credit back a rep
Weighting in Salesforce and Chili Piper differ because in Salesforce it's based on meetings held whereas in Chili Piper it's based on meetings booked. To make it easier to have the two match, there should be a way in Chili Piper to mark a held meeting as unqualified and credit the user back a meeting. Currently we can credit back no shows - but not unqualified held meetings.
2 votes -
Allow configuring order based on recency when matching against opportunities
We use ownership rules heavily and our rules match against opportunities and their owners. Opportunities in our Salesforce instance can have different owners. Because Chili Piper randomly selects an opportunity to match against currently, this leads to inconsistency in terms of how the ownership rule is applied, which undermines the effectiveness of the rule. Please provide the ability to control the sort order in which opportunities are pulled back (or provide a sane default - always use the most recent opportunity based on the criteria) so that this rule can be relied upon.
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 -
Either Deny Ability to Pull "Unavailable" Rep from HH Queue or Designate in Reports
We run into a common problem with very small queues (for example, our AE1s, of which we have <20) and during certain times of day (i.e., morning huddles or lunch periods) where the queue itself is devoid of "Available" reps. When this happens, we have a separate process we would like our SDRs to follow to find a warm body for the live transfer; however, in their haste, they often do not even notice that the queue is empty and suggesting an "Unavailable" AE -- and will pull them out of rotation when they cannot take the call. When this…
2 votes -
Remove calibration impact of removed users
Remove the calibration-effect of a user if they're removed from the queue
2 votes -
Ability to bulk deactivate & reactive users
We have a process that requires that SDRs be removed completely from routers when they are on PTO. They can not receive new leads even within their calendar availably when they are out on PTO. Because of this process, It would be great if we could remove and re-add users in bulk vs. having to go into each queue and do so manually.
2 votes -
Customizable Internal Email Notification
Allow the internal email being sent to the new lead owner. This will allow for the email to include various fields the internal teams want to know without having to click into the record and dig around.
Example:
Subject:
New {!routed lead.leadsource} lead! {!routed lead.company}
Message:
Lead Link: https://seesaw.my.salesforce.com/{!routed lead.leadidcaseinsensitive_c}of Students (Opportunity): {!routed lead.opportunityofstudents__c}
Total Enrollment: {!routed lead.numseesawstudentstotalc}
Name: {!routed lead.name}
Role: {!routed lead.rolec}
Organization: {!routed lead.company}
District Account ID: {!routed lead.districtaccountr.accountidcase_insensitivec}
District Account Name:{!routed lead.districtaccount_r.name}1 vote
- Don't see your idea?