Overview
The Agents and Teams section is where you organize the people whose conversations Ender Turing analyzes. An agent represents one contact center representative; a team is a group of agents that usually work in the same department (for example, Customer Support or Telesales). Each team has one scorecard and an optional hourly rate; the team rate applies to every agent in the team unless an individual agent has their own Rate/hr override (see "Agents in a team" below).
An agent profile is separate from an Ender Turing user account. The agent profile is what the platform attaches conversations to (using a phone number or other extension ID), while a user account is what a person uses to log in. You can optionally link an agent to a user so that when that user opens their workspace, they see only their own conversations.
How It Works
Accessing Agents and Teams
Open Settings from the main navigation.
Select Users & Agents.
Switch to the Agents and Teams tab.
The page opens on the team list. Selecting a team takes you to its member list.
Teams
The Teams view lists every team in your organization. For each team you see:
Name
Members — the number of agents currently in the team
Scorecard — the scorecard that applies to scoring this team's conversations
Rate/hr — the hourly cost used in cost-based analytics (or "Default Rate" when not set)
One team is always marked as the Default Team. Agents that are created automatically — for example, from incoming audio files with new phone numbers — are placed into the default team. The default team itself cannot be deleted.
Create a team
Click Create a team in the top bar.
Enter a Team Name.
Pick a scorecard from the dropdown. (A scorecard must already exist; if none does, you'll be prompted to create one first.)
Optionally set a Rate/hr for the team. Leaving it empty falls back to the organization's global rate.
Optionally tick Set as default team to make this the default.
Save.
Rename, change scorecard, or change rate
Click the pencil icon on any team row to edit its name, scorecard, default flag, and rate.
Delete a team
Delete is available only when the team has no members and is not the default. To clear a team for deletion, move its agents to another team first. Teams that still have conversation history attached to them cannot be deleted either — if the delete call fails after you've moved the agents out, it's because past sessions are still linked to the team.
Sync with CRM
If a CRM connector is active for your organization, a Sync with CRM button appears in the top bar. Use it to pull team and agent definitions from your connected CRM into Ender Turing. The sync runs in the background; existing data stays in place until the sync completes.
Agents in a team
Click a team's name (or the members count) to open its Members view. The list shows all agents currently in that team with:
Full Name
Phone number — the primary identifier the system matches conversations against. If the agent has alternative numbers, a small "+N" chip appears next to the main number; hover it to see the aliases.
Email — the email of the linked user, if any
Team — the current team (the field is shown so you can move the agent here from another team during editing)
Rate/hr — per-agent hourly rate, falling back to the team's rate, then to the global rate
Active — the agent's status switch
A search box above the list filters by name, phone number, alias, or linked-user email. The status selector on the right narrows the list to active agents, deactivated agents, or both.
Create an agent
Click Create Agent in the top bar.
Fill in Agent name and Agent phone number. Both are required.
Optionally pick the agent's Team if you want to create them in a team other than the one you're viewing.
Optionally type an email in the Agent email field. The dropdown suggests users who already have either the Agent or Agent with Team Dashboards role and aren't yet linked to another agent, with two caveats:
Suggestions permission — the dropdown calls the shared user-suggestions endpoint, which is gated on Sessions comment, Sessions comment (own), Trainings view, Scheduled Chats manage, or EnderGPT Chats view (own). A custom settings admin whose role has only Agents manage and Manage Users has none of those, and the dropdown will stay empty for them — link existing users from the Manage Users tab instead, or grant one of the listed permissions to the role.
Agent-only users hidden — even when the suggestions endpoint is accessible, users whose roles are limited to the Agent role family (Agent, Agent with Team Dashboards, or both) are filtered out unless your role also grants Scheduled Chats manage, so most settings admins will only see Agent-role users that also carry a second role (for example, Manager + Agent).
You can:
Pick an existing user from the dropdown to link them to this agent.
Type a new email — when you save, Ender Turing creates a new user with the agent role and sends them an invitation email. This invitation step requires the Manage Users permission in addition to Agents manage; without it the agent profile is saved but the user-creation call is rejected.
If the person you want already has an Ender Turing account but isn't in the dropdown (because their roles are limited to the Agent role family, or because their role is something else entirely such as Manager or Supervisor), do not type their email here — an email that already belongs to a user is rejected with a duplicate-user error. The agent profile itself is saved first and is not rolled back when the user-creation step fails, so you'll be left with an unlinked agent record and an error notification about the duplicate user. Instead, open the Manage Users tab, edit that user, ensure they have the appropriate Agent role if needed, and set the agent profile to link from there. If you've already hit the duplicate-user error, edit the orphan agent from the team view to clear the email field or link it to the right user.
Optionally open the Alternative Numbers dialog to add other phone numbers or extensions that the same person uses.
Save.
Active agents must have a unique phone number. You cannot create or activate a second active agent with the same number — but a deactivated agent can keep an old number for history (see "Replace a staff member" below).
Edit an agent
Click the pencil icon on a row. From the edit form you can change name, phone number, alternative numbers, linked user, team, and rate.
Saving an edit never changes whether the agent is active. The Active switch is not part of the edit form, and if the agent is deactivated while its edit form is still open (for example, through Deactivate agent in the multi-select toolbar), saving the form keeps the agent and its linked user deactivated. To turn access back on, use the Active switch described in "Deactivate or reactivate an agent" below.
When you change an agent's team, a Confirm team change dialog appears with two options:
Leave existing calls in the previous team — only new conversations are attributed to the new team.
Also move existing calls to the new team — historical conversations are re-attributed to the new team as well.
The first option is the default in most cases. When the source team is the Default Team (for example, when you are moving auto-created agents into a real team), the "Also move existing calls" option is pre-checked instead, so historical conversations follow the agent unless you uncheck it.
The same two options are offered for the bulk move action described below.
Move agents in bulk
Tick the checkboxes next to the agents you want to move.
In the multi-select toolbar, pick a destination team from the dropdown.
Click Move and choose how to handle existing calls in the same confirmation dialog as the single-agent flow.
Deactivate or reactivate an agent
Use the Active switch on the agent's row. A confirmation dialog (Deactivate agent or Activate agent) appears. Editing an agent or moving it to another team leaves its status unchanged. Deactivating an agent has two main effects:
Audio/file pipeline — new recordings that match a deactivated agent's phone number are skipped entirely (the file is removed from the inbound queue); reassign the number to the new hire by following the "Replace a staff member" pattern below.
Linked user — because each agent profile can be linked to one user account, deactivating an agent also deactivates the linked user (except for superusers and the built-in system user, which are not affected).
The same skip applies to chat and email sessions uploaded through the integrations API: an inbound upload attributed to a deactivated agent profile is skipped, and no conversation is created. Reassign the chat handle by retiring the old agent first (rename it with a suffix such as _old per the "Replace a staff member" steps) so new uploads attach to the active replacement profile.
You can deactivate many agents at once by selecting them and clicking Deactivate agent in the multi-select toolbar.
Replace a staff member (agent rotation)
When a phone extension is reassigned to a new hire, simply renaming the old agent would mix the previous person's history into the new agent's analytics. The recommended pattern is:
Deactivate the old agent so they drop out of active dashboards.
Edit the phone number of the deactivated agent — add a suffix such as
_oldor_archived. This frees the original number for the new person while preserving the link between the deactivated profile and past conversations.Leave the deactivated agent in their original team so historical reports for that team stay accurate.
When the new employee makes their first call with the freed-up number, Ender Turing creates a fresh agent automatically in the Default Team. Move that new entry into the right team and set the proper name.
Delete agents
To delete agents, select them with the checkboxes and click Delete. Deleting an agent is destructive — past conversations attributed to that profile lose their agent link. Use deactivate instead of delete whenever you want to preserve history.
Alternative numbers
A single human agent may receive calls or chats through more than one identifier (different extensions, a softphone ID, a chat handle, and so on). To make sure all of those land on the same agent profile, open the agent in edit mode and click the + button next to the phone number field. The Alternative Numbers dialog lets you add, edit, and remove additional numbers. The primary phone number must still be unique among active agents; aliases follow the same rule.
Merge duplicate agents
When two agent records turn out to be the same person — for example, one created from your call platform and one from chat — you can merge them into a single profile. The unified profile keeps all historical data; one identifier becomes the main number and the other is stored as an alias.
To merge:
In the team view, tick the checkboxes next to exactly two agents.
Click Merge in the multi-select toolbar.
In the Merge Agents dialog, review both records side by side. Choose which agent stays as the main one by ticking Keep agent on that card.
Read the resulting preview (name, primary phone, aliases, linked user).
Click Confirm Merge. You will be asked to type "merge" to confirm, because the operation cannot be undone.
Reload the tab afterwards so charts and filters pick up the unified profile.
Two agents can only be merged when:
Both belong to the same team.
They have either the same linked user or no linked-user conflict (one without a user, one with a user). If both have different linked users, unlink one first.
If one of the two source agents is inactive, the merged agent will also be inactive — the dialog warns you before you confirm.
Linking agents to users
Linking an agent to a user is what powers the My Dashboard and Agent's Workspace experiences: a logged-in user with a linked agent profile sees their own conversations, scorings, and trainings.
You can manage the link from either side:
From the Agents list, set or change the linked user via the Email field on the agent's edit form. Typing a new email creates an invited user with the agent role.
From the Manage Users tab, edit a user and pick an agent profile to link.
A user can be linked to one agent profile at a time. Once linked, the user is treated as part of that agent's team for permission scoping.
Agent summary
Each agent has a summary page with their results. Open it by clicking the agent's name — or the chart icon at the start of the row's actions — in a team's Members view. Agent names in a conversation's header and in dashboard scoring tables link to the same page when your role can view agents.
The agent's name appears in the top bar, and the page has three tabs:
Agent dashboard — the agent's scoring results, opened by default.
Reviewed and Commented — the agent's conversations that were scored or commented on. The Reviewed by column lists the reviewers and, when a conversation has more than one score, how many scores it has — every submitted score counts, including several Auto QA scorecards or repeat scores from one reviewer.
Trainings — the agent's trainings. The tab is always listed, but opening it needs the trainings view permission (see Access and Permissions).
On Agent dashboard, set the period and other filters in the top bar. The summary cards (conversation counts, average scores, and duration distribution) cover the agent across all teams. The team selector under the tabs applies only to the scoring tables and to Go to calls, which opens the agent's conversations for the selected team. Each scorecard used for the agent gets its own table, headed **Scoring by {scorecard} - {period}, with an Overall bar and one column per category. Click a category's column header to see its individual points, and Back to categories to return. The person icon and robot icon in the table header switch between manual and automated scores. If your own user is linked to an agent and Allow agents to see automated scoring and feedback** is turned off in General Settings, the icons are hidden and only manual scores are shown, including on other agents' summaries.
Download an agent's scoring table
Each scoring table has a download button in its header. The menu offers:
Option | What you get |
Image (.png) | A picture of the table as it is shown on screen |
Excel (.xlsx), Excel (.csv), Text (.txt) | The table's values as a file |
Detailed XLS (Categories) | One row per review, with scores grouped by category, plus the reviewer, comments, the conversation summary, and its topics. A conversation scored by several reviewers appears once per review |
Detailed XLS (Points) | The same, with scores for each individual point |
The file and text exports follow what the table currently shows: the selected agent and team, the scorecard, the manual or automated score mode, the filters in the top bar, and — if you have opened a category — that category's points. The two detailed exports ignore the opened category: Detailed XLS (Categories) has a column for every category in the scorecard, while Detailed XLS (Points) has columns only for points that were scored in the exported reviews. All downloads start straight away.
The download button appears only on the agent summary page opened from Agents and Teams or from a link to it. Agents viewing their own results in My Dashboard do not get it.
Access and Permissions
Who sees what depends on the permissions assigned to the user's role. The table below describes the user-visible behavior on the Agents and Teams tab.
Action | Required permission |
Open the Agents and Teams tab | Agents view (or higher) and a Teams view permission — the tab loads the team list on open, so without any Teams view scope the page renders empty or errors |
See every team in the organization | Teams view |
See only your own teams | Teams view (own scope) — applies to users linked to an agent |
Create, rename, or delete a team | Teams manage |
Change a team's scorecard or rate | Teams manage |
Create an agent (without inviting a new user) | Agents manage |
Create an agent and invite a new linked user from the email field | Agents manage and Manage Users — the user-creation call is gated by Manage Users, so without it the agent saves but the invitation step is rejected |
Edit or delete an agent | Agents manage (or Teams manage) |
Move agents between teams (single or bulk) | Agents manage (or Teams manage) |
Merge agents | Agents manage (or Teams manage) |
Activate or deactivate an agent | Manage Users and Agents manage (or Teams manage) — the Manage Users permission is required because the linked user is also (de)activated, and the agent update endpoint additionally requires the agent/team manage permission |
Sync with CRM | Teams manage, and a CRM connector must be active |
Open an agent's summary | Agents view, Agents view (team scope), or Agents manage, and a Teams view permission (any scope) or Teams manage — the page loads the team and scorecard lists on open, so without a Teams permission it does not load. Teams view (own scope) lists only your own teams, so it works only for agents in one of those teams. Likewise, Agents view (team scope) opens only the summaries of agents in your own teams; to open any agent's summary, use Agents view or Agents manage |
See and download the scoring tables on Agent dashboard | Additionally, Dashboard View, Dashboard View Team, Dashboard View Agent, or View Own Sessions — without one of these, the tables do not load. Dashboard View Team shows results only for your own teams, and Dashboard View Agent or View Own Sessions only for the agent linked to your own user; other agents' tables stay empty |
Open the Reviewed and Commented tab of an agent's summary | Additionally, a Conversation view permission (any scope) — without it, the list does not load. With team or own scope, the list shows only conversations from your own teams or of the agent linked to your own user |
Use Go to calls on Agent dashboard | Additionally, a Conversation view permission — without it, the button opens an access-denied page |
Open the Trainings tab of an agent's summary | Additionally, Trainings view. Trainings view (own scope) works only on the summary of the agent linked to your own user; Trainings view (team scope) does not open the tab |
Open an agent's summary without a permission notification | Additionally, Trainings manage, because the page loads the training list on open. If the agent is linked to a user, also Trainings view or Trainings view (team scope); on the summary of the agent linked to your own user, Trainings view (own scope) is enough. Without these, the summary still opens and works, but shows "You don't have permission to perform this action" |
Roles are configured under Settings → Users & Agents → Roles & Permissions. To restrict a user to specific teams only — for example, an external QA partner — set their role so that Conversation permissions are granted under the Teams scope and the All scope is empty, then pick the allowed teams on the user's edit page.
Read-only viewers
A user with only view permissions on Agents and Teams can open the Agents and Teams tab, browse the team list, open team members, and inspect agent details, but the Create, edit, delete, move, merge, and CRM-sync controls are hidden.
Limits and Caveats
An agent belongs to one team at a time, but team membership has history: the previous team is preserved on the agent's record and used when re-attributing historical conversations.
A team has one scorecard at a time. (On systems with scorecard variation enabled, a three-dot menu button inside the Scorecard chip on the team row opens a dialog where you can define backup scorecards triggered by conversation filters. Clicking the chip body itself navigates to scorecard editing instead, if your role has scorecard-manage.)
The active agent's primary number and each alias must be unique across active agents. Deactivated agents may keep numbers that overlap.
The system user (ID 0) cannot be modified.
Sync with CRM and bulk merges run asynchronously in the background; refresh the page if results don't appear immediately.
