A team is a collection of users in User Management. The team can be created manually on the Teams page (see Adding New Teamsfor more details), or it can be imported, along with its users, from an external database.
User teams can be arranged hierarchically, with one or more teams being a part of larger teams. Teams can be specifically used by the connected applications. For example, in Quality Management, teams are used to select multiple users for review in the Review Scheduler and to filter reports to display team performance. Users who can conduct reviews can also create reviews of agents in any team they have the right to review (see Assigning Managers to Teamsfor more details).
Teams in User Management share a common set of attributes and role mappings across their members. Users can belong to any combination of teams – or none at all – and inherit the attributes and role mappings of each team they are in.
Teams are hierarchical:
-
A team can have many subteams.
-
A team can only have one parent.
Subteams inherit the attributes and role mappings from the parent. If there is a parent team and a child team, and a user only belongs to the child team, the user inherits the attributes and role mappings of both the parent and child.
Agent Team Changes and Conversation Visibility
If an agent switches between teams, the previous supervisor can view conversations from before the team change, and the new supervisor can view conversations from after the team change.
However, if a conversation is updated after the team change – for example, a comment is added from the Call Recording UI or a tag is added from the Quality Management UI – the conversation becomes visible to the new supervisor, because the agent is assigned to that supervisor at the time of the update. The conversation is no longer visible to the previous supervisor.
Example: An agent works for Team A until the end of May and then moves to Team B from June 1. Supervisor A (Team A) can see all recorded conversations through the end of May. Supervisor B (Team B) can view only calls made from June 1. However, if a conversation from May is updated – for example, Supervisor A adds a tag during a routine review – it becomes visible to Supervisor B, because the agent is a member of Team B at the time of the update.
Conversations Involving Multiple Teams
If a user can view part of a conversation because it involved an agent from a team they have permission to view, they can view the whole conversation, including parts that involved agents from different teams.
Team Names Must Be Unique
The Quality Management database requires that each team name be unique. Duplicate team names are not allowed; duplicate teams are ignored during the import process.
-
This is relevant if two or more external systems are used, or if manual changes are made to names, and each system contains teams sharing a common name.
Example: if a team named SanFran is imported from UCCE1, it is imported properly and is visible in Quality Management. However, if an import is performed from a different system (or a team called SanFran is manually created in User Management), the new team is not imported and is not visible in Quality Management. -
Ensure that team names are unique, both across and within all systems.
Multi-Team Membership
-
Users – Quality Management does not support multi-team membership. A user can be assigned to only one (main) team.
-
Supervisors – An individual can supervise multiple teams.
Any changes to teams and team membership made in User Management are reflected in other Eleveo applications after a delay of up to 10 minutes.