Spaces

First-week checklist for a hospital AI agent on chat

This checklist walks a hospital through its first week of letting an AI agent answer visitor and outpatient messages. It covers the notes, the limits, the hand-over people and the daily checks.

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

Before you start

A hospital cannot switch on an agent and hope for the best. The first week is for getting the facts right, setting hard limits and watching closely. Visitors will ask about parking and visiting hours straight away, and a few messages will test the edges, so the team needs to be ready for both.

Work through the list in order, one or two items a day. Assign each item to a real person, such as facilities for the maps or the privacy officer for the limits. By the end of the week you should know exactly what the agent says, who catches the rest, and what you still need to fix.

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

[ ] Write down visiting rules for each type of ward.
[ ] Add entrances, car parks, drop-off points and accessible routes.
[ ] List each department and how people should reach it.
[ ] Write the emergency wording and have a clinician check it.
[ ] Write the limits: no patient confirmations, no clinical advice.
[ ] Name the staff who take handed-over chats on each shift.
[ ] Test fifteen real past messages with the team watching.
[ ] Run a few awkward tests, such as a named patient and a worrying symptom.
[ ] Read every conversation at the end of each day.
[ ] Hold a short review on day seven and update the notes.

A sensible shape for the week

Spend the first two days on the written notes and the limits, because everything else depends on them. Days three and four are for testing with real past messages and awkward cases. From day five, let the agent answer live while a named person reads each chat the same day.

Keep the scope narrow at the start. Visiting hours, directions and parking are a safe beginning. You can add clinic bookings or billing contacts later, once the basics hold steady and the team trusts the handovers.

Things teams often forget

These small gaps cause most early problems.

  • Temporary changes such as building works and closed lifts.
  • Out-of-hours handover people, especially at weekends.
  • Rules for children's, maternity or psychiatric units.
  • A clear way for the agent to say it does not know.

FAQ

Do we need our whole hospital ready before the first week?

No. Start with one site and one narrow set of questions, such as visiting hours and directions. Add departments and clinics as the notes and the handovers prove reliable.

Who should read the chats during the first week?

A named person with authority, such as a patient experience lead or a senior administrator, should read every chat daily and flag anything clinical or unclear to a clinician.

What if the agent gives a wrong answer during the week?

Fix the written note that caused it the same day, and tell the team. If it touched a patient or a safety matter, escalate it through your usual incident route.

More free tools for hospitals and hospital admin teams

Read the guide: An AI agent for hospital enquiries and administration.