Spaces

Hand-over rules: rail vehicle chats that must go to a person

This checklist lists the messages a locomotive or railcar builder should always pass from the AI agent to a person, such as defects, braking, structural findings and claims. It helps you set the rules before a partner is let down.

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

Before you start

An agent can safely answer gate times, document requests and shipping weeks. A rail vehicle is different from most products, because a wrong word about brakes, couplers or a cracked frame can reach passengers or crews. Some messages need an engineer, and they need one fast.

Go through each rule and decide whether it fits your plant, your depot support team and your contracts. Then give the final list to whoever sets up your agent, and name a person for each topic with a backup. A rule with no owner fails the first time someone is on leave.

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

[ ] Any report of a defect, crack, leak or unusual noise on a vehicle.
[ ] Anything about braking performance or a brake test result.
[ ] Reports of a derailment, collision, fire or injury.
[ ] Questions about structural fitness, repairs or modifications.
[ ] Requests to change a contract, price, delivery date or payment term.
[ ] Warranty claims and disputes over who pays.
[ ] Requests for drawings, test records or software that are not on the shared list.
[ ] Urgent spares for a vehicle that is out of service.
[ ] Messages from regulators, auditors, the press or unknown senders.
[ ] Anything the agent is unsure about, or a partner asking for a person.

Make the hand-over useful to the engineer

A person picking up a chat should not have to ask the basics again. The agent should leave a short note: who wrote, which vehicle number, which project, what they said and where the vehicle is. Our hand-over notes tool shows how to write one.

Tell the partner what happens next in one calm line, such as: I have passed this to our service engineer, who will call you today.

Agree these with your team first

Settle the answers before the first message arrives.

  • Who covers defects and incidents out of hours and at weekends?
  • What is the longest a partner should wait for an engineer to respond?
  • Who steps in when the usual contact is on leave or on site?

FAQ

Why must defect reports always go to a person?

A rail vehicle defect can mean a safety risk and a warranty question at the same time. An engineer has the records and training to judge it, and the agent does not.

Can the agent still be helpful while it hands over?

Yes. It can collect the vehicle number, location, time and a short description, then tell the partner who is taking over. It must not offer a diagnosis or promise a fix.

Should I list every possible risky word?

Start with the obvious ones: brake, crack, derail, collision, fire, injury, failure. Review chats each week and add words you see partners use for the same problems.

More free tools for rail vehicle builders and rebuilders

Read the guide: Keep rail vehicle partner messages moving without extra staff.