94 results found
-
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 queues 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 -
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.
5 votes -
Delete first queue rule
Currently not possible to delete first queue rule in a list.
2 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…
9 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 -
Queue Rule config with logic tree
Instead of writing the conditions with AND and OR, it'd be easier to describe the queue rule with a logic tree. Some major routing software offers it and it's fool proof than writing conditions with AND and OR.
1 vote -
Don't use commas to separate queue keywords
Use a visual or other indication of a separate queue keyword so that commas in picklists can be used for routing.
1 vote -
Drag and drop users in queue order
It's very time intensive to manually click up or down to rearrange users in large queues.
1 vote -
Search all open opps for matching criteria
Search all open opportunities for a match to Queue criteria rather than just last modified.
11 votes -
Queue Rules View
Easier way to keep track of the rules related to a queue, which does not involve opening each queue.
1 vote -
Existing Lead to Account Matching in Distro
A customer is interested in using Distro to match existing Leads to Accounts in Salesforce. This would be matching based on email domain as well as company name (fuzzy matching).
1 vote -
Deduping in Distro
Many customers look for deduping in their routing software to help keep their CRM data as reliable as possible. For example, LeanData offers deduping. We have seen many Distro cross-sell opportunities fall through because Distro cannot do deduping.
2 votes -
Leverage existing teams and rules between distro & concierge
Be able to bring over existing meeting queue rules to distro to make the build easier.
2 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 -
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 votes
- Don't see your idea?