Call handling

When a CSR may end an abusive call

A written warn-then-end policy for plumbing CSRs: where the line is, the exact words to use, what to log, and who calls the customer back afterward.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing9 min read

On this page
  1. Angry comes with the job; abuse does not
  2. Where the line is
  3. Why a written rule beats a judgment call
  4. The warn-then-end script
  5. What to log, while it is fresh
  6. Who calls the customer back
  7. Protecting technicians after a threat
  8. The after-hours line
  9. Rolling out the policy
  10. Frequently asked questions
  11. References
Call handling: When a CSR may end an abusive call69%: of dispatchers outside emergency services face unpleasant or angry people every dayCALL HANDLINGWhen a CSR may end anabusive call69%of dispatchers outside emergency services face unpleasant orangry people every dayAva for PlumbersInsightsCall handling: When a CSR may end an abusive call69%: of dispatchers outside emergency services face unpleasant or angry people every dayCALL HANDLINGWhen a CSR may end anabusive call69%of dispatchers outside emergencyservices face unpleasant or angrypeople every dayAva for Plumbers
Figure source: O*NET OnLine (U.S. Department of Labor, Employment and Training Administration), 2026[1]

Key takeaways

  • Angry callers get de-escalation; insults, slurs, sexual remarks and threats get the written policy.
  • One redirect, one clear warning, then end the call politely and say a manager will call back.
  • Threats of harm skip the warnings, go straight to a manager and flag the address before anyone is dispatched.
  • Log the exact words, the times, the warnings given and the recording reference within 15 minutes.
  • An employer can be responsible for a customer's sexual harassment of staff if it knows and fails to act[2].

Angry comes with the job; abuse does not

Every plumbing office takes calls from people having a terrible day: a basement full of water, a technician who ran two hours late, a bill bigger than they expected. Raised voices about those things come with the job, and a good CSR can usually turn the call around. Personal insults, slurs, sexual comments and threats are something else, and no CSR should have to decide alone, mid-call, whether they are allowed to hang up. The answer should already be written down and signed by the owner.

The people answering your phones meet hostility constantly. In O*NET's survey data, 42% of customer service representatives say they deal with unpleasant, angry or discourteous people every day, and another 36% at least once a week[3]. Among dispatchers outside police, fire and ambulance work, 69% say every day[1]; among receptionists, 32%[4]. In a plumbing office, where one person is often CSR, dispatcher and receptionist at once, those numbers describe a normal week.

How often customer service reps deal with unpleasant or angry peopleO*NET work context responses for customer service representatives.
How often customer service reps deal with unpleasant or angry peopleStacked bar chart. Every day: 42%; Weekly, not daily: 36%; Less often: 22%.Every day: 42% (42%)Weekly, not daily: 36% (36%)Less often: 22% (22%)How often customer service reps deal with unpleasant or angry peopleStacked bar chart. Every day: 42%; Weekly, not daily: 36%; Less often: 22%.Every day: 42% (42%)Weekly, not daily: 36% (36%)Less often: 22% (22%)
  • Every day 42%
  • Weekly, not daily 36%
  • Less often 22%

Source: O*NET OnLine (U.S. Department of Labor, Employment and Training Administration), 2026[3]

Show the data
ItemValue
Every day42%
Weekly, not daily36%
Less often22%

The policy below does three things. It draws the line between angry and abusive, gives the CSR exact words to use before ending a call, and makes sure someone else calls the customer back, so ending a call does not end a customer relationship by accident.

Where the line is

Angry or abusive?
Angry: keep helpingAbusive: warn, then end
LanguageSwearing about the situationSwearing at the CSR, or slurs
TargetThe leak, the delay, the billThe CSR's intelligence, accent, gender or race
PatternCalms down once heardCarries on after a clear warning
Sexual remarksNoneAny, at any point in the call
Next stepDe-escalate and solveRedirect, warn, end and log

Threats of harm are a third category: no warnings, end the call and tell a manager at once.

A threat to post a bad review or complain to the licensing board is not abuse. It is a customer using the options they have, and it gets handled as a complaint, with the de-escalation steps for angry callers and a manager if needed. The policy is for what a CSR should never have to absorb, not for customers who are loud and right.

Threats of violence sit apart. OSHA defines workplace violence as any act or threat of physical violence, harassment, intimidation or other threatening behavior at the work site[5]. A threat made by phone about the technician who will be standing in that caller's kitchen tomorrow fits that description. Those calls skip the warnings.

Why a written rule beats a judgment call

