Intercom assignment methods: test balanced, round-robin and manual ownership

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Match the method to the queue

Intercom distinguishes balanced assignment, round robin and manual assignment. Its documentation describes balanced assignment as distributing conversations to active teammates with the fewest open conversations while respecting assignment limits, round robin as sequential distribution that does not account for teammate assignment limits, and manual assignment as leaving individual pickup to the team unless another rule assigns the conversation.

Turn those mechanics into an operating choice

A support queue usually needs capacity awareness and priority handling. A sales enquiry queue may prefer sequential distribution. A low-volume specialist inbox may stay manual if an explicit duty owner reviews it. These are proposed operating choices; availability can depend on the workspace plan, so confirm the exact settings available before designing around them.

A synthetic capacity trial

Create a test team with two available teammates and no live customer traffic. Prepare five synthetic conversations: two normal, one urgent, one specialist request and one conversation that should remain in a team queue. Record the intended order and owner before changing the assignment method.

1. Set documented teammate limits and note each starting open-conversation count.
2. Submit the normal and urgent conversations and record assignment order.
3. Bring one teammate to the configured limit, then submit another eligible conversation.
4. Mark a teammate unavailable and verify the next eligible owner.
5. Repeat under round robin and record where the outcome intentionally differs.

Do not confuse fairness with capacity

Sequential distribution can look fair by count while giving complex work to someone already overloaded. Capacity-aware distribution can still be unfair if every conversation is treated as equally demanding. If the workspace supports inbox and teammate limits, document how specialist queues and individual limits interact. Do not promise a service level from assignment settings alone.

Define the unassigned state

Every method needs an owner for conversations that cannot be assigned. Name the role that reviews the queue, the review frequency and the escalation condition. An unassigned conversation is a valid state only if the team has a procedure for leaving it there.

Review outcomes after launch

Compare time to first ownership, reassignments, conversations at limit and queue age by inbox. Intercom provides workload and team performance views, but a dashboard should be interpreted with the routing policy. Investigate outliers and repeat the synthetic trial after changing priority, limits or team membership.