Spaces

Hand-over notes for telecom staff taking over from your AI agent

These hand-over notes show what an AI agent should write for a team member when it passes a telecom chat over, so the customer never repeats the story. Add the team name and the customer detail you want first, then copy the one that fits.

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

Before you start

A hand-over is where telecom chats most often go wrong. The agent has spent ten minutes learning the problem, then the customer is asked to explain it all again to a person. That feels like a step backwards. A good note lets the team member pick up the thread with the first line they write.

Add the name of the team and the detail you want at the top of every note. Copy the format that fits the type of chat. Ask your agent to write notes in the same shape every time, so your team learns where to look and can scan a note in seconds.

Hand-over: fault after tried steps

For the [team]: customer reports a lasting fault at [business]. Key detail: [key detail]. The agent has already asked for a restart and a light check, and the problem remains. The customer wants a visit.

Hand-over: bill worry

For the [team]: customer is worried about a charge on a [business] bill. Key detail: [key detail]. The agent did not discuss the account. Please check identity and reply in this chat today.

Hand-over: number or SIM issue

For the [team]: customer wants help with a lost handset or number transfer at [business]. Key detail: [key detail]. The agent has taken no action and asked for nothing sensitive. Please verify identity first.

Hand-over: customer wants a person

For the [team]: customer asked to speak to a person about their [business] service. Key detail: [key detail]. The agent gave general help only. The customer sounds frustrated, so please reply quickly and warmly.

What a good note holds

Who the customer is, which service they are writing about, what they want, what the agent has already said and done, and the mood of the chat. Add anything the customer said that suggests urgency, such as a medical alarm or a business that cannot trade.

Keep it to five or six lines. A note that runs to a page will be skipped, and the whole point is to save the customer from repeating themselves.

  • Put the service and address first.
  • List the steps already tried.
  • Mark safety or vulnerability clearly.

What the note must not hold

Leave out passwords, PINs, full card numbers and guesses about the account. If the customer typed any of these by mistake, the agent should say so in the note so a person can advise the customer to change them.

FAQ

Who reads the hand-over note?

The team member picking up the chat. It appears in the same conversation, so they can see both the note and the full history, and reply to the customer without switching between systems.

Should the note include the agent's opinion?

A short line on the customer's mood and urgency helps. Keep facts and impressions apart, and avoid guesses about the cause of a fault or the status of an account.

How fast should a person pick up a handed-over chat?

Agree a time with your team, such as within an hour in opening hours, and tell the customer. Faster for safety worries. A promise the team cannot keep does more harm than a longer honest one.

More free tools for broadband, mobile and satellite providers

Read the guide: Answer customer messages for telecommunications providers.