Our team uses branching rules to route conversations to the correct workflows, but once messages enter a branch, there is no option to distribute workload evenly. This creates uneven assignment, unassigned emails, and extra manual queue management.
It would be very helpful if branching rules included an optional load balancing setting (round-robin or load-based), similar to the existing load balancing option in standard rules. This would allow conversations to be both routed and evenly distributed in a single automated step, especially when volume is high or certain advisors are OOO.
This enhancement would reduce manual reassignment, prevent overload on specific advisors, and improve SLA consistency.
Your idea is now live and open for voting.