Skip to main content

Work Teams

Navigation: Admin → Directory → Work Teams Also accessible via: Menu → User Management → Work Teams


What Are Work Teams?

Work teams are supervisor-managed groups of agents used to monitor performance and manage workforce operations collectively. They are distinct from Groups (People & Permissions) in purpose and behaviour.


Work Teams vs. Groups — Key Differences

FeatureWork TeamsGeneral Groups
Primary purposePerformance management & WFMRouting, chat, role assignment
Membership ruleOne team per division per userUsers can belong to multiple groups
Division requirementAll members must share same divisionMembers can span divisions
Chat room createdNoYes (automatic)
Role assignmentNoYes
Queue membershipYes (add team to queue)Yes (add group to queue)
Schedule managementYes (WFM schedules)No
Automatic membershipNo (manual only)Yes (rule-based or skill expression)

Org Limits

ItemLimit
Work teams per org200 (contact Customer Care to increase)
Work teams per user1 per division
Division requirementAll members must belong to the team's assigned division

Creating a Work Team

  1. Click Admin
  2. Under Directory, click Work Teams
  3. Click New Team
  4. Fill in the required fields:
FieldNotes
NameAppears in views and lists
DescriptionPurpose/context for the team
DivisionAll members must belong to this division
  1. Add members — you can only add users from divisions where you have the Assign permission
  2. Save

Adding a Work Team to a Queue

Work teams can be assigned to queues in place of individual users.

⚠️ Mutually exclusive: You cannot mix individual users and a work team on the same queue. If you switch from users to a work team, the previously selected individual users are removed.

Steps:

  1. Admin → Contact Center → Queues → select queue
  2. Click the Members tab → Groups tab
  3. Click Add Group → search for and select the work team
  4. Click Add Selected → Save

What Supervisors Can Do with Work Teams

Work teams enable the following supervisor capabilities:

Performance Monitoring

  • Filter Agent Performance / Detail views by work team
  • Filter Agent Status view by work team
  • Filter Agent Evaluation view by work team
  • Filter Queue Performance Detail by work team

Workforce Management

  • View and edit WFM schedules by work team
  • Schedule activities for an entire work team at once
  • Filter Real-time Adherence by work team
  • Assign quality policies to a work team

Audit & Tracking

  • Work team membership appears on the People page
  • Changes to work team membership are recorded in the audit trail

Permissions Required

ActionPermission
Create / manage work teamsGroups > Work Team > Add, Edit, Delete
Add members from a divisionGroups > Work Team > Assign (for that division)
View work teams in WFM schedulesGroups > Work Team > View (non-conditional = all teams in management unit)

ℹ️ If you have no Work Team permissions at all, the work team selector does not appear in WFM schedule views.


Relationship to Divisions

  • When creating a work team, the division controls which users are eligible for membership
  • A supervisor can only add users from divisions where they have the Assign permission
  • Users can belong to one work team per division — so a user in multiple divisions could technically be in one work team in each

Relationship to WFM Business Units and Management Units

Work teams operate within the WFM scheduling hierarchy:

Business Unit
  └── Management Unit(s)
        └── Work Teams (filter / schedule view layer)

Work teams are not the same as management units. Management units group agents for forecasting and scheduling capacity (max 1,500 agents). Work teams are a supervisory filter and scheduling activity tool layered on top.


See Also

  • Groups (People & Permissions) — for routing, role assignment, and chat rooms
  • Queue & Routing Management — for assigning work teams to queues
  • Divisions & Access Control — division membership rules affect work team eligibility
  • Architectural Build Order — work teams are built in Phase 3 (People), after users and before queues