Roles in Call: Agent, Supervisor, Admin and Owner Explained
What each role in a call-centre system should be able to do, how Call maps agents, managers, admins and owners, and how to give people only the access they need.
A phone system holds a lot of sensitive material: recordings, transcripts, customer details, billing information and the settings that decide where every call goes. Not everyone needs all of it. A new agent answering calls does not need to change the opening hours, and a supervisor reviewing quality does not need to manage billing. Roles are how you encode those differences.

This guide explains the usual four levels in a call team, how they map to Call, and how to set up access so that people have what they need and no more. It pairs with two-factor sign-in and switching between workspaces.
Why roles matter
Roles protect against three kinds of problem. Mistakes: an agent who changes a routing rule by accident can send every call to nowhere. Misuse: a person with more access than they need may look at data out of curiosity. And loss: when someone leaves, fewer powers means less to take back.
There is also a morale benefit that is easy to miss. A clear structure tells people what is expected of them and who to ask. In a small team, "who can change that?" has a quick answer.
The four levels in a call team
Most contact centres end up with four layers, whatever the software calls them. The names vary; the jobs are stable.
| Level | Typical job | Typical powers |
|---|---|---|
| Agent | Takes and makes calls, handles messages and bookings | Works their own queue, contacts and conversations |
| Supervisor | Watches the floor, coaches, handles escalations | Sees team activity, listens to calls, manages queues and schedules |
| Admin | Sets up the system and the team | Adds and removes people, changes settings and routing |
| Owner | Is accountable for the organisation | Is accountable for the organisation as a whole |
In small teams one person often holds several levels. That is fine, as long as the powers are used deliberately and the owner is not also the person who forgets to sign out on a shared computer.
How these map to Call
In Call, the roles the product enforces are agent, manager and admin, and the organisation has an owner. There are no custom roles. A supervisor in the everyday sense is normally given the manager role. In Admin, in Team & Roles, the team table shows each person's name, role, status, extension, calls today, prospects and access, with cards below for teams, skills and the roles and permissions.
Roles in Call at a glance
- AgentThe default for new people. Works with calls, contacts and messages that belong to them or nobody.
- ManagerCan view the Team page and use management functions, such as confirming bookings, setting customer portal rules and managing voice settings.
- AdminAdds, edits, disables and enables people, and has the widest settings access.
- OwnerHolds the organisation; owners and admins share some actions, such as creating web lead flows.
Examples of who can do what
Looking at examples is the quickest way to understand how access is spread. These are drawn from how Call describes its own screens.
- Adding or disabling a team member: admins only. Managers can view the Team page but not change people.
- Customer portal rules and services: owners, admins and managers.
- Calling from a calendar entry: owners, admins and managers, and every calling rule still applies.
- Creating web lead flows: owners and admins.
- Choosing the workspace voice and testing a cloned voice: workspace managers.
- Reading sources for an AI agent: members can read; only workspace managers can change them.
The pattern is clear: reading is broad, changing is narrow, and anything that can affect customers or costs sits with the people accountable for it. Copy that pattern in your own rules of thumb.
Least privilege in practice
The principle of least privilege means giving each person the smallest set of powers that lets them do the job. It is simple to say and takes discipline to keep.
Setting access for a new person
- Define the jobWhat will they do in their first month?
- Choose the lowest role that fitsStart as an agent unless they need to manage others.
- Add themAn admin creates the login with a name, email and role.
- Give them an extensionWhere their calls should ring, if they take calls.
- Review after a monthWiden access only if the job needs it.
Joining, moving and leaving
Access problems usually arise at the edges of a person's time on the team. Handle all three with a short routine.
People lifecycle checklist
- New person: login created, role set, extension checked, two-factor enabled
- Moving role: change the role the same day, do not stack old powers
- Leaving: disable the login the day they go, before anything else
- Password reset by an admin: tell the person, since sessions end and they must sign in again
- Departing manager: reassign their conversations and bookings
- Quarterly: read the whole team list and ask whether each role is still right
Disabling a login blocks sign-in and can be reversed with Enable, which is useful for someone on long leave. You cannot disable your own account, and a person suspended by the platform operator can only be reinstated by the operator. Setting a new password for someone ends their existing sessions.
Common mistakes with roles
Habit versus better habit
| Common habit | Better habit | |
|---|---|---|
| Everyone is an admin | Convenient at first, but anyone can change routing or remove colleagues | Keep admins to the few people who run the system |
| One shared login | Nobody knows who did what, and nobody can be removed alone | One login per person, always |
| Access never removed | Former staff keep working credentials | Disable on the last day, as part of leaving |
| Roles set once and forgotten | Roles drift away from the real jobs | Review on a schedule and after any change |
The first habit is the most tempting. When a team is small and in a hurry, making everybody an admin removes every "I cannot do that" moment. Six months later, nobody remembers who changed the opening hours, and a new agent has deleted something by accident. Setting roles properly on day one costs a few minutes and avoids those afternoons.
Roles in a very small team
If there are only three of you, the structure can be light. A hypothetical three-person dental practice might make the practice manager the admin, the receptionist an agent and the dentist a manager who can see activity and confirm bookings. What matters is that the arrangement is written down, even in two lines, and that everyone knows who to ask for a change.
As the team grows, split the duties. The person who adds users should not also be the only person who can approve changes to routing. Having two admins also means the system is not stuck when one of them is on holiday, a point teams often miss until the day it matters.
Reviewing regularly
A role list that is never read drifts. Put a short review on the calendar. Look for people who have left, roles that no longer fit, accounts nobody recognises and shared logins. For the wider context of running the desk, see agent status and supervisor live listening.
Frequently asked questions
What roles does Call enforce?
Agent, manager and admin are the roles the product enforces, and the organisation has an owner. Custom roles cannot be created.
Is a supervisor a separate role?
Not as a separate setting. Supervisors normally hold the manager role, which gives management access without the ability to add or disable people.
Who can add or disable team members?
Only admins. Managers can view the Team page but cannot add, edit, disable or enable people.
Can I disable my own account?
No. You cannot disable yourself, which prevents locking yourself out by accident. Another admin can change your access if needed.
What happens when an admin sets a new password for someone?
The person's existing sessions end and they must sign in again with the new password. Tell them before you change it.
How often should we review roles?
At least every few months, and whenever people join, move or leave. Remove access on the day someone leaves.