> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Human routing: availability and capacity

> Set whether each agent can receive sessions and how many they handle at once, update capacity for everyone, and see how capacity drives team assignment.

Human routing decides which agent gets a session that is waiting for a person. Here you set whether each agent can receive sessions and how many open sessions they handle at once.

> [!NOTE]
>
> **Settings → Human Routing** in your [OpenCX dashboard](https://platform.open.cx/settings/agent-assignment). The page is titled **Agent assignment**. Viewing it requires the **Members** or **Agent availability & capacity** permission; changing availability and capacity requires write access to either one.

## Set an agent's availability and capacity

The **Agent availability** table lists every agent with their current status. Search by name or email. The table refreshes every 30 seconds.

| Column | What it does |
| - | - |
| **Availability** | The agent's main availability switch, the same one agents use in their own menu. Off means the agent receives no automatic assignments. |
| **Capacity** | The most open sessions the agent can be assigned at once, across all teams. Saves shortly after you stop typing. |

New members start **Offline** with a capacity of 5. Changing an agent's availability here clears any [availability status](https://docs.open.cx/ticketing/availability-statuses.md) they picked, and their status shows as Online or Offline again.

## Update capacity for all agents

**1. Open the dialog**

Click **Update all…** above the table.

**2. Enter the capacity**

Under **Global capacity**, enter a number from 0 to 1,000,000.

**3. Save**

Click **Save**. Every agent in the workspace gets this capacity. Per-team capacity set in [Teams](https://docs.open.cx/teams.md#team-editor-settings) is not changed.

## What counts toward capacity

* Open sessions assigned to the agent count.
* Snoozed sessions do not count while they are snoozed.
* Sessions released with the **Release Session From Capacity** workflow action do not count until the customer sends a new message.
* Capacity only limits automatic assignment. You can still assign a session to an agent by hand when they are full.
* Chat capacity does not stop an agent from receiving phone calls. See [Human calling](https://docs.open.cx/phone/human-calling.md).

## How capacity works with team assignment

Sessions reach a team through a workflow such as **Assign Ticket to Support Team**, a teammate changing the team in the Inbox, an integration, or the API. What happens next depends on the team's **Support Assignment Strategy** in [Teams](https://docs.open.cx/teams.md#team-editor-settings).

> [tab] Least busy
>
> OpenCX assigns the session to an eligible team member. A member is eligible when all of these are true:
>
> * Their **Availability** is on.
> * They are **Available** in that team.
> * They have free capacity.
> * The team is within its office hours.
>
> Among eligible members, the one with the most free capacity gets the session. If several tie, OpenCX prefers the member with fewer snoozed or released sessions, then picks at random.

> [tab] Unassigned
>
> Sessions wait in the team, unassigned, until a teammate picks one up or someone assigns it. Availability and capacity are not used.

A team can also set its own capacity per member in the team's **Members** tab. The member's limit in that team is the lower of the team capacity and their global capacity, and it counts only that team's sessions. Free capacity is the smaller of what is left globally and what is left in the team.

For example, an agent has a global capacity of 5 and a capacity of 2 in the Billing team. They have three open sessions in other teams and one in Billing. Globally they have 1 slot left, and in Billing they have 1 slot left, so Billing can assign them one more session.

When nobody is eligible, the session waits in the team. OpenCX checks every support-enabled team's waiting sessions about once a minute, and also right away when an agent comes online, becomes available in a team, or a session in the team closes. Waiting sessions are served in the team's [session assignment order](https://docs.open.cx/teams.md#choose-session-assignment-order).

> [!NOTE]
>
> Turning an agent's availability off does not take away the sessions they already have. It only stops new automatic assignments.

## Auto-assign on handoff

Each channel's settings under [Settings → Autopilot](https://platform.open.cx/settings/autopilot) include **Auto-Assign on Handoff**, which is on by default. When the AI hands off a session, it assigns it to an available agent anywhere in the workspace, not within a particular team. It is not used when Zendesk or Salesforce handles your handoffs. If a workflow then moves the session to a team, the agent keeps it only if they belong to that team; otherwise the team assigns it as described above.

## Calendar integration

**Calendar integration** is in early access. It marks agents unavailable during their calendar events. The **Google Calendar** and **Microsoft Calendar** switches stay disabled until your workspace is enrolled; hover a switch to see the support address to contact.

## Troubleshooting

| Symptom | Likely cause | Fix |
| - | - | - |
| Sessions wait in a team while agents are online | The team uses **Unassigned**, it is outside the team's office hours, members are unavailable in that team, or everyone is at capacity. | Check the team in [Teams](https://docs.open.cx/teams.md#team-editor-settings), then raise **Capacity** here. |
| An agent never gets sessions | Their capacity is 0, or they are not **Available** in any team. | Set a capacity above 0 and make them available in their teams. |
| **Update all…** is missing and the switches are disabled | Your role can view this page but not change it. | Ask an admin for write access to **Members** or **Agent availability & capacity**. |
| None of the above | | Contact OpenCX support with the session link and the team name. |

***

## Related Documentation

> [card] [Availability statuses](https://docs.open.cx/ticketing/availability-statuses.md)
>
> Statuses agents pick to go online or offline

> [card] [Teams](https://docs.open.cx/teams.md)
>
> Assignment strategy, pacing and team capacity

> [card] [Skills](https://docs.open.cx/ticketing/skills.md)
>
> Route sessions by expertise

> [card] [Office hours](https://docs.open.cx/ticketing/office-hours.md)
>
> When teams accept new assignments


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.