Spaces

Hand-over notes your AI agent leaves your team about a user chat

These hand-over notes show what an AI agent should leave a teammate when it passes a chat at a software company: who the user is, the problem, what was tried and what is needed next.

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

Before you start

Nothing annoys a user more than being handed to a person and then asked to explain everything again. A good hand-over note carries the whole story: who they are, what is wrong, what has been tried and what they were told. Your teammate then starts from step three, not step one.

Fill in who receives the hand-over and the usual deadline. Copy these formats into your agent's instructions, so every hand-over is written the same way. The same layout also helps your team scan a queue of chats fast.

Billing or refund

Handing to [teammate] for [business]: user asks for a refund on a charge they say they did not expect. I explained our policy only. They were told to expect a reply [reply by]. Please decide and reply.

Bug report

Handing to [teammate]: user reports their export fails with an error on large workspaces. I suggested a smaller date range, which did not help. They expect an update [reply by]. Screenshot is in the chat.

Security worry

Urgent for [teammate]: user says they saw a login they do not recognise on their [business] account. I asked for nothing else and shared no details. They were told a person will reply [reply by].

Sales question

Handing to [teammate] at [business]: team of about thirty asking about a custom plan and single sign-on. I shared the pricing page link only. They were told to expect a reply [reply by].

What a good note contains

Four things: who the user is, what they want, what the agent already said or did, and what the user was promised. If a note has all four, the teammate can write a useful reply in a minute.

Keep notes factual and short. Do not let the agent guess at causes or blame. 'Says export fails' is better than 'probably a server bug'.

  • Who: name, plan or workspace if known.
  • What: the problem in one line.
  • Done: what the agent said or tried.
  • Promise: what the user expects and by when.

FAQ

Why does a hand-over note matter so much?

Because it saves the user from repeating themselves and saves your teammate time. A clear note often means the first human reply already solves the problem, not just asks a question.

Should the user see the note?

Usually not, it is for your team. The user should instead be told plainly who will pick up their chat and roughly when, in a short message in the chat itself.

Can the agent decide whom to hand over to?

Yes, if you write simple rules, such as billing to one person and bugs to another. Keep the rules short, and name a fallback person in case the first one is away.

More free tools for software companies

Read the guide: Answer your users' messages with an AI agent.