Spaces

Reply speed scorecard for transit rider messages

This scorecard asks eight yes or no questions about how your bus or rail service answers rider messages. It shows whether riders get fast, useful replies in the peak and after hours.

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

Before you start

On a transit network, a slow reply is often useless. A rider asking whether to wait for the bus or walk to the next stop needs an answer in minutes, not hours. By the time a slow reply arrives, the rider has already made their choice, and may have made a bad one.

Answer each question honestly, based on a normal week and not your best day. Count the yeses at the end to see where you stand. Do the exercise with a colleague from customer care or the control room, since you may remember the week differently.

Do you reply to most rider messages within ten minutes during the morning and evening peaks?
Do you reply to rider messages sent after your customer care desk closes, even if only with a holding note?
Do you have written answers for fares, passes and concessions that every team member uses?
Do you check that delay and detour advice matches the live service alert before you send it?
Do you ask riders for the line and stop in the first reply when they leave it out?
Do you pass safety, harassment and injury messages to a named person within minutes?
Do you log lost property messages with a reference number the rider can quote?
Do you look at a sample of rider chats each week to find wrong or slow answers?

Answer all 8 to see your result. 0 so far.

What your score tells you

A low score does not mean your team is failing. It usually means the rider messages have grown faster than the team, which is common for networks where chat has become a main channel. The fix is clear steps and a little help, not blame.

A high score is a good sign, but check it against the peaks. Many teams score well on a quiet Tuesday and badly on the first rainy Monday of the term.

Quick wins at any score

These changes help nearly every transit team.

  • Write a first reply that asks for line and stop
  • Give every lost property case a reference
  • Name an on-call person for safety messages
  • Review twenty chats each Monday

FAQ

How fast is fast enough for rider messages?

During the peaks, aim for minutes. Riders at a stop need answers at once. For fares, passes and lost property, a same-day answer is usually fine, as long as the first reply says so.

Does this scorecard measure my agent or my team?

Both, since the questions describe how messages are answered. Whether a person or an AI agent replies, riders judge the speed, the clarity and the care of the response.

How often should I repeat the scorecard?

Every three months, and after a big change such as a new timetable, a new fare system or a new agent. Compare scores to see whether you are improving.

More free tools for city bus and rail transit operators

Read the guide: Answer rider questions about routes, passes and lost property.