Assignment methods at a glance
Manual
Balanced
Round Robin
Manual assignment
With manual assignment, new tickets land in the shared inbox and wait for a teammate to pick them up or for a manager to assign them directly. This is the default strategy for new teams. Best for:- Small teams where agents self-select work
- Specialized tickets that require specific expertise
- Low-volume inboxes that don’t need automation
Balanced assignment
Balanced assignment automatically routes each incoming ticket to the available agent with the lowest number of open tickets. In the team settings it reads “go to the team member with the fewest open tickets.” This keeps workloads even across your team, so no single agent gets overwhelmed while others sit idle. Balanced only counts each agent’s open tickets in this team. An agent with 8 open tickets on a “Billing” team and 2 on a “Tier 2” team counts as having 2 when Tier 2 assigns a ticket.How it works
- A new ticket arrives in the Helpdesk.
- The system finds all agents whose status is Available.
- If a max ticket limit is configured, agents who have reached that limit are excluded.
- The ticket is assigned to the agent with the fewest open tickets. Which statuses count as open is set per team; see Agent workload.
- If multiple agents are tied, the one who was least recently assigned a ticket receives it.
Round robin assignment
Round robin distributes tickets sequentially by assigning each new ticket to the available agent who was least recently assigned, regardless of how many tickets they currently have open. It’s a good fit for sales and lead distribution where equal opportunity matters more than current workload.How it works
- A new ticket arrives in the Helpdesk.
- The system finds all agents whose status is Available.
- If a max ticket limit is configured, agents who have reached that limit are excluded.
- The ticket is assigned to the agent with the oldest last-assignment timestamp, the teammate who has waited longest for a new ticket.
Comparison
Unassigned tickets
When no agents are available or all agents have reached their ticket limit at the moment a ticket is created, the ticket stays in the shared inbox as unassigned. It isn’t stuck there: on Balanced and Round Robin teams, Chatbase picks up waiting tickets again when something changes in the team.When waiting tickets are picked up
Chatbase looks for unassigned tickets that have a New status and belong to a Balanced or Round Robin team, and runs the team’s strategy on them. It runs when:- an agent’s status is set to Available
- a member is added to the team
- the team’s settings are saved
- a shift is edited or deleted, or an agent is put on a shift
- time off is added or removed
- a ticket is moved to the team
- an agent’s workload drops below the team’s max tickets per agent
Unassign on reply
Turn this on in the team’s settings. A customer reply then gives the ticket another chance at assignment:- If the ticket is already unassigned, assignment runs again.
- If the ticket is assigned and that agent is still available, nothing changes.
- If the ticket is assigned and that agent is no longer available, the agent is unassigned and assignment runs again.
- On a Manual team, the agent is only unassigned. There is no auto-assignment to run, so the ticket goes back into the team’s pool for someone to claim.
- The ticket keeps its existing team.
- The same max tickets per agent limit and Assign to next available shift setting apply, just as they do when the ticket is first created.
- Closed and Cancelled tickets are skipped.
When all agents are unavailable
If every agent is set to Away, Busy, or Paused at the moment a ticket is created, the auto-assignment algorithms (balanced and round robin) cannot find an eligible agent. Here’s what happens:- Incoming tickets stay unassigned in the shared inbox with a New status, in the Unassigned view.
- When an agent is set back to Available, the team’s waiting tickets are picked up, highest priority first. See When waiting tickets are picked up.
- A teammate can claim a ticket, or a manager can assign one, at any time.
Assign to next available shift
When every agent is unavailable and you use Balanced or Round Robin assignment, you can enable Assign to next available shift so that incoming tickets are automatically routed to an agent whose shift starts soonest, instead of staying unassigned.How it works
- A new ticket arrives and the system finds no available agents (all are
Off shift,Away,Busy, orPaused). - The system looks at all scheduled agents and calculates when each agent’s next shift begins, skipping any agents who are on time off.
- The ticket is assigned to the agent (or agents, if tied) whose shift starts the earliest.
- The chosen agent is selected using the same algorithm you configured. Balanced picks the one with the fewest open tickets, Round Robin picks the one least recently assigned.
Enabling the toggle
Open the team
Choose an auto-assignment method
Enable the toggle
Things to know
- Max ticket limits still apply. If you have a max tickets per agent configured, the next-shift agent must also be under that limit to receive the ticket.
- Time off is respected. Agents on time off are skipped even if their shift is the soonest.
- Multiple agents on the same shift. When several agents share the same next shift start time, the configured assignment algorithm (Balanced or Round Robin) breaks the tie.
- No scheduled agents? If your team has no scheduled agents, this toggle has no effect since there are no shift start times to predict.
Max tickets per agent
For both automated methods (balanced and round robin), each team can optionally set a maximum number of open tickets per agent. When an agent reaches this limit, they stop receiving new assignments until their workload drops below it, for example by closing tickets.- Default: No limit
- Maximum: 1,000,000
- Scope: Set per team, alongside the assignment strategy
- What counts: See Agent workload. By default, every ticket that isn’t Closed or Cancelled counts.
Open the team
Set the cap
Agent workload
An agent’s workload is the number of their tickets that count toward the team’s max tickets per agent. Balanced assignment also uses it to find the agent with the fewest open tickets. Each team chooses whether tickets waiting on someone else are included:Open the team
Open the workload settings
Choose the statuses
Save the team