Without a written rule, two things happen. Some CSRs absorb abuse for twenty minutes because they think hanging up will get them in trouble. Others end calls early with callers who were only upset, and lose good customers. A written rule protects the employee and the customer relationship at the same time, and it means every CSR handles the same situation the same way.

There is a legal side too. Under EEOC regulations, an employer may be responsible for sexual harassment of employees by non-employees, which includes customers, where it knows or should have known of the conduct and fails to take immediate and appropriate corrective action[2]. A caller who makes sexual remarks to the same CSR every time he rings is that situation. A policy that lets her end the call, and a manager who acts on the log, is the corrective action. OSHA also lists customer service agents among the workers at higher risk of workplace violence[5], which is reason enough to have the rule written before you need it.

The warn-then-end script

Example: ending an abusive call
  • Caller
  • Your team
  1. 01Caller

    Caller turns abusive

    Insults, slurs or sexual remarks aimed at the CSR, not at the problem.

  2. 02Your team

    Redirect once

    Steer back to the job: β€œLet's go back to what's happening with the leak.”

  3. 03Your team

    Clear warning

    β€œIf the language continues, I'll end this call and a manager will call you.”

  4. 04Your team

    End the call politely

    β€œI'm ending the call now. A manager will call you back today. Goodbye.”

  5. 05Your team

    Log and hand off

    Written up within 15 minutes; a manager owns the callback.

Example sequence for abuse. Threats of harm skip the redirect and the warning.

Use the same words every time. Rehearsed words come out under pressure, and identical wording makes the log simple to write and simple to defend. A full set:

  • Redirect: β€œI can hear how frustrated you are, and I want to get this fixed. Let's go back to the water heater: is it still leaking?”
  • Warning: β€œI want to help you, and I can't do that while I'm being spoken to like this. If it continues, I'll end the call and a manager will call you back.”
  • Ending: β€œI'm going to end the call now. A manager will call you back today on this number. Goodbye.”
  • Threat: β€œI'm ending this call now.” Nothing more, then straight to a manager.

Rules that go with the script:

  • One redirect, one warning, then end. No arguing, and no long explanation of the policy.
  • Safety first. If the caller describes a gas smell, water near electrics or sewage coming up inside, give the safety instruction before anything else, then follow the policy.
  • Never end a call in silence or mid-sentence. The caller should hear that the call is ending and what happens next.
  • The CSR who ended the call does not call back. The callback belongs to a manager.
  • No permission needed. The written policy is the permission; a CSR should never have to put an abusive caller on hold to ask.

What to log, while it is fresh

Abusive call log. Write it within 15 minutes of the call, while the words are fresh.
FieldWhat to write
Date, time and lineWhen the call started and ended, and which number it came in on
CallerName, callback number, address and any open job
Exact wordsThe insults or threats word for word, in quotation marks, not β€œhe was rude”
Warnings givenThe redirect and the warning, with the time of each
Recording referenceCall ID or recording link, if the call was recorded
Who was toldThe manager's name and when they were told
OutcomeCallback made, conditions set, service declined or police contacted

A recording makes the log much stronger, but only a lawful one. Federal law allows a call to be recorded when a party to it consents[6], while states such as California require the consent of all parties to a confidential communication, with fines of up to $2,500 per violation[7]. If your phone system records every call with an announced notice, the call is already captured; call recording consent rules for plumbing companies explains the state differences. Do not start a secret recording on a personal phone halfway through an ugly call.

If the same person keeps calling to abuse staff, the log matters even more. Federal law makes it an offense to make repeated calls solely to harass a specific person, or to make someone's phone ring repeatedly with intent to harass, with a penalty of up to two years in prison[8]. A dated log with the exact words is the first thing police will ask for.

Who calls the customer back

Ending the call is not the end of the matter. The policy should say that a manager calls the customer back the same business day. The exception is a call that included a threat of harm: then the manager and the owner decide together whether anyone calls at all.

Example callback: β€œMr. Hale, this is Rob, the service manager at Kettle Creek Plumbing. Our office ended a call with you earlier today after a warning about language. I'd like to sort out the water heater problem you called about. We're glad to help, and we need calls with our staff to stay respectful. Can you tell me what's happening with it now?”

Most callers apologize, or at least calm down, when a manager rings them. The call separates the issue from the behavior: the leak still needs fixing, and the language still was not acceptable. The manager closes it with one of three outcomes and writes it in the log:

  • Resolve the original problem and close the log.
  • Set conditions: further contact goes through the manager, by email, or only about the open job.
  • Decline future service in writing, finishing or settling any work already agreed under your terms.

