My votes: Load balancing

Since chat and text are the busiest support channels, an option to set up rules so those conversations are auto-prioritized and routed to the most or first available agent would be great.

This proposal introduces a systematic approach to assign importance and difficulty levels with Load Balancing based on subject types. By implementing a weighted allocation system, we can better distribute workload, optimize resource utilization, a...

The option to have emails assigned to agents in order in SLA, for example a chat should have a low SLA, and should be assigned to agents at a higher level than an email with an SLA of 2 hours for example

When inboxes are "work queues" it makes sense to not overfill some work queues. Using load balancing between inboxes is a way of solving this.

Load balancing rule conditions are checked when a conversation *enters* the queue, but not when Front tries to assign. Ex: - Rule says "when inbound, if in inbox A, then assign load balance" - Conversation comes in inbox A, no teammate capacity, g...

Similar to what is offered to load balancing, round robin would not assign to teammates that have N open conversations already assigned.

Giving Admins the ability to set complex limits such as “assign up to 1 chat and up to 5 emails to this teammates"