Spaces

Hand-over notes from your software agent to your team

These hand-over notes show what an AI agent should write for a staff member when it passes a software chat on: product, version, steps tried and what the customer needs. Use them to brief the agent.

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

Before you start

When a chat reaches an engineer, the worst start is asking the customer to repeat everything. A good hand-over note gives the engineer the product, the version, the error, the fixes already tried and the customer's mood, so they can reply with something useful.

Fill in the two boxes and pick the note that fits the situation. Copy the shape into your agent's instructions, so every hand-over reads the same way. Staff learn to scan a consistent note in a few seconds.

Crash or install fault

Hand-over for [business]: [customer name] reports a fault in [details]. Known fixes were tried and did not work. Please contact them in this chat with next steps. They are polite but losing work time.

Security report

Urgent for [business]: [customer name] has reported a possible security issue, details: [details]. The agent only acknowledged receipt and discussed nothing else. Please contact them privately and log the report.

Billing or refund question

Hand-over for [business]: [customer name] has a billing question about [details]. The agent made no promises. Please check the account and reply in this chat with a decision on any refund.

Lost data or privacy request

For [business]: [customer name] has lost data or asked about personal data, concerning [details]. The agent gathered the account email and promised nothing. Please take over and reply soon.

Larger company enquiry

Sales hand-over for [business]: [customer name] asked about a team purchase, relating to [details]. The agent explained published editions only. Please follow up about seats, pricing and any contract needs.

What an engineer needs in ten seconds

Product and version, system, the error as the customer wrote it, what was tried and how the customer feels. If your notes capture those five things, the engineer can answer the person without asking anything again.

Add the customer's own words in quotation marks when they matter. A direct line like it crashes every time I open a project tells more than a paraphrase.

Keeping hand-overs clean

A messy note wastes the time the hand-over was meant to save.

  • Put the most urgent fact in the first line.
  • List the steps already tried, so nobody repeats them.
  • Say what the agent has promised, which should be nothing risky.
  • Name who the chat is for, not just the team.

FAQ

Where does the hand-over note go?

It goes to the person on your team who takes the chat, inside the same conversation or in your usual tool. Staff see the full history, so they can reply without asking again.

Should the customer see the note?

Not usually. The customer sees a short message saying a colleague is taking over. The detailed note is for staff, written in plain, factual language.

How long should a note be?

Five to eight lines. Lead with the urgent fact, list the steps tried and finish with what the customer needs. Longer notes tend to be skimmed or skipped.

More free tools for software publishers and app makers

Read the guide: Answer software customer messages before they become tickets.