Automatically balance your team’s workload with load balancing rules
Teams handling high message volume can automatically distribute work amongst teammates with the load balancing feature. That way, customers get the quickest responses, and each teammate has a set limit so they don’t get overwhelmed.
Load balancing is a specific type of auto-assignment rule available on the Pro plan and allows you to set assignment limits for each teammate. Load balancing rules automatically assign inbound conversations to the teammate with the fewest open assigned team conversations until they reach their limit. During busy times when all teammates have reached their load balance limits, load balancing rules will will automatically pause and resume assigning as teammates have bandwidth.
How it works
Load balancing option in assignment rule action
Load balancing is an alternative to using round-robin or random group assignment rules. Load balancing rules will automatically assign conversations to the teammate in the group who has the fewest open assigned team conversations. Load balance assigning runs once every minute.
Set assignment limits for each teammate
There will be a Load Balancing tab in each Team’s rule settings where admins can set assignment limits for auto-assignment rules. If all teammates are at their limit, assignment rules will pause assigning and resume when a teammate in the group is below their limit again.
Click into Settings and Rules under the Team section. You must be a team admin to set up load balancing rules and limits.
Click into the Load Balancing tab to set up the limits for your teammates.
Click Add assignment limit.
Choose the assignment limit and select the teammates that this limit should apply to. Click Save.
Click back to the All Rules tab of the settings and click Add a team rule.
Set up your rule conditions. Under the Then section at the bottom, add the action Assign in group, choose [PRO] Load balancing and select the teammates who should receive assignments under this rule. These teammates will be capped at the conversation limit that you set in the load balancing settings.
Helpful to know
- If a user is a member of multiple Teams, their load balance limits are specific to each Team. Example: Joe is a member of Team A with limit of 10 and Team B with limit of 8. During a busy time for both Teams, he could have up to 18 conversations assigned to him at any time (10 from Team A and 8 from Team B).
- Private conversations do not count against the work balance limit, since they are not in a Team space.
- If you are at the limit, the rule engine will stop assigning to you, but a teammate can manually still assign to you.
- Load balancing applies only to the Load balancing option in the rule action, not other assignment rule types. In other words, assignment rules that are Assign to teammate, Assign randomly, and Assign round-robin do not fall within the load balancing limit.
- We recommend that you only have one Assign in group rule to avoid confusion, as rules can only assign conversations that are not already assigned. In other words, the earliest assignment rule will trigger but subsequent ones won’t work to re-assign these conversations.
- You can set up to a limit of 100 conversations per teammate.
- If you use the Assign in group load balancing action in a rule but do not set any load balance limits for teammates, then the load balancing rule will still assign to teammates with the least number of assigned conversations first. The difference in this case is that the assigning will continue without a cap.
- If everyone is at capacity, Front will not assign more conversations and will pause. If any teammate goes below capacity, then Front will start assigning again from the oldest conversation being assigned to the teammate with the least amount of assigned conversation. There is logic in place such that once there is a queue of conversations, Front’s rule engine will ping each minute to check teammate capacity. If anyone has capacity, Front’s will engine will assign until everyone is at capacity again. If the rule engine checks and no teammate has capacity, the clock will extend checks overtime to be less frequent - up to 15 min. Once assignments resume that clock resets to 1 min polling checks.