Spaces

Do and don't guide for your agent answering transit riders

This guide gives plain do and don't rules for an AI agent that answers transit riders. It helps operators set clear boundaries on timetables, fares, disruption and safety.

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

Before you start

Riders ask short questions and expect short, true answers. An agent that follows a few firm rules sounds calm and helpful, while one without rules may guess a time, invent a fare or brush off a safety report. The rules below are the ones that matter most on a transit network.

Read the list, change anything that does not fit your system, and give it to whoever sets up your agent. Then check a few chats each week to see that the rules are being followed. Print it for your customer care team too, so people and agent work the same way.

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

[ ] Do answer the route or stop question first, in a sentence or two.
[ ] Do say that times are usual patterns unless a live source is connected.
[ ] Do point riders to today's service alerts for any delay or detour.
[ ] Do explain fare, pass and concession rules in plain words.
[ ] Do give step-free options clearly when someone mentions access needs.
[ ] Don't promise that a bus or train will arrive at a set minute.
[ ] Don't guess a fare, a refund or a fine amount.
[ ] Don't give advice about injuries, first aid or personal danger.
[ ] Don't argue with a rider who is upset about a late or missed service.
[ ] Don't share another rider's details, lost items or travel history.

Why firm rules help the agent

An agent follows clear boundaries well. Left vague, it may fill gaps with something that sounds right. By saying exactly what it may not guess, such as live arrival times or fine amounts, you turn a risky area into a simple handover.

Write the rules in everyday words, the way you would brief a new customer service officer on day one. Add an example for each tricky rule if you can.

Rules to add for your own network

Every system has local quirks, so add a few rules of your own.

  • Names riders use for stops that differ from the names on your signs
  • Routes that run only on school days or event days
  • Which fare zones cause the most confusion
  • The phrase to use when a service is suspended

FAQ

How many rules should I give my agent?

Ten to fifteen firm rules is plenty to start. Focus on timetables, fares, disruption, safety and privacy, then add more when weekly reviews show a repeated slip.

What if a rider asks for something the rules forbid?

The agent should say politely that it cannot do that itself and hand the chat to a person with a short note. It should not argue or leave the rider waiting without a reply.

Should staff follow the same rules?

Mostly yes. Staff can go further when they have authority, such as agreeing a refund, but the same care about promises, privacy and safety applies to everyone who answers riders.

More free tools for city bus and rail transit operators

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