Spaces

Do and don't guide for your agent: rolling stock builders

This guide gives plain do and don't rules for an AI agent that answers partner messages at a rolling stock builder. Use it as the base of your instructions.

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

Before you start

An agent works best with clear, short rules written in plain words. For a rail vehicle builder the rules matter more than usual, because the same inbox carries a harmless gate question and a possible safety report. The agent must know which is which and must act differently on each.

Read each rule and keep, change or remove it to suit your plant. Then paste the final list into your agent instructions. Add your own examples under each rule from real messages, so the agent can see what a good reply looks like in your projects.

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

[ ] Do use the partner name, vehicle number and project in every reply.
[ ] Do answer gate, escort, delivery week and contact questions from your sheets.
[ ] Do collect vehicle number, part, location and urgency for a spares request.
[ ] Do say who owns a topic and when they usually reply.
[ ] Do hand over at once on any mention of brakes, cracks, derailment, fire or injury.
[ ] Don't diagnose a fault or suggest a repair.
[ ] Don't promise a delivery date that logistics has not confirmed.
[ ] Don't discuss prices, discounts, claims or contract changes.
[ ] Don't send any document that is not on the shared list.
[ ] Don't message anyone who has not written to you or does not expect to hear from you.

Turn rules into examples

A rule such as do not promise dates is clearer with a sample. Add a line like: Logistics will confirm the truck slot today, and I have passed your request on. The agent learns the tone as well as the limit.

Add three or four examples for each phase of a project. Build, commissioning and service messages sound different, and the examples teach the difference.

Review the rules with the team

Rules go stale when projects and people change.

  • Read the list aloud at the monthly operations meeting.
  • Ask each topic owner whether the rule for their area still fits.
  • Add a rule after every close call and remove one that no longer applies.

FAQ

How many rules should an agent have?

Ten to fifteen clear rules are plenty to start. Too many make the instructions hard to follow, so keep the ones that protect safety, contracts and restricted documents.

Can the agent use first names and project shorthand?

Yes, if you give it the names and shorthand. Partners are known and few, so natural language that matches your project vocabulary makes replies feel like a colleague wrote them.

Where do these rules go?

Into the instructions you give your agent. Keep a copy for your team and review them regularly, because partners, projects and contacts change over time.

More free tools for rail vehicle builders and rebuilders

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