Spaces

Hand-over notes for hosting and data processing support teams

These hand-over notes show hosting and data processing teams what an AI agent should write when it passes a chat to a person. Add the customer and the service, then copy the note that fits the situation.

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 goes with it. When a technician opens a chat and must scroll through twenty messages to find the problem, the customer waits longer and gets angrier. A short, clear note lets the person start helping at once.

Fill in the customer and the service, then copy the note that matches the situation. A good note says who is writing, what they asked, what the agent has said and what has not been promised. Keep copies where your agent and your team can see them, and update them as your needs change.

Outage or fault

Handover from [business]: [customer] reports a fault on [service]. Symptoms and start time are in the chat above. Nothing has been promised on fix time. Please take over and update the customer.

Billing dispute

Handover from [business]: [customer] disputes a charge linked to [service]. I explained our published rules and nothing more. No credit or refund was offered. Please review the account and reply.

Suspected security problem

Urgent handover from [business]: [customer] suspects unusual access on [service]. I have not shared any account details and have asked for none. Please verify identity and respond as soon as you can.

Request to change or delete

Handover from [business]: [customer] asked for a change to [service], such as a deletion or a contact update. Identity is not yet checked. Please verify who is writing before doing anything.

What every note should hold

Name the customer and the service, say what happened in one sentence, and state what has already been said. Most importantly, say what has not been promised. That keeps a technician from walking into a trap, such as a fix time the customer thinks was agreed.

Mark urgent matters clearly at the top. A suspected breach and a billing question should not look the same in a busy queue.

  • Customer and service in the first line.
  • What they asked, in one sentence.
  • What the agent said and did not promise.
  • What you need the person to do.

Keep customer data out of the note

A note should point to the chat, not copy account details, passwords or file contents. Anyone with access to the queue can read it, so write only what is needed to act.

FAQ

How long should a handover note be?

Three or four lines. A person should understand the case in ten seconds. The full chat is there for detail, so the note only needs to say who, what and what happens next.

Should the agent tell the customer about the note?

Yes, in one line. Say that a person has been given the details, so the customer does not have to repeat the story, and say roughly when they should hear back.

Where should the notes go?

To the person or desk that owns that type of case, such as the on-call engineer for faults and the accounts team for billing. Name the route in your agent's notes so it is never left to guess.

More free tools for hosting and data processing providers

Read the guide: Answer hosting and data processing customers in the chat they already use.