When a customer calls a business a second time about the same matter, they are rarely asking for something exotic. Most of the time they want the person on the other end to already have the thread: what was agreed, what was promised, what happened since. They want to talk to someone who knows them well enough that the conversation can start in the middle rather than at the beginning.
This piece looks at why that preference seems so durable, what it actually requires from a small or mid-sized South African business, and what it costs the people on both sides of the call when it is missing. It is a reasoned hypothesis about human connection in customer follow-up, not a finding, and it is offered with that status.
What "knowing a customer" does and does not mean
It is easy to hear "someone who knows them" and picture a shopkeeper who remembers your name, your children and your usual order. That kind of familiarity is lovely where it exists, but it is not what most customers are asking for in a follow-up conversation, and it is not what a growing business can promise at scale.
In practice, knowing a customer in the sense that matters during follow-up is much more modest:
- Knowing that the customer has already explained their situation, and not asking them to do it again.
- Knowing what was promised, by whom and by when.
- Knowing the history that changes the right answer, such as a previous complaint, a special arrangement or a delivery that went wrong last month.
- Knowing how the customer prefers to be reached, where they have said so.
None of this requires intimacy, and Mellorca does not want to manufacture it. It requires continuity. A person, or a team, that can pick up where the last conversation stopped has given the customer something real: the sense that they were listened to the first time.
Why the preference is so persistent
There are at least three plausible reasons customers keep gravitating towards someone who already has the context. They are reasoned, not measured, so treat them as hypotheses.
Repeating yourself feels like a small indignity. Having to re-explain a problem tells the customer that the earlier explanation did not matter. The cost of one repetition is minor; the cost of the third is a different feeling altogether. Mellorca's article on the time tax of re-explaining the same thing describes the staff-side version of the same effect.
Context lowers the effort of trust. When the person you speak to already understands your situation, you do not have to check whether they have understood it.
Presence signals priority. A reply that refers to the specific order, the specific quote or the specific date tells a customer they are being dealt with as an individual rather than as a ticket in a queue.
Research from large software vendors points in the same general direction. Salesforce's State of the Connected Customer series surveys customers about what they expect from the companies they deal with. This is vendor research, so treat it as indicative; the recurring theme is that people expect organisations to treat them as individuals and to work from a consistent picture of the relationship.
Where follow-up breaks down
Follow-up is the stage where this goes wrong most visibly, because it depends on something being remembered across time and across people. A few typical breakdowns:
- The conversation lives in one person's inbox or phone, and that person is on leave, in a meeting or has left the business.
- Notes are kept, but in a place the next person does not look: a notebook, a personal WhatsApp thread, a spreadsheet tab.
- Several people each hold part of the picture, so the customer is given a slightly different answer by each.
- The follow-up that was promised is remembered by nobody, because it was only ever held in someone's head.
The last of these is the most corrosive, because it turns an ordinary courtesy into a broken promise. Mellorca's piece on the customer who gets a different answer from every person covers the second-last. The financial side of disconnected records is explored in the analysis of customers repeating information across disconnected records.
An illustrative scenario
Consider a hypothetical example, not a real business: a Gauteng supplier of commercial kitchen equipment with eleven staff. A restaurant owner ordered a replacement extraction fan, was told it would arrive in ten working days, and was also told that a technician would call to confirm the installation slot.
On day eight the owner phones. Whoever answers has no record of the installation call, cannot see the supplier's delivery date, and asks for the order number and the history of the order. The owner explains it all again. A colleague later says the technician was meant to call, but that was a verbal arrangement between the salesperson and the workshop.
No one in this scenario is negligent. Each person did their own part reasonably. What is missing is a shared place where the promise, the date and the history sit together, so that whoever picks up the phone is, for practical purposes, the person who knows the customer.
What it takes to be that person
The aim is not to make everyone a relationship manager. It is to make the knowledge portable, so that it does not depend on a particular person being at their desk.
- One shared record per customer or per job. Notes, promises and dates in a place everyone who deals with the customer can see. A customer relationship management (CRM) system is one way to do this; Wikipedia's overview of customer relationship management describes such systems as ways of recording and analysing interactions across the customer lifecycle. A well-kept shared spreadsheet or job-card system can achieve the same for a small team.
- Record promises, not just conversations. A line such as "technician to call by Thursday" is far more useful than a transcript of the call.
- Give each follow-up an owner and a date. A promise with a name and a date gets kept; a promise with neither tends to evaporate.
- Make the first lookup quick. If finding the history takes longer than the customer's patience, the benefit is lost. Mellorca's discussion of the half-hour lost to finding the right file is relevant here.
- Keep the human part human. The record exists so the person can listen, not so that they can read from a screen. The best use of a good record is to spend the first thirty seconds of a call on the customer instead of on the lookup.
A note on personal information
Keeping customer records is also a legal matter in South Africa. The Protection of Personal Information Act (POPIA) requires that personal information be collected for a specific, lawful purpose and that what is held be adequate, relevant and not excessive for that purpose. The Information Regulator publishes its own guidance on POPIA.
This shapes what "knowing a customer" should include. Notes that help serve the customer, such as an agreed delivery window or a past complaint, are in scope. Speculation about a customer's personal circumstances, or details collected merely because they might be useful some day, are not. Being known should feel like being remembered, not like being profiled.
The human dividend
The dividend is presence: the experience, for the customer, of being met by someone who is paying attention to their situation, and for the staff member, of being able to give that attention without scrambling for context. It also restores a measure of dignity to both. The customer is not made to prove their history, and the employee is not put in the position of apologising for a gap they did not create.
The trade-offs
- Record-keeping takes discipline. A shared record only helps if people update it, and updating it is extra work in the moment.
- Systems can replace attention instead of supporting it. Reading a note aloud is not the same as listening.
- More data means more responsibility. Under POPIA, every extra detail held about a customer is something the business must protect and justify.
- Not every customer wants to be known. Some prefer a quick, impersonal transaction. Continuity is a choice a business offers, not a duty customers must accept.
Why it matters
Customers want to talk to someone who knows them because it spares them effort and tells them they were heard. Businesses want the same thing for different reasons: fewer repeated explanations, fewer dropped promises, and calmer days for the people who answer the phone.
The two meet in a modest piece of operational design: keep what matters about each customer in one agreed place, give promises an owner, and make the lookup quick enough that the conversation can be about the customer. That will not create loyalty by itself, but it removes one of the most avoidable reasons for losing it.
Sources and further reading
- State of the AI Connected Customer (last verified 10 October 2026)
- Customer relationship management - Wikipedia (last verified 10 October 2026)
- Protection of Personal Information Act 4 of 2013 - South African Government (last verified 10 October 2026)
- Who makes an application to process Special Personal Information? (last verified 10 October 2026)
Related Mellorca reading
- Why Self-Service Can Feel Like Respect
- Why the Person Closest to the Problem Can't Fix It
- The Founder Who Wants to Step Back but Can't