Handling Difficult Phone Calls and Escalations

The core practices in the phone etiquette section — answering within three rings, taking accurate messages, screening calls without offence — work for the calls that go smoothly. Difficult calls follow different patterns and benefit from rehearsed responses you can reach for under pressure. This page covers the common categories, the scripts that work, and the wider rules around what you can and cannot say on the phone.

The Angry Caller

Anger on the phone is almost always about something other than the conversation you are in. The caller is frustrated about a delay, a missed commitment, a billing dispute, or a personal slight, and you are the first human voice they have reached. The trap is to defend the company, your executive, or yourself. The faster path through the call is to route the energy somewhere it can actually be resolved.

The four-step script

1. Acknowledge without conceding. "I can hear that this has been frustrating, and I want to help you get to a resolution." You are not agreeing they are right. You are confirming you have heard them.
2. Get the facts. "Can you tell me what's happened so I have the full picture before I route this?" People de-escalate when they are being listened to specifically. Generic listening does not work; structured note-taking does.
3. Set a realistic next step. "I am going to flag this for [the right person] and get you a callback by end of day Tuesday." The trap to avoid is promising your executive will personally call back today; you do not control their day.
4. Close cleanly. "I have your number as [number]; you'll hear back by [time]. Is there anything else I should make sure to flag?" Repeating the number reduces the chance of a wrong-number call-back, which is its own kind of escalation.

What to do after the call

The post-call work is more important than the call. Write up what was said while the language is fresh. Send the summary to whoever owns the resolution — typically your executive or a department head — with the specific commitment you made on their behalf. If a call recording was made, note that too, with the legal disclosure rules in mind (covered below).

What you do not do

• You do not match their volume.
• You do not commit your executive to a personal callback unless you have explicit standing authority to do that.
• You do not give out the executive's mobile number, home address, or personal email "just to make this go away." That trade always ends badly.
• You do not transfer the call to someone who is not expecting it — this turns a cold escalation into a worse one.

The Persistent Caller

A different pattern: the caller is not angry, but they keep calling — sometimes daily — trying to get past you to your executive. They may be a vendor, a recruiter, a journalist, an investor, or a stakeholder who feels they are not getting attention. The script for the second and third call differs from the first.

First call

Treat as a normal screening call. Get the name, the company, the topic, and the level of urgency. Take a message and route it correctly. The first call is not yet "persistent."

Second and third call within a short window

"I want to make sure you get the response you're looking for. The fastest path is for me to take detailed notes about what you need, route them through, and confirm a timeline back to you. I won't be able to put you through directly without that step." The phrasing makes you the gate without making them feel like they have hit a wall — they have a path.

If they keep calling

At some point the right answer is to be explicit: "I have flagged your three messages. I am the channel for this; I will get you an answer when [executive] has had a chance to review. Calling more often will not speed it up." Said calmly, this often works on the third or fourth call. If it does not, escalate to your executive — the pattern is now their decision to handle, not yours to absorb.

Most persistent callers eventually get a written answer rather than a phone one. The craft of writing the polite, final-feeling decline that closes the loop without burning the relationship is in declining on behalf: writing regrets and saying no well.

Information Requests You Should Not Answer

Many difficult calls are not about emotion at all. They are about extracting information. The caller wants to know whether a specific person works there, whether your executive will be in the office Tuesday afternoon, what the company's current address is, what a salary range is, whether a particular deal is closing. Your default for any of this is to confirm nothing.

Categories of information that almost never go out by phone

• Whether a specific employee works at the company. Even confirming this gives away targeting information for fraud, harassment, or social engineering.
• Anyone's calendar, location, or travel plans. Even at a high level. "She's in meetings all day" is more information than the caller needs and can be used to time a follow-up attack.
• Internal extension lists, email addresses, or org charts.
• Salary, compensation, or budget figures.
• Active vendor relationships, contract terms, or commercial status.
• Anything about active legal matters, M&A activity, or pre-announcement personnel changes.

The redirect script

"That's not something I can confirm by phone. If you can tell me what you are trying to accomplish, I can route you to the right person, who can decide what to share with you." This works for almost every category. It is polite, it does not lie, and it puts the burden of escalation on the caller — most callers will give up at this point because their question was an opportunistic fishing expedition rather than a real need.

The social engineering pattern to recognize

A small but meaningful share of these calls are deliberate attempts to extract information for fraud — wire transfer scams, phishing attacks, or executive impersonation. The patterns are recognizable:

• The caller claims authority (the executive's own boss, a regulator, a vendor with an urgent contract issue) and creates time pressure.
• They ask you to confirm details rather than provide them — "I just need to verify the wire account ending in 4471, can you read me the last four digits?"
• They discourage you from following normal channels — "Don't email about this; he asked me to call you direct."
• They know enough about your company to sound legitimate, but cannot answer follow-up questions cleanly.

The defense is to stop the call and verify. "I will need to confirm this through our usual channels and call you back at the published number for [organization]." Any legitimate caller will accept this. Anyone who refuses is the reason the rule exists.

Recording Disclosures

Some companies record incoming calls, either to a published line or to direct numbers. The rules around this vary substantially by location and are worth knowing in outline:

• One-party-consent jurisdictions: only one participant in the call needs to consent to the recording. In practice this means your company can record without disclosing.
• All-party-consent jurisdictions: every participant must be informed. This is why so many calls open with "this call may be recorded for quality and training purposes" — that opening is a legal requirement, not a courtesy.
• International calls: the stricter rule typically applies. If your company records calls and a caller is dialing in from a jurisdiction with stricter rules, the disclosure obligation usually still applies to that call.

None of this is legal advice — the actual rules in your country, state, and industry are specific and can change. What it means in practice is that you should know whether your company records calls, and you should not promise a caller a recording does not exist without checking. If a caller asks whether the call is being recorded, the right answer is "let me check" or "I would need to confirm that with our compliance team," not a guess. The site disclaimer covers the broader point: when in doubt on rules like these, route through the appropriate qualified person.

Logging the Calls That Matter

Difficult calls often resurface — the caller calls back, the issue escalates, or someone else has to pick up the thread. A short, structured log saves you each time:

• Date and time
• Caller's name, organization, and number
• The substance of the call in two or three sentences
• What you committed to and by when
• What you escalated, and to whom

Keep the log somewhere you can search it. The first time a caller comes back two weeks later claiming you promised something different, the log resolves the conversation in thirty seconds.

When the Call Is Threatening

Rarely, a difficult call crosses into territory that is not just unpleasant but threatening — direct threats to your executive, your colleagues, the building, or yourself. Three rules:

1. Stay on the line if it is safe to do so. The caller's words are evidence.
2. Take detailed notes — exact phrases, background sounds, any names or specifics dropped.
3. End the call calmly, then immediately route the incident to security or your executive's chain of command, not just by email but by phone or in person. A threat sitting unread in someone's inbox is the worst possible outcome.

Most companies have an explicit protocol for this. If yours does, it should be in your desk manual; if it is not, this is a section worth adding before you ever need it.

The thread that runs through all of these scenarios is the same: difficult calls reward preparation. The script you rehearsed yesterday works at the speed real calls require, while the script you have to invent in the moment usually does not. Build the muscle when the calls are routine, so it is there when the calls are not.