Spaces

Your first week of answering ride requests with an AI agent

This is a first-week checklist for community and special needs transport services that want an AI agent to answer ride messages. It covers the facts to write down and what to check each day.

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

Before you start

A transport service runs on routines, and your riders trust those routines. So start small. In the first week you are not trying to answer everything. You are making sure the facts are right, your team knows what is happening, and a scheduler is ready when the agent hands a chat over.

Work through the items in order, ideally beginning on a quieter day. Tick each one off as you go. If one does not suit your service, swap it for something that does. The habit of checking the chats every day matters more than the exact list.

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

[ ] Write down your service area, with the towns and clinics you cover.
[ ] Write down operating days, hours and the booking cut-off time.
[ ] List your vehicles and which ones have ramps, lifts and tie-downs.
[ ] Write your escort, carer and companion rules in two lines.
[ ] Write how to cancel, and what happens if a rider is not ready.
[ ] Name the scheduler who takes over every handed-over chat.
[ ] Tell your drivers and dispatchers that chats are now answered.
[ ] Test with five real questions from your own phone.
[ ] Read every chat at the end of each of the first three days.
[ ] Fix the two most common weak answers, then review on day seven.

What the first week usually shows

Most services discover gaps quickly. Someone asks whether you serve the hospital on Saturdays, or whether a carer can bring a second bag, and nobody ever wrote down the answer. Add it and move on. That is exactly what the first week is for.

You may also learn that some riders are better served by a call from the start. That is fine. The aim is to take routine questions off your scheduler so they have time for the rides that need a human.

Keep these slow

A few things are worth going gently on.

  • Do not widen the service area in the agent notes until you are sure.
  • Do not skip telling the drivers, even in a small team.
  • Do not judge the agent on one unusual conversation.

FAQ

How much do I need to write down before starting?

A single page is enough: area, hours, vehicles, booking and cancellation rules and who takes over. You can add more every day as real questions show you what is missing.

Should I tell riders and carers that an AI agent is replying?

Being open about it is a good habit. A short line in your greeting saying the first reply comes from an AI agent, with your team behind it, keeps expectations honest and calm.

What if the agent gives an answer I do not like?

Note the exact question, correct the information the agent works from, and test it again. Most weak answers come from a missing fact, not from the agent being careless.

More free tools for special needs and community transport services

Read the guide: Answer ride requests for people who depend on your service.