Search for advice on escalation and almost everything you find is written for the people trying to reduce it. Lower your escalation rate. Contain more calls at tier one. Those are perfectly reasonable business goals and they answer a question you are not asking.
Your question is narrower and lands about forty seconds into a call that is going wrong. Do I keep this, or do I pass it on, and which choice is going to look worse later.
Two ways to get it wrong
New agents tend to pick one failure and settle into it.
Some cling to calls far past the point of usefulness, because handing one over feels like confessing they were not capable. Others release them at the first sign of friction, because getting a hostile caller off the line is an enormous relief.
Both feel like decisions at the time. Neither one is. They are habits wearing the costume of judgment, and the tell is that the same agent makes the same choice regardless of what the call actually contains.
A threshold you can apply while the caller is still talking
Your account has an official escalation policy. Learn it, because that is the standard you will be measured against, and nothing here replaces it.
Underneath it, you need something faster, because policies are written to be read at a desk and you have to decide while somebody is mid-sentence.
The working version has two conditions, and a call stays with you only while both hold. It is still inside what you are responsible for, and the caller has not asked for someone above you. The moment either stops being true, the call moves.
Notice what is missing from that. Difficulty is not in it.
Hard is not the same as outside your scope
A brutal call that sits squarely inside your remit is still your call. That is the job, and there is no version of it where the unpleasant ones belong to somebody else.
Passing a call along because a caller is abusive, or because you are near the end of a punishing shift, is not escalation. It is a long hold with better paperwork. A hold parks the problem for ninety seconds. An unnecessary escalation removes it permanently and manages to look conscientious on the way out.
Reviewers see the difference eventually, because it shows up as a pattern rather than as any single call.
When they ask for a supervisor, that is the line
This is the half people argue about, and it is the half that matters more.
Treat a request for someone senior as a boundary, not an objection to be worked around. Plenty of training frames the request as something to talk people out of, and you can watch agents doing exactly that. It works often enough to survive as a technique.
It also explains why so many customers now open with the demand instead of arriving at it. They have learned from experience that the request has to be fought for, so they start fighting before you have said anything.
Treating the request as a line rather than a hurdle costs you very little and removes you from that dynamic entirely.
When the demand arrives before you have done anything
Sometimes it lands during your greeting. Nothing attempted, nothing established, nothing written down.
You cannot simply forward that. It will return to you within the hour, because whoever receives it has nothing to act on, and by then the customer has been passed around twice and is considerably angrier.
The move is to agree first and gather while you arrange it. You are not refusing and you are not stalling. You are setting up the thing they asked for, properly, and doing it properly requires their account. That framing is almost never argued with, and while you are taking the details the history opens up in front of you.
Once they have agreed, find out what they need someone senior to do. The question is fair, the handover is useless without it, and it is frequently the first time anyone has invited them to state the actual problem in a sentence. A surprising number of calls reveal what they are really about right there.
Now you have enough to judge. If it genuinely needs authority you do not have, send it up, and the note practically writes itself at that point.
If it does not, allow yourself a single try at resolving it.
One attempt, and only one
The limit is not about politeness. It is about how a second attempt sounds from the other end.
One try reads as service. Two reads as obstruction, and the caller registers the shift immediately.
They asked for something specific. You made a genuine effort to solve it first. When that fails, give them what they originally asked for. Pushing again only proves that their instinct to demand a supervisor was correct, which is precisely the conclusion you were hoping to avoid.
On leaner floors the person you hand to might be a team lead, or a queue rather than a named individual. That does not change anything. The point is simply that it reaches someone who can do what you cannot.
Handovers that do not bounce
An escalation that comes straight back is worse than never having escalated, since the caller has been shuffled twice over and restarts from zero.
Bounces nearly always have one cause. Whoever picks it up cannot tell which ground you covered, so they duplicate your work or send it back for detail.
Before you hand over, write down the complaint as they phrased it, the actions you truly took rather than the ones the script assumes, the point where it stopped working, and the specific thing they wanted that you could not authorise. If they were hostile, note that plainly and without adjectives.
Then apply one test. Could a colleague pick this up cold and carry on without phoning the caller for an explanation?
If the answer is no, expect it back.
Nobody is counting your escalations. They are reading the pattern
Escalating a call that needed escalating is not a black mark, and no experienced lead thinks otherwise.
What does register, over months rather than calls, is the shape of your decisions. Escalate seldom and accurately and you get left alone to work. Escalate every time a call turns uncomfortable and you get managed instead, which in practice means closer monitoring and fewer decisions left to you.
Those are two quite different working lives, and skill is not what separates them. What separates them is whether you applied the same threshold on the calls where applying it was inconvenient.
That pattern is one of the things leads read, and it feeds a bigger question about whether your floor actually rewards the work.
The fuller version, including how to write an escalation note that survives a cold handover and how to read whether your floor rewards this kind of judgment, is in BPO Agent Handbook, Volume 2: The Floor, written for the agent making the call rather than for the people counting them.