Spaces

Hand-over notes for engineers and sales when an agent passes a chat on

These hand-over notes show what an AI agent should write for your engineer or sales team when it passes a chat on. They hold the part, quantity, date and the customer ask, so no one has to start again.

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

Before you start

A handover is only as good as the note that travels with it. If your engineer opens a chat and finds a long thread with no summary, they will ask the customer the same questions again. The customer will then feel they have been passed around, and you lose time you did not have.

Fill in the customer, the part or order and how urgent the matter is, then copy the note that matches the type of handover. Notes like these help your agent too, as they show the structure a good handover should have, with facts first and nothing guessed.

Design question for an engineer

Handover from the agent at [business]. [customer] asked a design question about [part]. They need an engineer to advise. Urgency: [urgency]. Datasheet already sent.

Quality problem

Quality handover for [business]. [customer] reports a problem with [part]. Lot code, quantity and symptoms are in the chat. Urgency: [urgency]. No cause or remedy was given to the customer.

Quote request

Quote handover at [business]. [customer] asked for a price on [part]. Quantity and delivery date are in the chat. Urgency: [urgency]. No price was given by the agent.

Order or shipment issue

Order handover from the agent. [customer] is asking about [part] at [business]. Status was checked and the customer was told a person will reply. Urgency: [urgency].

Export or contract question

Handover for [business]. [customer] asked a question about export, origin or terms on [part]. The agent made no statement. Urgency: [urgency]. Please reply personally.

What every hand-over note should hold

Who the customer is and what they asked, in one line. The part or order number. What the agent already told them. What the agent could not or should not answer. How urgent it is and when the customer expects a reply.

The last point is the one most often forgotten. A customer told a person will answer today needs that person to know it.

Keeping notes useful

Check a few notes each week.

  • Could someone act on the note without opening the whole chat?
  • Did it say what the agent had already promised the customer?
  • Was the urgency clear enough to put the chat in the right queue?

FAQ

How long should a hand-over note be?

Three to five lines is usually enough. It should let an engineer or salesperson understand the situation in seconds, with the full chat there for anyone who wants more detail.

Should the note say what the agent told the customer?

Yes. Your team must know what has already been said, especially promises about timing, so they do not contradict it. Also note what the agent deliberately did not say.

Who should receive the note?

Route by topic: engineering for design, quality for failures, sales for quotes and orders. A named backup for each topic means nothing is lost when someone is away.

More free tools for electronic component makers

Read the guide: Answer engineer and buyer messages for electronic component makers.