Skip to main content

Supervisors: roles and permissions

A supervisor is not a special kind of account. It is a person who holds supervisor permissions through a role, for the whole company or for chosen departments. This page lists which permissions unlock what in the web console and in the MonoPhone app, how to build a supervisor role, and how the notice beep works. For a tour of the app screens see Supervisor features in the MonoPhone app; for roles in general see Users and roles.

Which permissions make someone a supervisor​

PermissionWhat it unlocks
queues:monitorThe Supervisor page of the console and the Queues and Wallboard tabs of the app. Live view of the queues you supervise, Listen, Whisper and Barge into an answered queue call, Stop, Hang up, Log in and Log out of an agent, changing an agent's status, and the Risk watch.
calls:controlLive calls in the app: hang up or transfer one party of a call. It also lets a person force office hours when they do not hold team:status.
team:statusTeam control in the app: change a colleague's status and force office hours open or closed for a while.
callbacks:approveCallbacks in the app: reject a waiting callback or approve a failed one to be tried again.
queues:writeChange the Notice beep setting (company-wide), start, pause, resume and stop dialer campaigns, and everything the callbacks permission does. It also lets a person edit queues, so hand it out with care.
queues:readView the Wallboard, dialer campaigns and their progress, and campaign alerts.
messaging:read, messaging:writeView or control message campaigns, and answer, assign or close conversations in the team inboxes.
voicemail:readShared voicemail in the app.
recordings:readRecordings and the search over what was said.
reports:readToday (the day's figures) and the service level on the wallboard.
trunks:readTrunk alerts in the Alerts tab.
users:writeAlternative to team:status for changing a colleague's status.

The app shows the Supervisor area to anybody who holds at least one of these and shows only the tabs that person has a permission for. The server checks the permission again on every action, so hiding a screen is never the only protection. A change to a role reaches the person's app within a moment, without signing out.

What a supervisor can do with queues​

On the console Supervisor page (Team, Supervisor, queues:monitor needed), each queue you supervise shows its waiting callers, its agents and its answered calls.

  • In the console, each agent's state is a pill (green for available) with Log in or Log out next to it and a Status menu for the built-in statuses (available, away, do not disturb, lunch, business trip).
  • Listen, Whisper and Barge. Your own phone rings first. Once you answer you hear the call (Listen), speak to the agent only (Whisper) or speak to both sides (Barge). In the console the three modes are one segmented control on the call's row; the mode in force is highlighted. You can change the mode during the call, Stop the supervision, or Hang up the call. One supervisor can be in a call at a time, and the page tells the others (Another supervisor is listening).
  • Log in and Log out an agent. This changes all the queues of that agent, so you need queues:monitor for every one of them.
  • Status of an agent: Available, Away, Do not disturb, Lunch or Business trip.
  • Call an agent: your phone rings, then the agent's.

Only answered calls of a queue can be supervised. Emergency calls are never supervised, you cannot supervise a call you are part of, and an API key cannot listen in because the supervisor's own phone must ring.

Risk watch​

The Risk watch button on the Supervisor page listens to the live calls of the queues that have Live agent assist switched on and flags an Angry customer, a Churn signal or an Escalation request. Each flag has a short reason and a suggested action (Whisper or Barge) you can accept with one click. The words of the call are not stored. It needs queues:monitor for the queue, and a queue without live agent assist is not watched. A company watches at most 25 calls at once, counted across all servers of the install; a further watch is refused until one ends.

Build a supervisor role​

  1. Open People and devices, Roles and choose New role. Or open the built-in Supervisor role and use Copy into a new role, because built-in roles cannot be changed.
  2. Give it a Name and a Key (lowercase letters, digits and underscores, which cannot be changed later).
  3. In the permission matrix tick what the role may do. A good start for a queue supervisor is queues:read, queues:monitor, calls:control, call_history:read and reports:read. Add team:status, callbacks:approve, recordings:read, voicemail:read and the messaging permissions for a team lead. You can only grant permissions you hold yourself.
  4. Save, then assign it: open the user, choose Assign role, pick the role and, under Applies to, the whole company or one department.

Four editable preset roles are created for every company: Queue supervisor, Team lead, Campaign supervisor and Read-only manager. The built-in Supervisor role holds queues:monitor and calls:control among others, and Department Admin, Manager and Owner hold them too.

Scope to departments​

Every permission above can be given for the whole company or for selected departments. A supervisor of Sales sees and controls the queues of Sales and the calls that have a party in Sales, and nothing else. Anything outside that reach is answered as if it did not exist. A queue that belongs to no department needs the permission company-wide.

A few things are company-wide only: the Notice beep setting needs queues:write for the whole company, and company-wide alerts are pushed only to people who hold the permission company-wide.

The Users page has an App features column that shows Supervisor for everybody who holds a supervisor permission, and the Roles page shows which roles open the area.

The notice policy (the beep)​

By default supervision is silent. On the Supervisor page, people with queues:write see Supervisor settings with the Notice beep list:

ChoiceEffect
Silent (no beep)Nobody is told.
The agent hears a beepA short beep plays to the agent when a supervisor connects and when the mode changes.
The agent and the caller hear a beepBoth hear it.

The setting applies to the whole company. Telling callers that calls may be monitored remains your company's duty: say it in the queue's intro prompt.

Audit​

Every listen, whisper, barge, mode change, stop, hang up and agent change is written to the audit log with its result, also when the server refused it.