Sooner or later a council member will ask whether the phone agent is worth it. A good answer uses real numbers from your own line, read honestly. This post covers what the supervisor console measures and how to present it.
Start with the question council is asking
Before you pull any numbers, write down the question. Council questions about a 311 phone agent usually fall into a few groups:
- Is it answering calls? How many, and when.
- Is it doing useful work? Requests filed, questions answered, callers sent to the right agency.
- Are residents still reaching people when they need to? Transfers and messages.
- Is it on budget? Minutes used against the bundle the city bought.
Pick the numbers that answer the question asked. A short report that answers one question clearly is more useful than every chart the console can draw.
What the console measures
The dashboard
The dashboard shows live numbers for any day you choose:
- Calls, and the share handled without staff.
- Requests filed in Sentra 311, all tagged "Phone (SentraOperator)".
- Texts sent to callers who said yes.
- Average call length, measured per second of connected time.
- After-hours share, the calls outside office hours.
- Calls by hour, split between office hours and after hours.
- Top requests, the request types callers asked about most.
Two of these tend to matter most to council. After-hours share shows calls that would otherwise have reached voicemail. Calls by hour shows when residents actually call, which is useful for staffing conversations.
Reading "handled without staff" carefully
"Handled without staff" is the number people quote most, and the one most easily misread. It means the call ended without a transfer to a department. The caller filed a request, checked a status, got an answer from your FAQ, or was given another agency's number.
It does not mean no staff work followed. A filed pothole request still needs a crew. Present it as "calls that didn't need a clerk on the phone," not as work that disappeared.
Pair the number with its opposite. Report transfers and messages alongside calls handled without staff. It shows council that residents who wanted a person got one.
Usage and the minute bundle
The usage screen answers the budget question. It shows minutes used against your annual bundle, a month-by-month chart, rolled-over minutes, and how many extra 1,000-minute blocks you have used against the limit your city set. Monthly usage reports can be downloaded to attach to a staff report.
Since the per-minute rate is fixed for the contract term, the budget conversation is about volume, not price changes. If you are on pace to finish the year with minutes left, they roll over until the contract ends.
Building the report
Here is a simple structure for a quarterly report to council, using a hypothetical example.
- One sentence on what the line does. "The 311 line is answered 24/7 in English and Spanish, and callers can reach staff at any time."
- Volume. Say, as an example, the line received 3,000 calls in the quarter. State how many came after hours.
- Outcomes. Requests filed, status checks and FAQ answers, county referrals, and transfers to staff.
- What residents call about. The top five request types.
- Budget. Minutes used against the bundle, and whether any extra blocks were needed.
- What you changed. New FAQ answers, request types or other-agency entries added because of what the calls showed.
That last item is often the most persuasive. It shows staff are running the line, not just watching it.
Behind the numbers
The call log
Numbers get questions, and the call log has the answers. If a council member asks about a specific neighborhood or complaint, a supervisor can search transcripts, addresses and request numbers, and filter by outcome or department. The call log can be exported as a CSV for your own analysis.
Be careful with what you share. A council report should describe patterns, not individual callers. Check with your records manager before attaching any transcript.
What is coming
Quality review, coming in 2027, adds a monthly view of how many calls still needed staff and why, alongside drafted fixes for supervisors to approve. Until then, the dashboard, call log and usage reports cover what council usually asks.
The short version
The dashboard reports calls, the share handled without staff, requests filed, texts, average call length, after-hours share, calls by hour and top requests. The usage screen shows minutes against your bundle and downloadable monthly reports. Answer the question council actually asked, read "handled without staff" carefully, and always show transfers too.