Spaces

First-reply checklist for railroad shipper and partner chats

This checklist shows what the first reply to a new shipper or partner message should include, so a car request or a status question gets a useful answer straight away. It is made for railroad 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 railroad are working. A plant manager wants to know if the empties will arrive before the Thursday load-out. A broker has a customer waiting on a pull. A first reply that is slow or vague sends them to the phone, or to another carrier.

Read each point and tick it if your replies already do it. Every point you cannot tick is a gap in how your team or your AI agent opens a chat. Print it for the customer service desk, or read it aloud at the start of a shift.

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

[ ] Greet them by name and say which railroad they reached.
[ ] Answer the question asked in the first line.
[ ] Ask which siding, plant or facility they mean.
[ ] Ask for car numbers or a booking reference if they have one.
[ ] Ask what day the car or the pull was expected.
[ ] Take a direct contact name and number for follow-up.
[ ] Share status only from your own tracking, marked as last known.
[ ] Say plainly who to reach for billing and for the yard office.
[ ] Pass anything about safety or an incident to a person at once.
[ ] End with one clear next step and a time to expect it.

What a strong first reply sounds like

Picture a good customer service clerk at a short line. They say hello, answer the point, and ask for the one detail they need. In chat that might read: Hi, this is {business}. I can help with your car request. Which siding is it for, and what day did you need the empties?

That reply is short, it names the next detail, and it sounds like a person who knows the railroad. Anything longer starts to bury the question the shipper asked.

Slips that cost you goodwill

These are the mistakes that show up most often in freight chats.

  • Quoting a car location as certain when it is the last reported position.
  • Asking six questions in one message, so the shipper gives up and phones.
  • Promising a switch time that belongs to the dispatcher or the crew.
  • Treating a blocked crossing report like a normal customer question.

FAQ

How quickly should a railroad reply to a shipper message?

As fast as you can with a short, useful answer. Shippers plan loading around your service, so a quick reply that says what you are checking beats a long one sent after the shift ends.

Can the first reply say where a car is?

Only if your agent can read your own car tracking. Even then it should call the position the last known one and offer a person for anything that looks wrong or late.

What if the person writing is a neighbour and not a customer?

Be kind, take the details and pass them to a person. Do not promise a fix or a time, and treat any crossing or safety report as urgent.

More free tools for railroads and short lines

Read the guide: An AI agent for rail transportation: line-haul and short line railroads and their shippers.