Spaces

Weekly chat review checklist for community transport

This weekly checklist helps community and special needs transport owners review the chats their AI agent handled, spot wrong answers, and fix what confused riders and carers.

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

Before you start

A weekly look at your chats is the cheapest way to keep a transport service dependable. Riders rarely complain when an answer is slightly wrong. They simply stop trusting the chat and ring the office, which costs you the time you hoped to save.

Set aside twenty minutes on a quiet day, such as Monday after the weekend rides. Skim a sample of chats, tick the points below, and write down one change for the week ahead. Small, steady fixes beat a big clear-out every few months.

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

[ ] Read every chat that was handed to a person.
[ ] Look for any chat where a rider or carer sounded upset.
[ ] Check that every ride request has all five key details.
[ ] Count how many chats were about running late or not arrived.
[ ] Check whether any promised callback was missed.
[ ] Spot any answer that mentioned eligibility or funding.
[ ] Note questions the agent could not answer.
[ ] Check that standing rides were kept separate from one-off trips.
[ ] Look for details shared that should have stayed private.
[ ] Pick one change to make before next week.

How to read a week of ride chats

Look for patterns rather than single chats. If three carers asked whether your vans reach the hospital annex, the answer was not clear enough in your notes. If several riders wrote at the same hour, your pickup times may be bunching.

Share one finding with the team each week. A dispatcher who hears that carers keep asking about return trips will start offering it early, and the number of those chats will fall.

A simple weekly rhythm

Keep the review small enough to repeat.

  • Fifteen minutes reading chats, five minutes writing the fix.
  • Same day each week, so it becomes habit.
  • One person owns it, with a deputy for holidays.

FAQ

How many chats should I read each week?

Read every handed-over chat and a handful of others at random. For a small service that may be fifteen or twenty chats, which is quick enough to finish in a short sitting.

What counts as a bad answer?

One that is wrong, vague, or promises something only a person can promise, such as a held seat. Also flag any reply that made a carer ask the same question twice.

Who should do the weekly review?

Someone who knows the service well, usually the scheduler or the manager. They can tell at a glance whether an answer matches how you really run rides.

More free tools for special needs and community transport services

Read the guide: Answer ride requests for people who depend on your service.