BlogSupportSystem statusHosted in the USA

How it works

Answering "when's the next council meeting?" from CivicCA

Meeting questions come in to city hall all week: when is the next council meeting, is the budget on the agenda, where is it held. SentraOperator answers these from CivicCA, the same system the clerk's office uses to publish meetings and agendas.

A small question that adds up

Each meeting question takes a clerk a minute or two. Look up the calendar, find the agenda, read the item. On its own, that is nothing. Across a week, especially before a meeting with a contested item, those minutes add up, and they land on the staff who are busiest preparing the meeting.

Most of these questions have a factual answer that is already published. That makes them a good fit for a phone agent, provided it answers only from the published source.

Where the answers come from

CivicCA is a sister product for clerks and councils. When your city uses CivicCA and turns on meeting answers, the phone agent can look up:

  • When the next meeting is, for the bodies your city includes.
  • What is on the agenda for an upcoming meeting.

The agent answers from what CivicCA has. It does not answer meeting questions from memory or from general knowledge, and it never makes up a date. If the agenda isn't published yet, the caller hears that, not a guess.

What a call sounds like

Here is an example from the fictional City of Riverbend.

Caller: "When's the next city council meeting?" Agent: "The next Riverbend City Council meeting is Tuesday, November 17, at 6 p.m. Would you like me to text you a link to the agenda?"

That date is illustrative. In a real call, the agent reads the actual date and time from CivicCA. If the caller asks whether a particular topic is on the agenda, the agent answers from the published agenda. If the caller says yes to the text, the agent sends an agenda link. Like every SentraOperator text, it starts with the city's name and ends with "Reply STOP to opt out."

Why the agent sticks to the source

Meeting information is sensitive in a particular way. A wrong date can mean a resident misses the chance to speak on an item that matters to them. A wrong description of an agenda item can cause confusion before a contested vote.

So the rule is strict. The agent only answers from the city's FAQ, CivicCA meeting information or its own tool results. If it doesn't know, it says so and offers a transfer. For a meeting question, that transfer usually goes to the City Clerk.

What it doesn't do

It helps to be clear about the edges:

  • It doesn't explain or interpret agenda items. It can tell a caller an item is on the agenda. Questions about what it means belong to staff.
  • It doesn't take public comment. If your city has a process for submitting comment, put the instructions in your FAQ so the agent can describe them, or have callers transferred.
  • It doesn't answer for bodies you haven't included. Your city chooses which meeting bodies the agent covers.

Callers can say "talk to a person" or press 0 at any time.

What the clerk's office should know

The agent is only as current as what is published. A few habits keep answers accurate:

  1. Publish agendas in CivicCA as you normally do. The agent reads what is there.
  2. Update CivicCA promptly when a meeting moves or is canceled. That change is what callers will hear.
  3. Add common process questions to the FAQ, such as where meetings are held or how to sign up to speak.
  4. Check the call log. Meeting questions appear with an "Answered" outcome, and supervisors can search transcripts to see what residents ask most.

In the supervisor console, the City Clerk department can be set up with meetings answered from CivicCA, plus its own hours and transfer number for anything the agent can't answer.

Meetings as part of the whole line

Meeting answers aren't a separate service. They are part of the same call. A resident can report a streetlight, ask when the next council meeting is, and get both answers before hanging up. Requests still go to Sentra 311, meeting answers still come from CivicCA, and the call log keeps one record of the whole call.

The short version

SentraOperator answers "when is the next council meeting" and agenda questions from CivicCA. It never makes up a date. If something isn't published, it says so and offers a transfer to the clerk's office. It can text an agenda link if the caller says yes. Keeping CivicCA current keeps the phone answers current.

See the integrations