Flagging High-Risk Calls at Booking

Why this matters

Almost every bad visit a tech has had, the office could have seen coming. The address had a note from two years ago. The caller mentioned, in passing, that her brother "has a temper." The job was a crawlspace at 7:00 at night, at a vacant house, booked by someone who would not give a callback number. The tech found out on arrival, alone.

The office is the shop's early-warning system, and it only works if the questions get asked and the answers get turned into a decision before the truck rolls. OSHA's workplace violence guidance for workers who visit clients' homes recommends assessing that risk before the visit, not at the door. This article covers that booking side: what to check, what to ask, what to listen for, and how each answer turns into a two-tech assignment, a check-in call, or an owner's decision. What a tech does once on site alone, including how check-in calls are run, is its own card. See related: Working Alone and Check-In Discipline.

Step 1. Check the address history before you hang up

Before you confirm any booking, look up the address and the caller's name and number in the customer records. You are looking for four things: an existing safety flag, a sharps or hazard note, a harassment hold from a previous report, and any history of a visit cut short (a tech who left, a job stopped, a police call).

Why first: a flag written by a tech who was there outranks anything a caller says on the phone today, and finding it after the booking is confirmed means calling the customer back to change it, which is awkward and gets skipped.

What breaks if you skip it: the recurring visit to the house where a tech found needles in the vanity gets booked to a new apprentice who never saw the note. If the record shows a harassment hold, stop and route the booking to the owner; that account is not yours to schedule. See related: The Customer Harassment Report and Response SOP.

Step 2. Ask every caller the same three access questions

These are ordinary scheduling questions, and asking every caller the same ones means nobody feels singled out:

  1. "Who will be home during the visit?" You want to know an adult, 18 or over, will be present, and whether that adult is the person who can approve the work. A teenager alone, or "nobody, I'll leave it unlocked," changes the booking.
  2. "Where is the equipment?" Attic, crawlspace, basement, detached garage, roof. Confined or isolated work areas are where a tech is hardest to reach and slowest to get out of.
  3. "Is there anything our tech should know before arriving? We ask everyone to have pets put away and anything like firearms secured away from the work area." Saying it as a standard line to every caller lets you ask about firearms without implying anything about this caller, and often brings out the useful answer by itself: "oh, my husband's guns are all in the safe," or "my dad has dementia and sometimes thinks people are breaking in."

What breaks if you skip it: the office books a visit with no idea a minor will be the only person at home, which runs under its own SOP the moment the tech knocks. See related: The Unaccompanied Minor at the Door SOP.

Step 3. Listen for the cues nobody volunteers as a warning

Callers rarely say "this is dangerous." They mention things in passing. Write down what they said in their words, not your interpretation. The cues worth noting:

  • Conflict in the home: "my ex still has a key," "we're in the middle of a divorce," "my son gets angry when people come over."
  • Impairment: slurred speech on the call, a caller who forgets what they said a minute ago, mentions of drinking.
  • A caller who will not identify themselves: no last name, no callback number, a number that does not ring back, an address that does not match the name.
  • Pressure about the tech: asking for "the girl who came last time," asking whether the tech will be alone, or asking what time the tech will leave.
  • Unusual timing and setting: a non-emergency job requested after dark at a vacant or for-sale property, or "meet me at the house, I'll be the only one there."
  • Hostility already present: a caller who is threatening about a previous contractor, the shop's prices, or a dispute.

Two of those cues are almost always worth a second look on their own: a request that only a particular tech be sent, when it comes with a remark about how that tech looks, and a caller who will not give a number that rings back.

What is not a cue: a neighborhood, a name, an accent, a disability, a religion, or a family's makeup. Flags rest on conduct and on the job's physical setting, never on who the customer is. Besides being wrong, refusing or downgrading service on those grounds can violate state public accommodation laws, which in some states, California's Unruh Civil Rights Act among them, reach any business offering services to the public.

Step 4. Turn the answers into a level

Every booking ends with a level. Using a fixed set means two dispatchers make the same call.

Level Triggered by What it sets
Standard No flags, no cues Normal dispatch
Check-in One cue, or a confined or isolated work area (crawlspace, attic, vacant property) Tech calls the office on arrival and at each 60 minutes on site; a missed call starts the escalation in the working-alone card
Two-tech Two or more cues, any prior safety flag on the address, any firearms concern, or a request for a specific tech tied to remarks about them A second tech or a lead on the visit, never a lone apprentice
Owner review Any harassment hold, any prior police call, any threat on the booking call, or a caller who will not identify themselves for a non-emergency job Owner decides before booking: two-tech, daylight only, a different time with another adult present, or decline

