Spaces

Hand-over notes for machinery repair chats

These hand-over notes show what an AI agent should tell your dispatcher or engineer when it passes on a chat: the site, machine, fault, urgency and what the customer was told.

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

Before you start

When a chat moves from your agent to a person, the handover note decides how fast the person can act. A good note lets your dispatcher pick up without asking the customer to repeat anything. A poor one sends everyone back to the start, which hurts most when a line is down.

Fill in the customer and site, the machine and fault, and what the customer was told, then copy the note that matches the situation. Agree one fixed shape for your firm so every handover reads the same and can be scanned in seconds.

Urgent fault for dispatch

Urgent for [business] dispatch. Customer: [customer]. Machine: [machine]. The customer was told [next step]. Please confirm the visit and message them directly.

Safety concern for the engineer

Safety flag at [business]. Customer: [customer]. Machine: [machine]. The agent gave no advice and told the customer to keep clear. [next step]. Please call them now.

Quote request for the manager

Quote request for [business]. Customer: [customer]. Machine: [machine]. The customer was told [next step]. No price was given. Please arrange an inspection and written quote.

Complaint for the owner

Complaint for [business]. Customer: [customer]. About: [machine]. The customer was told [next step]. The agent made no promises about cost or blame. Please call back with a plan.

What a good note holds

Lead with the urgency, then who and where, then what and when. A technician reading it on the way to a van should know the site, the machine, the fault code and the promise made before the engine is started.

State plainly what was not said. If the agent gave no price or no safety advice, write that. It stops a person from assuming something was promised.

  • Urgency first: urgent, same day or routine.
  • Customer, site and the person to ask for.
  • Machine, fault and any error code.
  • What the customer was told, and what was not.

Make it a habit

Check the notes in your weekly review. If dispatch keeps asking the same follow-up, add that question to the intake.

FAQ

Where should the note go?

To the person on call, in the place they already look, such as your team chat or the dispatcher's phone. A note nobody sees is the same as no handover.

How long should the note be?

Four or five short lines. If a technician needs more than a glance to understand it, the note is too long.

Should the customer see the note?

The customer should see only what the agent said to them. The note is an internal summary, though it should be honest and respectful in case it is ever read aloud.

More free tools for industrial machinery repairers

Read the guide: Take fault reports and service requests for machinery repair.