​

Teams, routing, and categories

Teams and categories control how CXP routes live customer work to the right group of agents.

​

Prerequisites

You need an administrator, owner, or team-management role with permission to manage teams and routing settings.

​

How routing fits together

CXP routing uses several pieces of configuration:

• Teams group agents for ownership and routing.
• Categories classify what a conversation is about.
• Category mappings connect top-level categories to general teams.
• Routing policy decides how eligible agents receive work.
• Agent readiness determines who can receive live offers.

If a category cannot be mapped to a specific team, CXP falls back to the built-in All Agents team.

​

Team types

CXP includes a required All Agents team. This team represents the tenant-wide fallback pool and is system managed. Administrators can create general teams for operational groups such as Billing, Technical Support, or VIP Support. General teams can be mapped to top-level categories and can configure routing behavior.

​

Manage team membership

From the Teams workspace, open a team to manage:

• Team name and basic settings
• Active state
• Members
• Member routing eligibility
• Routing policy
• Category mappings
• Cascade routing, when enabled
• Team music settings for voice queues, when configured

Keep team membership aligned with the work the team should receive.

​

Configure routing policy

Team routing policy controls how CXP selects an eligible agent. Supported policies include:

• Round robin to rotate offers across eligible agents.
• Least loaded to prefer eligible agents with lower current load.

Only Ready agents who satisfy routing constraints should receive new offers.

​

Manage categories

Administrators manage category catalogs in the Categories workspace. A catalog can contain a hierarchy such as:

• Top-level category
• Subcategory
• Sub-subcategory

Categories help agents scan work, support reporting, and drive routing.

​

Map categories to teams

Map top-level categories to active general teams from team routing settings. When a conversation is categorized:

1. CXP identifies the top-level category.
2. CXP checks whether that category maps to an active general team.
3. If a mapping exists, the conversation routes to that team’s queue.
4. If no valid mapping exists, the conversation routes to All Agents.

Mapping changes apply to new routing requests. Work that is already queued normally keeps its current queue unless the target team is deleted or deactivated.

​

Configure cascade routing

Cascade routing can expand eligibility when work waits too long in a team queue. A general team can define stages such as:

• Start cascade after a configured delay.
• Add one or more extension teams.
• Include All Agents as a later fallback stage.

The conversation remains in its original queue while CXP expands the set of eligible agents according to the cascade schedule.

​

Operational checks

Before enabling a new routing setup:

1. Confirm agents are active and assigned to the intended teams.
2. Confirm agents can set themselves Ready.
3. Confirm category mappings cover the intended work.
4. Confirm unmapped work safely falls back to All Agents.
5. Test a live chat or voice offer before relying on the configuration in production.