Spaces

Your first week with an AI agent in a program office

This checklist walks a program office through the first week of letting an AI agent answer routine chat questions. It covers what to write down, who takes over and how to check the early replies.

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

Before you start

The first week matters more than it looks. In a program office the agent speaks for a public body, so people will treat its words as the office own. A careful start, with current information and clear limits, builds confidence among staff and the public. A rushed one leaves you correcting mistakes in public.

Use the list below as a simple day-by-day plan. You do not need to finish everything in a single day. Do the steps in order, tick them as you go, and keep the list on your desk. If a step cannot be done yet, wait before you move on to the next.

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

[ ] Write a one-page summary of each program in plain words.
[ ] Check hours, holiday closures, addresses and phone lines for errors.
[ ] List every form, its purpose and where the current version lives.
[ ] Write down the topics the agent must not answer at all.
[ ] Name the person or queue for each hand-over type.
[ ] Test your safeguarding route with a pretend message.
[ ] Try twenty real past questions and read the agent replies aloud.
[ ] Tell staff what the agent will and will not do.
[ ] Review every chat on day three and again on day five.
[ ] Fix the guidance, then note one change to try next week.

What to expect in week one

Most offices find the early chats are dominated by the same five or six questions. That is a good sign. It means a short piece of guidance can take care of a large share of routine traffic, and staff can spend time on the harder cases.

You may also find gaps. People ask about things your pages never mention, such as which door to use or whether a parent can send someone else. Write each gap down. It becomes tomorrow guidance.

Common first-week mistakes

Avoid these and the week will go more smoothly.

  • Starting with a long manual instead of a short, accurate page per program.
  • Skipping the safeguarding test because it feels unlikely to matter.
  • Telling nobody on the team, so handovers surprise them.
  • Reading only the replies that went wrong and ignoring the good ones.

FAQ

How much information does the agent need to start?

Less than most offices expect. Hours, a paragraph on each program, the list of forms, the hand-over rules and a few model replies are enough for a careful first week. You can add more as gaps appear.

Should the whole team know before launch?

Yes. Staff who receive handovers should know what a note looks like, how quickly to respond and how to correct the agent. A short briefing of ten minutes avoids a lot of confusion later.

When should we review the first conversations?

Read them daily at first, even for a few minutes. Look for wrong answers, missed handovers and tone that feels off. After the first week, move to a regular weekly review instead.

More free tools for education, health and social program offices

Read the guide: Answer routine program questions in chat, and keep every decision with your staff.