Spaces

Greeting messages for riders who write to your transit service

These are opening replies for riders who message a city bus or rail service. Fill in the route and stop, copy a message, and your team or AI agent can start every chat well.

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

Before you start

A rider's first message often arrives with no greeting and no detail, such as: bus late? or how to get to the airport. Your opening reply sets the tone, and it should invite the two details every transit answer needs: which line and which stop. A warm, short start gets that fast.

Fill in your own route name and main stop below, and the messages update. Pick the one closest to the rider's question, change the wording to sound like your service, and save your favourites. Keep each opening to two or three sentences, since riders read while they walk.

General opening

Hello, this is [business]. Thanks for getting in touch. Tell me the route and the stop you are at, and I will help you with your trip right away.

Rider asks about a route

Hi, thanks for writing to [business]. I can help with the [route]. Which stop are you leaving from, and where are you heading? I will give you the usual frequency and any change on the day.

Rider is at a stop now

Hello, you have reached [business]. I can see you are at or near [stop]. Which way are you travelling? Once I know, I will check the next service and any alert on that line.

Rider asks about a fare or pass

Hi, this is [business]. Happy to help with fares and passes. Are you travelling as an adult, a student, a senior or with a concession card? That tells me which fare applies to your trip.

Keep the opening short and useful

A rider does not need a speech. They need to know someone is there and what you need from them. Say who you are, say you can help, and ask for the route and the stop. That alone usually halves the number of back-and-forth messages.

If a service alert is active on a busy line, add one line to the opening, such as: There is a delay on Line 8 this morning, and I will tell you the latest. Riders appreciate being told before they ask.

Things to avoid in an opening

A few common habits make an opening worse.

  • A long welcome that repeats your mission statement
  • A menu of options that riders must pick from
  • Slang or internal route codes that the public does not know
  • Promising arrival times before you know the line and stop

FAQ

Should the opening mention that an AI agent is replying?

Being open about it builds trust. A short line such as, I am the virtual assistant for this service, and staff are here if you need them, is honest and does not slow the chat.

What if the rider's first message is only one word?

Reply with a friendly question that narrows it down, such as asking for the line and the stop. Do not guess the meaning of a single word like late or help.

Can I use the same opening on every route?

You can use one general opening, but a route-specific one feels more helpful. Riders on a long commuter rail line ask different things from riders on a short city shuttle.

More free tools for city bus and rail transit operators

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