The Customer Harassment Report and Response SOP

Purpose

When a customer harasses a tech, the shop's legal exposure and the tech's trust in the shop are both decided by the same thing: what happens in the days after the first report. A shop that hears it, means to deal with it, and books the same tech back into the same house a month later has turned a customer's misconduct into its own failure.

This procedure fixes the response: how the tech reports, how fast the owner answers, how the account is held before anyone goes back, how the customer is told, how the tech is followed up, and what is written down. It is built so that it still works when the customer says it never happened, which is the most common way these responses stall.

The duty behind it, who is covered, and the range of corrective options are set out in the reference card. See related: Sexual Harassment of Techs by Customers.

Scope

Covers any report by an employee of sexual or sex-based conduct by a customer, a household member or anyone else at a customer property: comments, propositions, staging, contact, and messages to a tech's personal phone or accounts. It applies whether the report is formal or a remark in the truck, and whether the tech wants action or "just wanted someone to know."

Does not cover harassment between employees, which runs under the shop's internal complaint procedure with its own investigation, nor a customer who is threatening or violent in a way that is not sexual, which runs under the hostile-customer card. Physical assault is covered here for the account steps, but the tech's medical care and any police report come first and are the tech's to decide.

Roles and responsibilities

Role Owns Hands off to
Tech Leaving when needed, reporting the same day, keeping any messages Owner, by phone, not text alone
Anyone who hears a report (dispatcher, lead, coworker) Passing it on the same day, word for word Owner, the same day, even if the tech said "it's nothing"
Owner Steps 2 to 7: response, account hold, customer contact, decision, follow-up Office for the account hold; employment attorney where step 5 or 6 says so
Office Applying the hold so no booking reaches the tech or a lone tech Every dispatcher, through the booking screen

The handoff that fails is the second row. A dispatcher hears a joke about "the creep on Elm Street" and does not realize they have just received a report that, once it reaches anyone the shop expects to pass complaints on, the law can treat as notice to the shop.

Procedure

Step 1. The tech reports the same day, by phone. After any incident, the tech calls the owner the same day, and from the truck straight away if the conduct was physical, threatening, or made them leave. The tech keeps every text, voicemail and message from the customer, unanswered and undeleted. Acceptance: owner spoken to by voice within the working day of the incident, and any messages kept on the tech's phone. Wrong looks like a text that says "weird guy at Elm," or a tech who deletes the customer's messages because they are embarrassing. Stop rule: if the owner cannot be reached within 2 hours, the tech tells the office manager, who logs it and keeps trying the owner. Hazard: a tech who is shaken should not drive straight to the next call; they sit in the parked truck until they are steady, and if they were touched or threatened they are offered the rest of the day.

Step 2. The owner answers within one hour and checks on the tech first. The owner's first questions are about the tech, not the account: are you safe, are you hurt, do you want to see a doctor, do you want to report this to police. Then the owner says plainly that the tech did the right thing by reporting and by leaving if they left, and that they will be paid for the visit. Acceptance: a call back within one hour of the report during working hours, those four questions asked, and the pay confirmed. Wrong looks like the first question being "did you finish the job?" Stop rule: where the conduct was physical or threatening, the owner tells the tech they may report it to police and that the shop will support whatever they decide, then takes no steps on the account that could alert the customer until the tech has made that decision. Hazard: none physical at this step.

Step 3. Take the account down in the tech's words within 24 hours. The owner, or a manager who is not the tech's friend or rival, writes down what happened: date, time, address, what the customer said or did in the tech's words, what the tech said or did, who else was present, and whether the tech left. The tech reads it and confirms it. Messages are saved by screenshot and by forwarding to a shop email, with dates showing. Acceptance: a written account the tech has confirmed, within 24 hours of the report, with any messages attached. Wrong looks like the owner paraphrasing ("customer was inappropriate"), which tells a later reader nothing, or an account that includes the owner's opinion of the tech. Stop rule: if the tech does not want to give details, record that they reported, what they were willing to say, and that they declined the rest, and continue to step 4 anyway. Hazard: none physical.

Step 4. Hold the account before any further booking. Within 24 hours the office places a hold on the account so no visit can be booked without the owner: the reporting tech is never sent there again unless they ask to be, and no tech goes alone. The flag the dispatcher sees is neutral, such as "owner to assign, two techs, call office before booking," and carries no description of the conduct. Recurring and plan visits on the schedule are pulled into the hold too. Acceptance: hold applied and confirmed on the screen within 24 hours, every scheduled visit at that address reviewed. Wrong looks like a recurring maintenance visit firing automatically three weeks later to the same tech. Stop rule: if a visit is already booked within the next 48 hours, the owner calls the customer to move it before any other step. Hazard: the scheduled visit no one remembered is the one that sends a tech back into the house.