Agent availability
Only agents with an Available status are eligible for automatic assignment. For agents who aren’t on a shift schedule, you set this status yourself from the Members page (Settings → Helpdesk → Members), where every agent is listed with their teams and availability. A scheduled agent’s status comes from their shift instead, so the Members page shows it as read-only, with the tooltip “Status is managed by the schedule” and the shift’s name.Setting up assignment
Open the team
Choose an assignment method
Configure ticket limits (optional)
Set agent availability
Good to know
- New agents default to Away. When an agent is first added to an AI agent, their status is set to Away. They will not receive auto-assigned tickets until an admin or the agent themselves switches to Available.
- Ticket limits only apply to auto-assignment. The max tickets per agent setting does not restrict manual assignment. An admin can still assign tickets to an agent who has exceeded the configured limit.
- Reassignment does not change ticket status. When a ticket is reassigned from one agent to another, the ticket’s status remains unchanged. It does not reset to New or On You automatically.
- The Away toggle only switches between Away and Available. Paused agents and agents on a shift schedule do not get this toggle in the sidebar. An admin can change a paused agent’s status from the Settings → Helpdesk → Members page. A scheduled agent’s status follows their shift instead.
- Agents are notified in the Helpdesk only. When a ticket is assigned to you, by a teammate or automatically, the Helpdesk plays a sound and, if the tab is in the background, adds an unread count to the tab title. Turn the sound off with Sound notifications in the sidebar user menu. There is no built-in email or push notice. To email agents, create a trigger with a Send email action to the Assignee.
- Takeovers skip assignment. A ticket created by a takeover is assigned to the teammate who took over.
- Live chat handoffs follow the same rules. Tickets from the Chatbase Live Chat Action go through your triggers and then the team’s strategy, availability, max tickets and next-shift settings, like any other ticket. The handoff happens even when no agent is available.
Frequently asked questions
Do unassigned tickets get assigned when an agent comes back online?
Do unassigned tickets get assigned when an agent comes back online?
Does Balanced count an agent's tickets across all teams?
Does Balanced count an agent's tickets across all teams?
Does ticket priority change who gets a ticket?
Does ticket priority change who gets a ticket?
How do agents know a ticket was assigned to them?
How do agents know a ticket was assigned to them?
Can I assign more tickets than the max tickets per agent?
Can I assign more tickets than the max tickets per agent?
Why are new tickets sitting unassigned in the default team?
Why are new tickets sitting unassigned in the default team?