4 results found
-
Declarative (code) flow descriptions
It would be very helpful—and in some cases game-changing—to provide a way to describe routing flows using code instead of the web UI. For complex flows with many routing rules and distributions (e.g., 10 sales teams in various regions or countries, speaking various languages), it's very inconvenient to maintain such a flow consisting of dozens of routing nodes.
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 -
Mass Distribution updating/grouped Distributions for easy rule changes
When working with 50+ queues due to large territories or broad teams/larger organizations, updating queues becomes a tedious and time-consuming task. It would be great if you could group queues together, and change a queue setting or add/remove a particular rule from the entire group at a time. Alternatively, you could select from a list of queues which to update, and trigger a mass update without a specific group defined.
18 votes -
PTO management and booking when PTO ends
Currently, when a rep who is in a queue has their calendar blocked off for PTO Chilipiper marks them as OFF and they are not selected in queues until their calendar block ends. For example, if I'm on PTO this week with my calendar blocked for all day events and someone is trying to book a meeting for next week, I won't be next in queue and am marked OFF, even though my calendar is empty the following week. This feature needs to be smarter and recognize that I'm bookable next week, even if my calendar is blocked today.
1 vote
- Don't see your idea?