Spaces

Your first week with an AI agent in a government office

This checklist walks a council, clerk or elected office through the first week of an AI agent answering resident messages. It covers what to prepare, what to test and what to watch.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Starting small is the safest way to bring an agent into a public office. Residents are different from shoppers: they cannot choose another council, and any slip is quickly noticed. A careful first week lets you find gaps while the volume is low and while staff still read every reply.

Work through the steps in order, one or two a day. Keep a shared note of anything the agent got wrong or any question it could not answer. That note becomes your to-do list for the second week, and it is the fastest way to build trust among the staff who will work beside it.

Tick each one as you go. 0 of 10 done.

[ ] Write down the questions you answer most often.
[ ] Collect the current public facts in one place.
[ ] List the topics the agent must never discuss.
[ ] Name the staff who take over each type of chat.
[ ] Choose a plain, neutral voice and a short opening line.
[ ] Start with drafts that staff check before sending.
[ ] Test with ten real questions from colleagues.
[ ] Tell residents the office now uses an AI agent.
[ ] Read every conversation at the end of each day.
[ ] Hold a short team review on the last day.

A sensible shape for the week

Early in the week, concentrate on facts and limits. Midweek, test and review drafts. Near the end, let the agent send simple answers on its own, such as meeting times, while staff keep reading everything else. Widen only when the notes show few corrections.

Resist the urge to switch on everything at once. A council that starts with three topics and does them well earns more trust than one that tries thirty and gets five wrong.

Warning signs in week one

If you see any of these, pause and fix them before going further.

  • The agent gives a date or fee that has changed.
  • It sounds as if it holds a political view.
  • Staff are not seeing hand-overs in time.
  • Residents ask whether they are talking to a person and get a vague reply.

FAQ

How many topics should we start with?

Pick three to five plain ones, such as meeting dates, office hours and which department handles what. Add more only after a week of reading the chats and finding them accurate.

Do staff really need to read every reply in week one?

Yes, it is the best use of that week. You learn where the facts are thin, and staff see that the agent helps them rather than replacing the judgement they provide.

Should we announce the change to residents?

A short, honest note on your page or in the chat is enough. Say that an AI agent answers simple questions and that a person is always available when someone asks.

More free tools for councils and government offices

Read the guide: Answer constituent and resident messages for government offices.