Spaces

First-reply checklist for rider messages to a transit system

This checklist shows what the first reply to a rider message should include, so a question about a late bus, a fare or a transfer gets a useful answer fast. It is made for city bus and rail operators and their AI agent.

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

Before you start

A rider who writes to a transit system is usually standing at a stop or on a platform, phone in hand, with a connection to catch. If the first reply is slow or vague, they guess, walk to another stop, or give up on the trip. The first answer carries a lot of weight.

Read each point and tick the ones your team already does. Every gap is a spot where riders get lost, or where a customer service officer loses time asking the same follow-up question. Share the list at your next shift briefing, or hand it to whoever sets up your agent.

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

[ ] Say hello and name your transit service in the first line.
[ ] Answer the exact question before adding anything else.
[ ] Ask for the route number or line name if it is missing.
[ ] Ask which stop or station the rider is at, and which way they travel.
[ ] Give times as a usual pattern, such as every ten minutes.
[ ] Point to your live service alerts for delays and detours.
[ ] Name the transfer point and the next line when a trip needs a change.
[ ] Mention fare and pass rules only when the rider asks or needs them.
[ ] Offer step-by-step help when the rider uses a wheelchair, stroller or bike.
[ ] Close with one clear next step.

What a strong first reply sounds like

Think of the best station attendant you know. They look up, answer the question, and ask one thing back. A chat reply should do the same. For example: Hi, this is {business}. The Line 4 bus from Market Square runs about every 12 minutes at this hour. Which stop are you at, so I can check the next one?

The rider asked, you answered, and you asked for the one detail you need. If a service alert is active on that line, say so in the same breath.

Slips that confuse riders

These are the mistakes that show up most in transit chats.

  • Quoting a timetable time during a known disruption.
  • Sending the full route map when the rider asked about one stop.
  • Using internal route codes the public does not know.
  • Answering a safety or harassment report with route information.

FAQ

How fast should the first reply to a rider be?

As fast as you can manage, especially during the morning and evening peaks. A rider deciding which stop to walk to will not wait long, so a short answer now beats a perfect one in an hour.

Can the agent tell a rider when the next bus will arrive?

Only if your agent is connected to your live arrivals system. Otherwise it should give the usual frequency and point to your service alerts rather than guess a time.

What if the rider does not reply to my question back?

Leave the chat open. If they were still planning a trip, one polite nudge later is fine since they wrote first. Do not keep chasing someone who has made their journey.

More free tools for city bus and rail transit operators

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