Spaces

Hand-over notes for internet phone and small telecom chats

These hand-over notes give your engineer or account manager a clear summary when an agent passes on a telecom chat. They hold the service, the device, the time of the fault and what has been tried, so the customer does not repeat anything.

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

Before you start

A handover that lacks detail wastes the first ten minutes of the engineer's time and the customer's patience. "Customer has a phone problem" tells nobody anything. A good note names the account, the device, the symptom and the steps already taken, so the engineer can start working before saying hello.

Fill in the customer, the issue and the next step, then choose the note that fits the type of chat. Your agent can write the same layout every time. Consistent notes are quick to read, easy to search later and make it clear who owns the next move.

Fault for an engineer

Handover for [business]: [customer] reports [issue]. Already tried: [tried]. Please check the line and voice settings and reply to the customer in this chat today.

Number porting

Porting request at [business]: [customer] asks about [issue]. Details gathered so far: [tried]. A person must confirm identity and timing before anything is promised to the customer.

Billing question

Billing handover for [business]: [customer] raised [issue]. So far we have [tried]. Please review the account and reply, as the agent has made no promise about credits.

Emergency calling concern

Urgent at [business]: [customer] is concerned about [issue]. Checked so far: [tried]. Please contact the customer immediately. The agent gave no advice on emergency calls.

Upset customer

Handover at [business]: [customer] is upset about [issue]. We have already [tried]. Please call or write soon, and open with an apology. The agent offered no compensation.

What every note should hold

Think of the note as a message to a colleague who is about to walk into a conversation. Who is the customer, what is wrong, what has been tried, and what do they need from you now? If any of those is missing, the colleague has to go back and ask.

Add the customer's mood in a word if it matters. "Calm" or "very upset" helps the person choose their first sentence. Also note any promise the agent made, so that it is kept or politely corrected.

Keep notes useful

A short, repeatable layout works best.

  • Start with the customer and the service.
  • Put the symptom and the time in one line.
  • List what has been tried, in order.
  • End with the exact action you need from the person.

FAQ

How long should a hand-over note be?

Three to five lines. Enough that an engineer can act without scrolling through the whole chat, but short enough to read in half a minute while walking to a desk.

Should the note include the full chat?

The full chat should stay linked, but the note itself must stand alone. Most people read the note, then dip into the chat only to check a detail or the tone.

Who should receive the note?

The person named on your handover list for that type of chat, such as the engineer for faults or the account manager for billing. Name a backup so nothing waits for someone on leave.

More free tools for internet phone and small telecom providers

Read the guide: Answer set-up and call-quality questions for smaller telecom services.