Step 5. Tell the customer within three business days. The owner calls the customer, and follows up in writing, saying in factual terms what was reported, that the shop's techs are not to be treated that way, and what the consequence will be. The owner does not need the customer to agree, and does not argue the facts. Acceptance: customer contacted by phone and by written confirmation within three business days of the report. Wrong looks like an apology to the customer for the "misunderstanding," or a negotiation over what really happened. Stop rule: if the customer disputes the report, the response does not stop. The owner says the shop has made its decision, notes the denial in the record, keeps every step 4 measure in place, and does not send the reporting tech or any lone tech; if the customer threatens a lawsuit or a campaign of reviews, or if the conduct was physical, the owner calls an employment attorney before saying anything further. Hazard: none physical; the owner makes this call, not the tech.

Step 6. Decide the outcome within five business days. The owner chooses from the corrective options: a warning with the account kept under the two-tech hold, or ending service with a short factual letter. Touching, exposure, threats, or any repeat after a warning ends the account. Acceptance: the decision recorded with its reason within five business days of the report, and the letter sent if service ends. Wrong looks like keeping a profitable customer and moving the tech off the account instead, at a cost to their hours or commission. Stop rule: any measure that changes the reporting tech's route, hours, pay or commission needs the tech's agreement in writing first; without it, the action lands on the customer. Hazard: none physical.

Step 7. Follow up with the tech at one week and at 30 days. The owner asks the tech whether there has been any further contact, whether they feel the response was enough, and whether anything about their work has changed since the report. The owner checks the tech's hours and earnings for the period against the period before. Acceptance: two conversations held, recorded, and an earnings comparison showing no drop tied to the report. Wrong looks like no follow-up at all, or one that is a formality. Stop rule: a drop in hours or pay, or the tech saying a coworker is making comments about the report, is treated as possible retaliation and dealt with that week. Hazard: none physical.

The record this produces

One incident file per report, kept by the owner, apart from both the tech's personnel file and the customer record.

INCIDENT  HR-2026-07                    OPENED 06/02
Tech:     A. Ruiz (HVAC)       Reported: 06/02 15:40
Address:  [plan customer, Elm St]       Visit: 06/02
Account:  in tech's words, confirmed 06/03 (attached)
Messages: 3 texts to personal phone, saved 06/03
Hold:     applied 06/03 09:10 / 2 techs / owner assign
Customer: called 06/04 DISPUTED / letter 06/05
Atty:     consulted 06/05 (dispute + review threat)
Decision: service ended 06/08, letter sent
Followup: 06/09 ok / 07/02 ok / earnings unchanged
Closed:   07/02

Who reads it: the owner, the shop's employment attorney, an insurer if the shop has employment practices liability cover, and possibly a state agency or the EEOC if a charge is ever filed. The dates are the part that matters most to every one of those readers, because "immediate and appropriate corrective action", the standard 29 CFR 1604.11(e) applies to harassment by non-employees, is measured by them.

A worked pass

That is the file above, filled in.

A shop of 22 employees. On a Tuesday, a female HVAC tech, A. Ruiz, services a maintenance-plan customer. The customer has sent three texts to her personal phone since her last visit and, during this one, asks her to stay for a drink and says she would look better out of her uniform. She declines, finishes the filter change, and leaves.

Step 1 passes: she calls the owner at 3:40 from the truck. Step 2 passes: the owner calls back at 4:05, asks the four questions, confirms she is paid for the visit, and tells her she did right. Step 3 passes: the account is written up Wednesday morning in her words; she confirms it, and three texts are saved. Step 4 passes: hold applied Wednesday at 9:10, and the plan's fall tune-up, booked to her for September, is pulled.

Step 5 fails as the customer disputes it. On Thursday the owner calls him. He says she is lying, that he was being friendly, and that if the shop "spreads this around" he will sue and post reviews. The stop rule runs. The owner does not argue the facts, says the shop has made its decision, notes the denial, keeps the hold, and calls the shop's employment attorney Friday before sending the written confirmation, which the attorney shortens to a plain statement of the conduct reported and the shop's rule.

Step 6: with the attorney's advice on the wording, the owner ends the plan the following Monday, refunding the unused portion, by a short letter stating that the shop has decided not to continue service. Step 7: follow-ups one week and one month on; no further contact from the customer, her hours and earnings for the month match the month before. File closed.

The failed step is the one that teaches. Without its stop rule, the denial would have become a question to be investigated, the hold would have quietly lapsed, and the September tune-up would have gone out to her on schedule.

References

  • 29 CFR 1604.11(e), employer responsibility for harassment by non-employees
  • Title VII of the Civil Rights Act of 1964, section 704(a), on retaliation
  • EEOC guidance on harassment and retaliation, current status on the EEOC website
  • See related: Sexual Harassment of Techs by Customers
  • See related: Writing a Safety Flag on a Customer Record Without Defaming Them