Spaces

First-reply checklist for taxi, bus and passenger transport chats

This checklist shows what the first reply to a new rider or booker message should hold, whether it is a taxi pick-up, a bus timetable question or a charter request. It is made for passenger transport owners and their AI agent.

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

Before you start

People who write to a transport business are usually on the move or about to be. Someone standing at a kerb wants to know where the car is. A parent wants to know if the school bus is running. An event organiser wants a coach for forty people. A slow or vague first reply sends all three to the next operator on the list.

Read each point and tick the ones your replies already do. Every gap is a place where a rider waits, worries or gives up. Share the list with your dispatchers and drivers who answer messages, and with whoever sets up your AI agent, so everyone opens a chat the same way.

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

[ ] Greet the person and use the name of your firm.
[ ] Answer the question they asked in the first line.
[ ] Ask for the exact pick-up point, not just the area.
[ ] Ask for the date, time and number of passengers together.
[ ] Ask about luggage, child seats, pets or a wheelchair early.
[ ] Say plainly if the service does not cover that area or hour.
[ ] Do not state an arrival time you cannot see in your system.
[ ] Give a contact name or number for urgent trips.
[ ] Offer a person at once if the trip involves a child or special needs.
[ ] Finish with one clear next step.

What a strong first reply sounds like

Picture your best dispatcher on a busy Friday night. They do not write an essay. They write something like: Hi, this is {business}. Yes, we can collect you at the station. Which entrance, and how many of you are travelling? That is a greeting, an answer and one question, all in a few seconds of reading.

For charters and airport transfers the first reply can ask a few more things, but still in a friendly order. Date and time first, then the places, then the number of people. Spread the questions over two or three short messages rather than one long form.

Slips that cost you trips

These are the mistakes we hear about most from passenger transport teams.

  • Sending a long block of terms and conditions as the first message.
  • Saying a car is on its way before a driver has accepted the job.
  • Asking for the pick-up point but forgetting to confirm the time.
  • Replying to a worried parent with a cheerful but empty message.

FAQ

How fast should I answer a ride or booking message?

For rides needed now, within a minute or two if you can manage it. For charters and next-week trips, the same day is fine, but a quick note saying you have the request goes a long way.

Can my agent tell a rider that a car is coming?

Only if it can read your dispatch or booking system and report what that system shows. Otherwise it should say it is checking and pass the message to a dispatcher straight away.

What if a rider writes again before I have replied?

Reply to the latest message and cover both. People who write twice are usually anxious, so a short calm note saying you are on it works better than silence or a long apology.

More free tools for taxi, bus and passenger transport firms

Read the guide: An AI agent for transit and ground passenger transportation: taxis, limousines, buses and special needs transport.