60 results found
-
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 -
Redirect links for deactivated users
The ability to redirect a personal booking link, for when employees leave a company but have emails out using personal booking links
9 votes -
Ability to read a time stamp in Salesforce
Ability to read a time stamp in salesforce. For example 8:00 needs to be routed to an EST rep while 17:00 should be routed to PST rep
1 vote -
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 -
Query Salesforce based on Account Record
Be able to query Salesforce based on Account Record Type when looking at ownership rules. For large companies with multiple account types only looking at 5 accounts isn't enough and the value will Chili Piper decreases over time as more accounts are added.
1 vote -
Move to another queue if ownership is unavailable for defined # of days
Ability for clients to set a variable # of days that if lead matches to owner but owner is not available for X number of days, move to route through other queues. This would solve for vacation or extended OOO without manual intervention from Chili Piper POC and prioritizing booking the meeting over waiting for an owner.
9 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 -
Sales Level Agreements from Distro Available Elsewhere
We did a demo of distro and my biggest takeaway was the SLA actions tool. We've been working on that in our org separately and the tool accomplishes a couple of things that would be useful on their own or tied to concierge as well. The time dependent actions can be really difficult to set up inside a CRM on its own and that would really simplify that process. Also being able to schedule slack reminders would be a huge benefit for everything we currently use.
1 vote -
Include two "owners" in a meeting
Be able to include one owner from X field in SF and another owner from Y field in SF on a meeting in a scalable way - ie, not by using a group booking queue.
4 votes -
Ability to easily PAUSE reps from distirbutions for leave
Want ability to pause a rep in queues rather than individually remove from each queue. the main issue is with such a large sales org, there are a lot of instances where reps either forget to mark their calendars as OOO or unexpectedly have to go on leave, and the only solution for us is to completely take them out of each of the RR.
5 votes -
Warning alert to super admins on sudden / dramatic decrease in form routing
Dramatic decrease in Chili Concierge volume should send warning to super admins that something may be wrong - otherwise, if you don't hear from your reps or look in reports regularly you could miss tons of opps if say, a website change was made, or an integration was deployed on your site that you didn't realize would affect Concierge, or some other random event. Would be superior if the "dramatic" criteria could be set by the customer - such as if we see X percent decrease in x amount of time, or if we go 1 hour with no leads…
10 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 -
Search all open opps for matching criteria
Search all open opportunities for a match to Queue criteria rather than just last modified.
12 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 -
Salesforce Queue
There is no way to identify if a SF record is owned by a queue. None of the drop down options allow for recognizing a record owned by a queue in SF when building out queue rules.
1 vote -
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 -
Account Ownership Recognition within "Queues For Prospects Who Don't Take Action" when Lead Creation is Disabled
In a scenario where lead creation is turned off, when a prospect matches L2A during initial routing, but then doesn't select a meeting time, they're routed via Queues for Prospects Who Dont Take Action. QFPWDTA does not account for Ownership queues if they are net-new and lead creation is disabled. It would be great if we could create some kind of key from the initial routing that holds true when QFPWDTA takes place, allowing for L2A at that time.
1 vote -
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.
-
Algorithm Reset Intervals
ability to choose from a range of intervals in which the Round-Robin algorithm resets itself from the Workspace Settings ie., 1, 3, & 6 month intervals. This is for quarterly and semi-annual reporting purposes on their end.
8 votes
- Don't see your idea?