Protecting technicians after a threat

A threatening caller is often a customer with an address on tomorrow's schedule. When a call ends with a threat, the manager flags the account before anyone is dispatched there. The options are to send two technicians, require a manager's approval for any visit, or decline the job. Technicians work alone in other people's homes, and OSHA notes that working alone or in isolated areas can contribute to the potential for violence[5].

Tell the technician what was said. A tech walking into a home where the customer threatened the office yesterday deserves to know, and deserves explicit permission to leave if the visit turns. If a caller makes a specific threat to harm someone, call the police and give them the log.

The after-hours line

Night calls are where the people answering are most alone. Put the same policy in front of whoever covers after hours, including a family member who picks up the on-call phone at 2 am. If an SI Employee answers your forwarded line at night, every call already has a recording, transcript and summary in your account, which gives the manager the verbatim record in the morning, and an owner or manager can listen to a call in progress and take it over or end it (what it does). The residential emergency-call example models how night calls would be sorted and handed to the morning dispatcher.

Rolling out the policy

  1. Write it on one page

    Definitions, the script, the threat exception, the safety exception and the log fields.

  2. Have the owner sign it

    CSRs need to know the owner will back them when they use it, including with a long-standing customer.

  3. Practice the words

    Each CSR says the redirect, warning and ending out loud in a role-play until the words come without thinking.

  4. Review every ended call

    The manager reads each log within a day and checks the policy was followed in both directions.

  5. Look for the pattern monthly

    Repeated abuse after late arrivals or surprise bills points to a process problem worth fixing upstream.

Then check the policy is used, not just written. If no call has been ended in a year, ask the CSRs whether they believe they are allowed to. If calls are ended every week, listen to a few: some may be angry customers who needed patience rather than a warning. Clear first-call scripts and a good booking-rate routine prevent a fair share of those calls before they start.

Frequently asked questions

When can you hang up on a customer?

When the caller is abusive, after one redirect and one clear warning, or at once if the caller threatens harm. Give any safety instruction first if the caller has described an emergency, and always tell the caller that a manager will call back.

Should a CSR ask permission before ending an abusive call?

No. The written, signed policy is the permission. Making a CSR put an abusive caller on hold to find a manager defeats the purpose; the manager reviews the log afterward instead.

What if the caller is abusive and also has a plumbing emergency?

Give the safety instruction first: how to shut off the water, to leave the house if they smell gas, or to call 911 if anyone is in danger. Then follow the policy. Whether a technician goes out is the manager's decision, not the CSR's.

Can we refuse future work for a customer who abused our staff?

Many businesses do, for conduct, provided the decision is not based on a protected characteristic and any work already agreed is finished or settled under your terms. Put the decision in writing, and talk to your attorney if a contract is still open.

What about a caller who keeps ringing back after we end the call?

Log every call with times and words, and route the number to a manager. Repeated calls made solely to harass a specific person are a federal offense[8], and the log is what police will need.

References

  1. O*NET OnLine (U.S. Department of Labor, Employment and Training Administration) (2026). O*NET OnLine summary report: 43-5032.00 Dispatchers, Except Police, Fire, and Ambulance (opens in a new tab) ↑

  2. Legal Information Institute, Cornell Law School (Code of Federal Regulations) (2026). 29 CFR Β§ 1604.11 - Sexual harassment (opens in a new tab) ↑

  3. O*NET OnLine (U.S. Department of Labor, Employment and Training Administration) (2026). O*NET OnLine summary report: 43-4051.00 Customer Service Representatives (opens in a new tab) ↑

  4. O*NET OnLine (U.S. Department of Labor, Employment and Training Administration) (2026). O*NET OnLine summary report: 43-4171.00 Receptionists and Information Clerks (opens in a new tab) ↑

  5. Occupational Safety and Health Administration (2026). Workplace Violence (opens in a new tab) ↑

  6. Legal Information Institute, Cornell Law School (U.S. Code) (2026). 18 U.S. Code Β§ 2511 - Interception and disclosure of wire, oral, or electronic communications prohibited (opens in a new tab) ↑

  7. public.law (California Penal Code) (2026). California Penal Code section 632 (opens in a new tab) ↑

  8. Legal Information Institute, Cornell Law School (U.S. Code) (2026). 47 U.S. Code Β§ 223 - Obscene or harassing telephone calls in the District of Columbia or in interstate or foreign communications (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo