The call comes in on a Monday morning. A customer was promised a delivery date, then a callback, then a corrected invoice, and none of the three happened. The person who picks up the phone did not make any of those promises, cannot see why they were missed, and has no authority to fix the underlying problem. What they can do is say sorry, and they will say it, in some form, forty more times before lunch.
This piece looks at that role: the customer-facing employee who absorbs frustration on behalf of a system they do not control. It asks why the pattern is so common, what it costs the person and the business, and what would move the apology from the front line back to the place where the fault actually lives. It is a hypothesis about a recurring situation, not a description of any particular company.
An apology is a symptom
An apology on a service call is rarely about the person on the line. It is the visible end of a chain: an order system that does not update the delivery team, a finance process that issues invoices from stale prices, a follow-up that depends on someone remembering. By the time the customer is angry, the fault is several steps back, and the only person in reach is the one holding the phone.
Mellorca's pattern on customers who know their order is late before the team does describes the information gap that sets this up. When the customer learns about a problem first, the service agent starts the conversation already behind, and the apology becomes the only tool available.
What the research says about effort and loyalty
A well-known Harvard Business Review article, "Stop Trying to Delight Your Customers", argues that customer loyalty is driven more by how little effort it takes to get a problem solved than by how impressive the service feels. Its practical lesson is that companies should reduce the work customers must do, such as repeating details, being transferred, or chasing for updates. That is mainly a lesson about systems and processes, not about friendliness. An agent can be warm and still unable to help if the system gives them nothing to work with.
The same point works from the employee's side. Gallup's burnout research identifies unmanageable workload, unclear expectations, lack of manager support and unfair treatment as leading causes of exhaustion. A role that consists of taking responsibility for decisions made elsewhere, without any power to change them, is a textbook case of unclear expectations paired with unfairness. The person is accountable for an outcome they cannot influence.
The World Health Organization's guidance on mental health at work adds that excessive workloads, unclear job roles and lack of control over job design are risk factors for poor mental health. A front-line job with a rotating queue of upset customers, and no ability to fix the cause, combines several of these at once.
An illustrative case
Consider an illustrative example, not a real case: a Cape Town furniture retailer with a support team of six. Orders are captured in one system, deliveries scheduled in a spreadsheet maintained by the warehouse, and customer notes kept in a shared inbox. When a delivery slips, nothing tells the support team. They learn of it when the customer phones.
Every Friday the same five or six complaints arrive: a delivery date nobody confirmed, a payment taken twice, a promised call-back that never came. The agents apologise, take notes, and email the warehouse. The warehouse replies on Monday. By then the customers have phoned again, and the agent who took the first call is on leave.
The team's manager sees a high call volume and a drop in satisfaction scores, and responds with a training course on empathy and de-escalation. The agents find it faintly insulting. They already know how to be kind; what they lack is an answer to give.
The human tax: dignity and energy
The first cost is dignity. Being asked repeatedly to apologise for things you did not do, and cannot fix, can feel like standing in front of a problem to absorb the blame for it. Over time it can wear down the sense that your job is skilled work, and replace it with a sense that you are a buffer.
The second is energy. Emotional labour is real labour: staying calm with someone who is shouting, rephrasing a refusal for the sixth time, and holding back the obvious reply ("I agree, it is a mess") all consume attention that is then unavailable for the rest of the day. When the same causes produce the same calls week after week, the effort has no end point, because nothing improves.
Customers pay as well. They can tell when the person they are speaking to is reciting a script. The earlier article on why customers want to talk to someone who knows them explains why a person who can see the customer's history and act on it is worth more than one who can only sympathise. A related situation, the customer who gets a different answer from every person, shows the same root cause from the customer's side.
What could realistically change
The apology is cheap to give and expensive to receive. The way to reduce it is to make fewer things apology-worthy, and to give the person on the line something more useful to say.
- Tag the reasons for every complaint. For a month, record the cause of each contact in a short fixed list: late delivery, billing error, no callback, wrong information. The top three causes usually account for most of the volume.
- Send the information to where the customer will ask. If a delivery will be late, the support team should see it before the customer does. A shared status the whole team can read removes much of the guesswork. The article on why customers have to ask what is happening sets out the idea of proactive updates.
- Give the front line a defined authority. A small, clear limit, such as the ability to reissue an invoice or arrange a re-delivery up to a set amount without escalation, turns an apology into a fix.
- Carry complaints back to the owner of the fault. Hold a short weekly review where the top causes are presented to whoever owns that part of the process. Google's engineers describe a similar practice in their writing on blameless postmortems: the aim is to fix the system, not to find a person to blame.
- Reduce repeated explanations. Capture the customer's story once, and keep it where the next person can see it. The cost of repetitive customer questions falls on customers and staff alike.
The business outcome
Fewer repeat contacts, shorter calls and a support team that spends more time resolving than apologising. The business also gains a source of reliable information about where its processes fail, because the people who hear about every failure now have a route to report it.
The human dividend
The dividend is predictability: a working day in which the next call is less likely to be a repeat of the last, and in which the person answering knows what they can offer. It also restores some dignity, because an agent who can say "this is what will happen, and by when" is acting as a professional rather than absorbing blame. Not every agent will want to stay in the role, and a better system does not make the work easy. It makes it more honest.
The trade-offs
- Delegated authority carries risk. Giving agents the ability to refund or reissue will occasionally be misused or applied inconsistently.
- Root-cause fixes take time. Complaint volumes may stay high for months while upstream processes are repaired.
- Some apologies remain right. A sincere acknowledgement still has value, and the aim is to stop it being the only response, not to ban it.
- Other teams must take part. If warehouse or finance staff do not respond to complaints reported to them, the front line is no better off.
Why it matters
A business that asks its front line to apologise for faults it will not fix is spending its people to cover for its systems. The remedy is mostly unglamorous: better information, clearer authority and a feedback route to the people who can change the process. It gives customers a quicker answer and gives staff a role they can respect.
Sources and further reading
- Stop Trying to Delight Your Customers (last verified 10 October 2026)
- Employee Burnout, Part 1: The 5 Main Causes (last verified 10 October 2026)
- Mental health at work (last verified 10 October 2026)
- Google SRE - Blameless Postmortem for System Resilience (last verified 10 October 2026)
Related Mellorca reading
- When Your Best Work Is Invisible Because It's Repair Work
- The Manager Who Can't Act Without the Founder
- The Owner Who Can Finally Say No to Work