Spaces

First-week checklist for a transit agent answering riders

This checklist covers the first week of letting an AI agent answer rider chats for a bus or rail system. It helps transit teams start small, catch mistakes early and keep staff in control.

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

Before you start

Transit riders are quick to notice a wrong answer, and a wrong answer about a route or a last service can leave someone stranded. That is why the first week matters. A careful start, with staff watching, builds the trust you need before the agent takes on the morning peak.

Work down the list in order. Some steps take ten minutes and some need a meeting with your control room or customer care team. Do not rush the early ones, because everything the agent says rests on the route and fare notes you write down first.

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

[ ] Write down your routes, stops, first and last services and usual frequencies.
[ ] Write plain answers for fares, passes, concessions and how to reload a card.
[ ] List accessibility features by route, station and vehicle type.
[ ] Write the lost property steps and the details your desk needs.
[ ] Choose who takes handed-over chats on each shift, including evenings.
[ ] Decide where live delays and detours will come from each day.
[ ] Test the agent with twenty real past rider questions.
[ ] Run the first three days with a staff member reading every chat.
[ ] Fix any wrong answer the same day, and note why it happened.
[ ] Review how many chats were handed over by day seven.

Start with the quiet hours

If you can, switch the agent on first for off-peak and evening messages. Fewer riders are writing, the questions are simpler, and your staff have time to read each reply. Move to the morning and evening peaks once a few quiet days have gone well.

Tell your customer care team what is happening and why. They will be the ones who take the handed-over chats, and they will spot odd answers faster than anyone.

What to look at on day seven

At the end of the week, sit down for twenty minutes and look at these.

  • Questions the agent could not answer.
  • Chats that went to staff and did not need to.
  • Any rider who wrote back to say the answer was wrong.
  • Gaps in your route or fare notes that showed up.

FAQ

Do I need to write down every route before starting?

No. Start with your busiest routes and the most common fare questions, then add more as chats show what riders ask. Anything missing should be handed to a person, not guessed.

How do I keep the agent from quoting old detour information?

Give it one place to read today's service alerts and ask it to point riders there. When no current note exists, it should say it is checking and pass the chat to staff.

Who should read the chats in week one?

Someone from customer care who knows your network well. They can spot a wrong route or fare quickly, and they will be the person riders meet when a chat is handed over.

More free tools for city bus and rail transit operators

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