BlogSupportSystem statusEspañolHosted in the USA

Running a 311 line

Holiday and closure schedules for your 311 phone agent

The phone agent knows when city hall is closed because your supervisors told it. Holidays and unplanned closures are where that matters most. This post covers how to set up holiday and closure schedules in SentraOperator so callers get the right answer on the days when routines change.

Why holidays trip up phone lines

On a normal day, hours are predictable. Holidays are not. Some departments close and others stay open. Trash pickup shifts by a day. An early closure on the day before a holiday catches people off guard.

If the phone line does not know about a closure, two things go wrong. Callers get transferred to a department where nobody is answering. Or they hear the regular schedule and show up to a locked door.

How the agent decides you are closed

In the supervisor console, each department has its own hours, and the city has a holiday list. When a call comes in, the agent checks both.

  • During hours, a caller who says "talk to a person" or presses 0 is transferred to the right department.
  • Outside hours or on a holiday, there is no one to transfer to, so the agent takes a message with the caller's name, callback number and what they need.
  • Everything else keeps working. Requests are still filed in Sentra 311, status checks still work, and FAQ questions are still answered.

The agent does not guess at holidays. If a date is not on the list, it treats the day as a normal one. Changes take effect on the next call, and every change is logged with who made it.

Build the year at once

The easiest approach is to load the full year's holiday calendar in one sitting, usually when council adopts it. A checklist for that session:

  1. City-wide holidays. The days when every department is closed.
  2. Department-only closures. Days when, say, the Permit Counter is closed for training but Utilities is open.
  3. Early closures. Days when offices close at noon. Set these as shorter hours for that date, not as a full holiday.
  4. Floating or observed days. When a holiday falls on a weekend, check which weekday the city observes.

Put the session on someone's calendar each year. Our post on after-hours 311 calls covers how messages are handled when a department is closed.

Tell callers what changed

The holiday list tells the agent when to take messages. It does not tell callers that trash pickup moved. For that, add a dated FAQ entry, such as:

"Because of Memorial Day, trash and recycling pickup this week is one day late. Monday's route will be picked up Tuesday, and so on through Saturday."

Add the entry a few days before the holiday, and remove it when the week is over. The agent answers general questions only from your FAQ, so a stale holiday entry will keep being read to callers until someone deletes it. See writing the agent's FAQ for more on wording.

If your city wants every caller to hear a holiday notice, a supervisor can also adjust the greeting. Keep it short, and keep the three required lines at the start: the AI disclosure, the recording notice and the 911 line.

Unplanned closures

Not every closure is on the calendar. Snow, power outages, a water main break at city hall or a building evacuation can all close offices with little warning.

Plan for these the same way you plan for a storm:

  • Decide who can make the change. At least two people should be able to update hours and the holiday list from the supervisor console.
  • Write a short closure FAQ entry in advance. Keep a template ready, such as "City hall is closed today, Tuesday, because of a power outage. Online services are still available."
  • Check transfer numbers. If a department is working from another site, update its transfer number so calls follow staff. See setting department transfer numbers.

Our storm day planning post covers the rest of the checklist for days when calls spike.

Check your work

After loading the calendar, test it. Look at the call log on the first holiday and confirm calls were handled as expected: messages taken for closed departments, transfers for open ones, and FAQ answers that match the week.

The reports in the supervisor console show calls by day and hour, so you can see what holiday call volume actually looks like in your city. That helps next year's planning more than any guess.

The short version

Load the year's holidays in one sitting, including department-only closures and early closures. Add dated FAQ entries so callers hear what changed, and remove them afterward. Keep a closure template and two named people ready for the days that are not on the calendar.

See the supervisor console