SentraOperator answers general questions, such as hours, trash day and permit basics, only from the FAQ your city provides. That makes the FAQ one of the most important settings you control. This guide covers how to write entries that work well when read aloud to a caller.
Why the FAQ matters so much
The agent does not draw on general knowledge about cities. If a caller asks when the transfer station opens, it looks to your FAQ. If the answer is there, it gives it. If not, it says it does not know and offers a transfer.
It never makes up a date, a phone number or a policy. That is the right behavior for a public line, but it means gaps in the FAQ turn into transfers. A good FAQ answers the routine questions, so staff time goes to calls that need a person.
Start with the calls you already get
Before writing anything, ask the people who answer the phone today. They know the top questions without looking. A quick list from a front desk might include:
- What day is my trash pickup?
- What are city hall's hours?
- Do I need a permit for a fence?
- How do I pay my water bill?
- Where do I get a dog license?
- When is bulk item pickup?
Questions about council meetings are a separate case. The agent answers "when is the next meeting" and "what's on the agenda" from CivicCA, so those don't need FAQ entries. See council meeting questions.
Write for the ear, not the page
A web FAQ is scanned. A phone answer is heard once, at the speed of speech. A few rules help:
- Lead with the answer. "City hall is open Monday through Friday, 8 a.m. to 5 p.m." Then add detail if needed.
- Keep it short. Two or three sentences is plenty. Long answers are hard to follow on a phone.
- Avoid tables and links in the text. "See the chart below" means nothing on a call.
- Spell out what matters. Write "the Public Works yard at 400 Mill Road," not "PW yard."
- Give one next step. "You can apply online or at the permit counter on the second floor."
An example
Here is a fence permit entry, first as many websites write it, then rewritten for the phone.
Web version: "Fence permits are required per Municipal Code 18.40 for fences exceeding thresholds in Table 18-4. See the Building Division page for fee schedule and submittal requirements."
Phone version: "Riverbend requires a permit for most fences over six feet tall. You can apply at the permit counter at city hall, 100 Main Street, or I can text you a link to the application form."
The phone version gives the answer, the place and a next step. If your city has set up form links for texting, the agent can send one, but only after the caller says yes. See texting callers.
Keep it accurate
A wrong FAQ answer is worse than no answer, because the agent will repeat it with confidence. Build upkeep into the routine:
- Name an owner for each topic. Utilities owns billing questions. Solid Waste owns pickup questions.
- Date anything temporary. Holiday schedules, storm notices and road closures should say when they apply, and someone should remove them after.
- Review on a schedule. Once a quarter, read the whole FAQ out loud. Anything that sounds odd spoken will sound odd to callers.
Every settings change is logged with who made it and when, and changes take effect on the next call. That makes it safe to fix a wrong answer the moment someone spots it.
Find the gaps with the call log
After go-live, the call log shows where the FAQ falls short. Look for calls where the agent said it did not know and offered a transfer. Each one is a candidate for a new entry.
The reports also show top request types and the unhappiest calls to review. If callers keep asking the same thing and getting transferred, that question belongs in the FAQ. Our supervisor console tour shows where to find these views.
Not every gap should be filled. Questions that need judgment, such as whether a specific project needs a variance, belong with staff. The FAQ should cover what has one clear answer.
The short version
Write short, spoken answers that lead with the fact and end with one next step. Start from the questions your front desk already hears, give each topic an owner, date anything temporary and use the call log to find what is missing. The agent will only ever say what the FAQ says.