Two refinements that hold up well. Daylight only fits almost any check-in or two-tech booking at a vacant or isolated property, and costs nothing but a slot. Never let a cue downgrade over time on its own: a flag from two years ago stays at its level until a tech who visited updates it.

Step 5. Write the flag in neutral words

The flag is what every dispatcher and tech reads, and possibly what the customer reads one day if they ask for their records. It states the level and the instruction, and the observations in plain words, without a diagnosis of the person.

BOOKING FLAG  Job 26-4418  Booked 10/13 by K. Tran
Level:    TWO-TECH  (+ daylight only)
Address:  history note 2024: tech left, customer
          shouting at family member (see job 24-1907)
Caller:   said "my son gets angry when people come
          over"; son lives at the address
Work:     crawlspace, water line, est 2.5 h
Asks:     arrive 9:00-11:00 only; lead on site;
          check-in on arrival and at 60 min
Review:   update after visit, expires 10/2027

"Customer is aggressive" is a conclusion; "said 'my son gets angry when people come over'" is a fact that tells the next reader what they need. The detailed rules for writing these are their own card. See related: Writing a Safety Flag on a Customer Record Without Defaming Them.

What breaks if you skip it: a flag that reads "difficult customer" tells a tech nothing about what to expect, and a flag that reads "drunk, violent family" is a defamation risk the day it is printed out.

Step 6. Tell the tech before dispatch, and get an answer back

The flag is only useful if the tech reads it before they knock. For any level above standard, the dispatcher tells the tech by voice or by a message that needs a reply, not just a note on the job card, and gets a confirmation back. The tech is told that they may decline a two-tech or owner-review job without penalty if they are uncomfortable, and that the office will reassign it.

What breaks if you skip it: the tech opens the job on the tablet in the driveway, reads the flag, and is already at the door.

Step 7. Close the loop after the visit

After any flagged visit, the tech gives a one-line update: the flag was right, the flag was wrong, or something new. The office updates the flag the same day. A flag that turned out to be unfounded comes down a level or off; one that was understated goes up.

Review every active flag at least every 12 months. A household changes: a family member moves out, a customer recovers, a home is sold. A flag that outlives the facts is unfair to the customer and teaches techs to ignore flags.

A worked example

A plumbing office, 4:10 on a Tuesday afternoon. A caller, giving her name and a number that the dispatcher confirms rings back, asks for a technician that evening for a leaking supply line in the crawlspace. The dispatcher, K. Tran, works the steps.

Step 1: the address has a note from 2024 on job 24-1907: a tech left part way through because a man at the address was shouting at a family member, and nobody was hurt. One prior flag.

Step 2: who will be home: "me and my son, he's 30." Where is the equipment: crawlspace. The standard line about pets and firearms: "no guns, just a cat."

Step 3: asked whether the son will be around, she says, "my son gets angry when people come over, but he'll stay in his room." One cue, in her words.

Step 4: a prior flag on the address plus a cue is the two-tech line already; the crawlspace adds to it, and an evening slot puts the visit after dark at a house with a history. The level is two-tech, and the dispatcher adds daylight only. Because the leak is active, the dispatcher asks whether the caller can turn off the main water valve tonight; she can, and does while on the phone. That turns an evening emergency into a morning repair without leaving the house flooding overnight. If she could not, the call would have gone to the owner, who could send two techs that evening rather than wait.

Step 5: the flag is written as shown above. Step 6: the dispatcher calls the lead and the tech that evening, reads them the flag, and gets a yes from each. Step 7: after the visit the lead reports the son stayed in his room and was polite. The flag stays at two-tech for the next visit, since one quiet visit does not undo a 2024 incident, with a note that this visit went without trouble.

What would have changed the level. Had the caller refused to give a callback number, or mentioned the son had threatened a previous contractor, the booking would have gone to owner review before any time was offered. Had there been no 2024 note and no remark about the son, a daytime crawlspace job would have been a check-in booking, not a two-tech one.

How to check it is working

Pull the last 20 visits where a tech left early, a job was stopped, or something went wrong on site. For each, look at the booking: was there a cue in the call notes or the address history that should have set a level? If more than a few had one and were booked as standard, the questions are being asked but not turned into levels, which is Step 4, not Step 2.

References

  • Your state's public accommodation or civil rights statute governing equal service to customers, such as California's Unruh Civil Rights Act
  • OSHA guidance on workplace violence prevention for workers who visit clients' homes
  • See related: Working Alone and Check-In Discipline
  • See related: Writing a Safety Flag on a Customer Record Without Defaming Them
  • See related: The Customer Harassment Report and Response SOP