# Phone Message Template: 9 Fields Every Note Needs

> A useful phone message records the date and time, who it's for, the caller's name and company, a callback number that was read back, the reason for the call in one sentence, how urgent it is, a callback deadline, the initials of whoever took it and a space to mark it done. Below is a template you can copy for paper, email or chat.

- URL: https://virtuelle-sekretaerin.de/en/office-admin/phone-message-template/
- Language: en
- Updated: 2026-10-19
- Publisher: Virtuelle Sekretärin (OnlineBuilders LLC, https://onlinebuilders.biz)

The most common flaw in phone messages isn't bad handwriting. It's the missing callback number. "Mr Patel called, please ring back" says the note, and there are three Patels in the customer list, none of them with the mobile number he's on today.

A template fixes that because it asks the questions for you. Whoever picks up just works through the fields instead of guessing what might matter.

## The nine fields of a good phone message

**Fields every phone message needs**

- [ ] **Date and time** of the call
- [ ] **For**: who the message is for
- [ ] **Caller**: name, company, account number for existing customers
- [ ] **Callback number**, read back and confirmed
- [ ] **Reason for calling** in one sentence, ideally in the caller's words
- [ ] **Urgency**: now, today, this week
- [ ] **Call back by**, or when the caller is reachable
- [ ] **Taken by** (initials)
- [ ] **Done**: when, by whom, outcome in a few words

The last field is the one most often left off, and for teams it matters most. Without a done marker, either nobody calls back because everyone assumes someone else did, or two people call.

## Template to copy

This works printed on a pad, as a text snippet in your email client or as a pinned template in a team chat:

```text
PHONE MESSAGE
Date / time:     ____________   For: ____________
Caller:          ____________   Company: ____________
Account no.:     ____________
Call back on:    ____________   (read back: yes / no)
Reachable:       ____________
Reason:          ______________________________________
Urgency:         [ ] now   [ ] today   [ ] this week
Call back by:    ____________
Taken by:        ____________
Done on:         ________ by: ______ outcome: __________
```

For email, a fixed subject line pays off because you can filter on it: "Callback / name / topic / by time". For example: "Callback / Patel, Patel Roofing / gutter quote / today 4 pm". The inbox then shows at a glance what's urgent.

## Phrases that fill the fields

Fixed sentences make the fields easy. Nobody has to work out how to ask for a number politely.

> "What's the best number for Sarah to reach you on?"
> "Let me read that back: oh-seven-seven-oh-oh, nine-oh-oh, four-five-six. Is that right?"
> "Can I note briefly what it's about, so Sarah can prepare?"
> "When would you need to hear back by?"
> "How do you spell your surname? Is that P-A-T-E-L?"

Reading numbers back in groups isn't ceremony. It catches exactly the transposed digits that otherwise surface only when the callback fails. For names, the international spelling alphabet helps: Alfa, Bravo, Charlie, Delta, and so on through to Zulu. It's what airlines and the military use, and most callers recognise it.

## What a finished message looks like

Here's an example from an architecture practice, to show how short a good message can be. The number is from the range Ofcom reserves for drama, so it reaches nobody.

> **14 Oct, 10:42, for Sarah.** Raj Patel, Patel Roofing, account 2231. Call back on 07700 900456 (read back). Reachable today until 5 pm. Reason: structural engineer needs the revised garage drawings before Friday. Urgency: today. Taken by: MK.

Seven lines, no wasted words. Sarah knows whom to call, what about and by when. She can open the drawings before she dials.

## Common mistakes and special cases

Most unusable messages fail in the same places:

- no number, or only a landline when the caller is out on site
- "please call back" with no reason, so the return call starts with a question
- no time, when the call was about a deadline
- abbreviations only the person who wrote them understands
- a note left on the desk of a colleague who's on holiday

Three kinds of call deserve their own rule. With complaints, add the caller's mood in one word, such as "annoyed", so the callback doesn't walk in blind. With emergencies the message comes second: transfer or call immediately, write afterwards. And when the press, the other side's lawyer or a regulator calls, nobody gives information on the phone. Take the details and the reason, nothing more.

## Holidays and cover

Messages for someone who's away are the second most common reason callbacks get lost. Decide who covers each person's messages during absence, and put both names in the "for" field, say "Sarah, cover: Tom". Tell the caller that the cover will be in touch, and by when. Obvious, yes. In practice it's exactly where customers drift away after waiting a week for a call that never comes.

## Paper, email or a system?

Where the message lands decides its usefulness more than what's on it.

**Where phone messages work best**

| | Notepad | Email or chat | CRM or helpdesk |
|---|---|---|---|
| Ready to use immediately | yes | yes | no |
| Available on the move | no | yes | yes |
| Done status visible to everyone | no | partly | yes |
| Linked to customer history | no | no | yes |
| Privacy risk from loose slips | yes | no | no |
| Best for | one person | small teams | teams with many calls |

My take: the notepad is unbeatable for speed, but only while one person takes all the calls and makes all the callbacks. As soon as two people are involved, messages belong in a shared place. A dedicated "callbacks" chat channel is the best compromise for most small teams. If you already run a CRM, log the message there as an activity on the contact.

## Privacy: what stays off the note

Phone messages contain personal data. Under the GDPR and UK GDPR, the principles of data minimisation and storage limitation in Article 5(1) apply. In practice: write down only what the callback needs, and delete or shred the message once it has done its job.

Details the caller volunteers are the tricky part. In a medical practice, symptoms are health data, and in the US they may be protected health information under HIPAA. In a law firm, the mere fact of a consultation can be confidential. Keep the note to the essentials, such as "question about appointment" rather than a diagnosis. A sticky note on a monitor any visitor can read is a real risk in those settings.

If an outside service answers your calls, messages usually arrive by email and the same applies at the provider's end; the piece on [answering services for contractors](https://virtuelle-sekretaerin.de/en/phone-answering/answering-service-contractors/) shows a message layout for job enquiries.

## When the message writes itself

Answering services and AI receptionists now deliver messages automatically in a fixed format. An AI assistant captures the key details and sends a summary straight after the call, as described in [how an AI receptionist works](https://virtuelle-sekretaerin.de/en/ai-phone-agents/ai-receptionist-how-it-works/). Even then, it's worth giving it the fields from this template, so messages from every source look the same. If you want those summaries landing directly in your own CRM, assistants with that kind of integration are something [OnlineBuilders builds](https://onlinebuilders.biz/solutions/ai-bots).

For a new [virtual secretary](https://virtuelle-sekretaerin.de/en/office-admin/virtual-secretary/), the template is also a good first handover document. It shows in a minute which details you care about.

Print the template today or save it as a snippet, and use it for every call for a week, your own notes included. On Friday, count how often the "call back on" field would have stayed empty if it hadn't been on the form.

## FAQ

### How long should I keep phone messages?

As long as you need them for their purpose. Once the call is returned and anything important is in the customer file or CRM, the message can go. Paper notes belong in the shredder, not the recycling bin.

### Does a phone message count as evidence?

It can support your side in a dispute, especially if it was written at the time with a timestamp and initials. It doesn't replace a written agreement, so confirm anything important agreed on the phone by email.

### Paper, email or software: which is best?

Whatever everyone on the team actually uses. A pad with a printed form works for one person. Once several people take calls, a shared digital place is better, because nobody hunts for slips and finished messages are visibly closed.

Photo: Jonathan Schilling, CC BY-SA 4.0 (https://commons.wikimedia.org/wiki/File:AT%26T_Bell_Laboratories_memo_of_call_pad.jpg)