Customer Service

Phone Calls Recorded on Notepads: The Cost of Incomplete Customer Records

When what customers say on the phone ends up on notepads, sticky notes and personal phones instead of a shared record, follow-ups are missed, work is duplicated and customers repeat themselves.

Mellorca Impact2026-10-06

The tolerated pain: the conversation leaves no trace

For many South African small and mid-sized businesses, the phone is still where much of the real business happens. A customer calls to change a delivery address. A supplier phones to say stock will be late. A client agrees a price change verbally. Someone rings to complain, to book, or to ask a question that will need a follow-up.

The information from those calls often goes nowhere useful. It is written on a notepad, a sticky note or the back of an envelope. It is typed into a personal phone or remembered until later. Sometimes it is copied into the CRM, job system or spreadsheet at the end of the day, and sometimes it is not. When the information does reach a shared system, it is often typed twice: once in rough notes during the call and again when someone has time.

This is related to, but different from, the experience of customers repeating information because records are disconnected. There, the records exist in separate systems. Here, the record of the call often does not exist at all.

Why businesses tolerate it

  • Calls are fast and systems are slow. Opening the right screen during a call feels awkward, so people write on paper and intend to capture it later.
  • The person who took the call remembers. As long as they are available, nothing seems lost.
  • There is no obvious place to put it. Calls from suppliers, prospects and existing customers may each belong in a different system.
  • Logging calls feels like admin for its own sake. Without a clear use for the record, staff do not see the point.

Operational consequence

  • Missed follow-ups. A promised callback, quote or credit note depends on a note that may be lost.
  • Customers repeat themselves. When they call again and speak to someone else, nobody can see what was said.
  • Duplicated administration. Notes are written during the call and retyped later, or two people capture the same call in different places.
  • Conflicting instructions. A change agreed by phone never reaches the people doing the work, who continue on the old basis.
  • Disputes without evidence. When a customer says "but I told you on the phone", there is nothing to check.
  • Knowledge walks out. When a staff member leaves, the history of their customer conversations leaves with them.

The underlying pattern is the same one seen when business knowledge lives in inbox history, except that phone conversations are even less searchable than email. The result is that customer service becomes what Mellorca describes as a human search engine.

How the pain becomes money

  1. Double-capture labour: notes written during the call and retyped afterwards.
  2. Search labour: time spent asking colleagues or hunting for notes to find out what was agreed.
  3. Missed follow-up cost: lost orders, late quotes and complaints caused by callbacks that never happened. Measure these from complaints and an audit of promised actions.
  4. Rework from unrecorded changes: deliveries to old addresses, work done to the old specification, prices charged at the old rate.
  5. Dispute cost: credits conceded because the business cannot show what was said.

An illustrative cost model

The figures below are illustrative assumptions for an unnamed South African business with a small sales and service office. They are not benchmarks. Replace them with your own counts from a two-week sample.

Activity (illustrative)AssumptionMinutes per month
Retyping call notes into a system360 calls × 3 minutes1,080
Finding out what was said on earlier calls120 searches × 6 minutes720
Recovering missed follow-ups14 incidents × 30 minutes420
Rework from unrecorded changes6 incidents × 60 minutes360
Total2,580

2,580 minutes is 43 hours a month. At an illustrative loaded cost of R240 an hour, that is R10,320 a month, or R123,840 a year, before any lost orders, credits or wasted deliveries. Those direct costs should be added from actual incidents: the cost of a redelivery, the value of a credit conceded, or the margin on an order that went to a competitor after a missed callback.

Secondary consequences

Paper notes and personal phones also create a data-protection problem. Call notes often contain names, phone numbers, addresses, account details and sometimes health or financial information. The Protection of Personal Information Act requires a responsible party to take reasonably practicable steps to keep personal information complete, accurate, not misleading and updated where necessary. Details scattered across notepads and personal devices are hard to keep accurate, hard to secure and hard to delete when no longer needed.

Managers also lose visibility. Without a record of calls, they cannot see how many enquiries arrive by phone, how many become sales, or which customers are calling repeatedly with the same unresolved issue.

When this becomes commercially urgent

  • Customers complain that nobody called back, or that they had to explain everything again.
  • Disputes about what was agreed by phone are becoming more frequent or more costly.
  • Work has been done or goods delivered on outdated instructions.
  • A key salesperson or administrator is leaving, taking their call history with them.
  • Phone volume is growing and more people are answering calls.

What better looks like

In a better state, every call that changes something or creates a commitment is recorded once, against the right customer or supplier, in a shared system, ideally during the call or straight after it. The record captures who called, when, what was agreed and what happens next, with a follow-up task and an owner where needed.

Most customer and business systems already support this. HubSpot's knowledge base, for example, describes logging calls on a record with a call outcome, direction, type, date and time, and associating one call with several related records so that it appears on each record's timeline. Microsoft's Business Central documentation describes recording interactions such as phone calls, emails, meetings and letters against contacts using interaction templates, and viewing them on an interaction log. Telephony systems that integrate with a CRM can go further, creating the call record automatically so staff only add the substance.

The design challenge is making capture faster than the notepad. Short templates, a few required fields and a follow-up option usually work better than long forms that staff will avoid.

Trade-offs to weigh

  • Not every call needs a record. Define which calls must be logged, such as changes, commitments, complaints and quotes.
  • Call recording raises separate issues. Recording audio involves consent, notification and retention decisions that should be taken deliberately.
  • Adoption depends on usefulness. If nobody reads the call log, staff will stop writing in it.
  • Integration has running costs. Telephony and CRM integrations need licences and someone to maintain them.

Practical diagnostic

  1. For two weeks, ask everyone who takes calls to tally calls that created a commitment or changed something.
  2. Count how many of those reached a shared system, and how long after the call.
  3. Review complaints and credits for the last quarter and note how many involved something said on the phone.
  4. Pick three regular customers and check whether a colleague could reconstruct their last month of calls from the system alone.
  5. Agree a short list of call types that must be logged, and test a two-minute logging template.

The cost of requests that disappear in shared channels is examined further in the cost of customer requests lost in a shared inbox.

The bottom line

Information from phone calls that never reaches a shared system costs the business twice: once in duplicated capture and searching, and again in missed follow-ups, rework and disputes it cannot settle. Recording each important call once, against the right record, turns private notes into shared knowledge that the whole team can act on.

Sources and further reading

Related Mellorca reading

Article summaryWhen what customers say on the phone ends up on notepads, sticky notes and personal phones instead of a shared record, follow-ups are missed, work is duplicated and customers repeat themselves.