BlogSupportSystem statusEspañolHosted in the USA

Guides

Training staff on the supervisor console in one afternoon

A new phone agent changes some daily routines, but it should not need weeks of training. This guide lays out a plan for getting supervisors, department staff and records staff comfortable with the SentraOperator supervisor console, in about an afternoon of sessions.

Who needs what

Staff sign in with role-based permissions. Each role sees and does different things, so train by role rather than all together:

  • Supervisors run the line: dashboard, call log, reports and settings.
  • Department staff take transfers and follow up on calls for their department.
  • Records clerks handle exports and public records requests.
  • City attorney staff may need legal holds and exports.
  • IT admins manage access and technical settings.

Short, separate sessions keep each group focused on what they will actually use.

Session 1: Department staff

Department staff mostly meet SentraOperator through the phone. A 30-minute session covers it:

  1. The whisper. Before a transferred caller is connected, staff hear a one-line summary. Play a test transfer so everyone hears one.
  2. What the caller has already done. The caller has already explained the problem to the agent. Staff should confirm, not start over.
  3. Messages. When a department is closed or no one answers, the agent takes a message. Show where those calls appear in the call log, with transcript and summary.
  4. Request numbers. Requests filed by the agent are tagged "Phone (SentraOperator)" in Sentra 311.

See talk to a person for the full transfer flow.

Session 2: Supervisors

Supervisors need the longest session, about 90 minutes, with hands on the console. Cover these areas in order.

The dashboard

Walk through calls today, the share handled without staff, requests filed, texts, average call length, after-hours share, calls by hour, top requests and the minute bundle. Explain what each one tells you.

The call log and call review

Search for a call, open it and play the recording while the transcript follows along. Click a line to jump to it. Show the summary and sentiment, and stress that both can be wrong. See AI call summaries and sentiment.

Settings

Go through departments, transfer numbers, hours, holidays, request types, greeting, languages, FAQ and other agencies. Make one small change together, such as fixing an FAQ entry, then show it in the change log. Changes take effect on the next call, so remind supervisors to double-check before saving.

Reports

Pick a date range, review top request types and the unhappiest calls list, and export a CSV.

A 45-minute session for records clerks and city attorney staff:

  • Searching the call log by date, request number or words in the transcript.
  • Exporting a call for a public records request.
  • Placing and releasing legal holds. Calls on hold are never auto-deleted.
  • The retention schedule. Who set it and how deletion works.
  • The access log. Every play, download, export, hold and settings change is recorded.

Have your records manager confirm local practice. Public records laws vary by state. See public records requests and transcripts.

Practice and follow-up

Practice with test calls

Reading about the console is less useful than using it. Before training, have someone place a set of test calls:

  • a new request, such as a pothole at 200 Elm St
  • a status check on a request number
  • an FAQ question, and one the FAQ does not cover
  • a "talk to a person" transfer, and one that goes unanswered
  • a call in Spanish, if your city offers it

During the sessions, staff find these calls in the log and work through them. It makes every feature concrete.

Write a one-page cheat sheet

After training, give each group a single page. For supervisors, that might list:

  1. Where to check yesterday's after-hours messages.
  2. How to update an FAQ entry and who approves it.
  3. How to change hours for an unplanned closure.
  4. Who to call if a transfer number breaks.

Keep it short enough to tape next to a monitor. Our holiday and closure schedules post has a closure checklist that fits well here.

Plan a follow-up

Schedule a 30-minute check-in two to four weeks after go-live. By then supervisors will have real questions. Common ones are about FAQ gaps, transfers that go unanswered and how to read the reports.

New staff can be trained by a supervisor using the same plan. The supervisor console tour is a good pre-read.

The short version

Train by role. Department staff need the whisper and messages. Supervisors need the dashboard, call review, settings and reports. Records staff need search, export, legal holds and the access log. Use real test calls, hand out a one-page cheat sheet and check in after a few weeks.

See the supervisor console