A telephone handset resting on a notepad covered in dated handwritten notes and reference numbersThe Open Gazette

Legal

Getting Nowhere on the Phone? How a Complaint Actually Moves Through a Company

Frontline staff work from scripts with fixed authority limits. Understanding where the authority sits turns a repeated argument into a short escalation.

Rosa Petrossian5 min read

Ask anybody who has worked a customer service phone line what the hardest part of the job is, and it is rarely the angry callers. It is having the same conversation forty times a day with people asking for something the person answering has no ability to give them, under a script that does not permit saying so plainly. Understanding that constraint is not sympathy for the company; it is the single most useful piece of information a customer can have, because it tells you that the argument you are having is with the wrong person.

What the First Person Can Actually Do

Frontline representatives typically hold defined authority: a refund up to a stated amount, a fee waiver of a particular type, a limited number of goodwill gestures per period, a replacement under specified conditions. Outside those boundaries they cannot act at all, and the system they are working in usually will not let them enter a transaction they are not authorized for. No amount of persistence changes what the software permits. The practical consequence is that the first call should be short and diagnostic rather than persuasive. State the problem, state the outcome you want, and ask directly whether they are able to authorize it. That question is answered honestly far more often than people expect, and a plain no is genuinely useful information: it means the matter has to move, and it means nothing further will be achieved by explaining the situation more thoroughly to the same person.

The Escalation Path, Which Is Shorter Than It Looks

Above the frontline sits a supervisor with broader limits, and above that a resolution or retention team that exists specifically to prevent complaints from leaving the company. Above that, in most larger organizations, sits an executive response function that handles anything arriving addressed to a named officer or referred from a regulator, and that team generally has authority to do essentially whatever the situation requires. Skipping levels is usually counterproductive, because most escalation processes require evidence that the earlier stages were attempted and will return the matter downward if they were not. The efficient route is to move one step at a time and quickly, asking at each level whether this is the point at which the decision can be made. Asking for the complaint to be escalated is a defined request in most companies, and phrasing it that way is more effective than asking for a manager.

What a Reference Number Is Really For

The reference or case number is not administrative decoration. It is what makes the next conversation continuous rather than a fresh start, and its absence is why a complaint can be explained five times to five people. Get one on the first contact, get the name or identifier of the person you spoke to, and write down the date and what was said, because the record you build is the only version of events that exists on your side.

Timing matters as much as identity. A company that has committed to responding within a stated period has created a checkpoint you can refer back to, and following up on the day that period expires, quoting the commitment, moves matters considerably faster than following up randomly. It also builds the sequence that a regulator or an ombudsman will later want to see, which is the reason to keep it even when the matter feels small.

Channels, and Which of Them Reach Whom

The route a complaint travels shapes who eventually reads it, and the channels are not equivalent. A phone call reaches the largest and least empowered team and leaves the weakest record. Web chat reaches a similar tier and produces a transcript, which is worth requesting a copy of. Email or a web form usually reaches a back office group with slightly wider authority and a documented queue, and a letter to a registered office reaches a small team accustomed to matters that have already gone wrong.

Public channels sit awkwardly in this list. A message on a social platform frequently reaches a dedicated team with unusual authority, because visible complaints are handled by people empowered to end them, and that is a genuine and slightly uncomfortable feature of how modern service organizations are arranged. It works best as a short factual statement of an unresolved matter with a case number rather than as an argument, and it works badly for anything requiring account details that should not be posted anywhere.

The Written Complaint That Gets a Decision

At some point the matter should be put in writing, and a written complaint that works has a particular shape. A short factual chronology with dates. A plain statement of what went wrong. A specific statement of the remedy sought, expressed as a number or a defined action rather than as a request for the company to make it right. A reference to the account and any case numbers. And a stated period for a response.

What weakens a written complaint is length, emotion, and the absence of a specific ask. A page and a half of grievance ending with a request to be contacted invites a call that resolves nothing, while a half page ending with a named remedy and a date can be acted on by somebody with authority in under five minutes. Tone does more work than people expect: a calm letter naming a specific failure is much harder to file away than an angry one.

When a Regulator Belongs in the Conversation

Some sectors have a body that accepts consumer complaints directly, and a complaint submitted there is generally forwarded to the company with a requirement to respond, which routes it straight to the executive team rather than back to the phone queue. For financial products, complaints filed with the Consumer Financial Protection Bureau are forwarded to the institution with a response deadline attached, and the resulting reply arrives in writing from somebody senior.

That is not a step to take first, since a company given a reasonable chance to fix something usually will, and the internal route is faster when it works. It is the step to take when the internal route has stalled, and mentioning that it exists is unnecessary because the file the company builds already anticipates it. The whole sequence, from a short diagnostic call to a half page letter with a date on it, is a couple of hours of work spread over a few weeks, and it succeeds mainly because it stops asking the wrong person for something they were never able to give.

Written by

Rosa Petrossian

Rosa writes about the specific case the general advice does not cover.