The Customer Who Calls the Office Every Day

Why this matters

Every office has one: the customer who calls most days, sometimes twice, about a thermostat, a noise, a question already answered, or nothing in particular. Offices tend to settle on one explanation early and treat every call that way, and each of the three common explanations has a different wrong response. Treat a lonely caller as a service problem and you send paid visits nobody needed. Treat a real recurring fault as loneliness and you miss the fault. Treat declining memory as either and you book work a confused customer agreed to on the phone, and later their family asks why. This card is a fork: three branches that do not converge, the criteria that tell them apart, and what each one asks of the office.

First, the calls that are not this article

Before you sort any caller into a branch, every call gets one screen, because a familiar voice is exactly how a real emergency gets waved through:

• Gas smell, a carbon monoxide alarm sounding, or smoke: tell the caller to leave the home now and call 911 or the gas utility from outside, and do not stay on the line while they are still inside. Then tell the owner.
• Headaches, dizziness or nausea, especially more than one person or worse in the mornings, in a home with fuel-burning equipment: treat as possible carbon monoxide. Same instruction: everyone out, 911 from outside.
• A fall, an injury, chest pain, confusion that is new today, or no answer after the caller says they are unwell: 911. See related: The Medical Emergency on a Service Call SOP.
• No heat or no water in a household that cannot manage without: this is an escalation, not a chat. See related: The Vulnerable Household No Heat or No Water Escalation SOP.

Only once a call clears that screen does it belong to one of the branches below. The screen runs on every call, including the fortieth.

The log that makes the fork visible

Nobody can tell the branches apart from memory, because each call on its own sounds reasonable. What separates them is the pattern across calls, so the first move is to keep a short log: date, time, what the caller asked for, whether it was new, and anything the caller said about a previous call or visit. One line per call, kept by whoever answers.

CALL LOG  customer 4471  (office, Feb)
02  09:15 Thermostat "not working." Booked.
03  --    Visit: hold mode on, batteries low.
          Batteries replaced. Paid by card.
04  09:20 Thermostat "broken again."
05  10:05 Chat, grandson's visit. No issue.
06  09:10 Asks when tech is coming. (Came 03.)
07  09:30 Wants to pay last bill. (Paid 03.)
09  05:40 Says house is cold. Office closed,
          voicemail. Called back 08:05: warm.
10  09:15 Thermostat "won't go up."
11  14:30 Asks for "the young man" by name.

Read that log against the criteria below before reading the rest of this card. The worked case comes back to it.

Branch A: loneliness

Criteria. Calls are friendly and conversational. They cluster at a steady time of day. The caller remembers earlier calls and visits accurately, including names. The stated reason is minor, recycled, or drops away quickly into conversation. The caller ends the call readily when given a warm close. Nothing reported is new, and nothing reported is wrong when someone checks.

What it asks of the office. Kindness with a time box. A sensible default is five minutes, ended warmly: "It's been good talking to you, I've got to get back to the phones. Talk to you soon." One named person takes these calls where possible, so the caller is not explaining themselves to a new voice each time and the rest of the office is not pulled in. The office does not book visits to answer loneliness, because each one costs a tech slot and teaches the caller that reporting a fault is how to get company.

Point the caller, gently and once, toward something built for this. The Eldercare Locator, run by the U.S. Administration for Community Living at 1-800-677-1116, connects older adults to their local Area Agency on Aging, many of which run telephone reassurance or friendly-visitor programs. Offer it as information, not as a referral that sounds like being passed off.

The failure mode in this branch is the office deciding a caller is lonely and then hearing every later call as social, so the one real fault report in month three gets the same warm brush-off. That is why the screen runs on every call, and why branch C's criteria get checked even for the regulars.

Branch B: memory or cognitive change

Criteria. The caller repeats a request as if it were new. They do not recall a visit that happened, or a call from yesterday. They try to pay an invoice already paid, or dispute one they approved. Calls come at odd hours or the caller is unsure of the day. They report a problem that a check shows is not there, or describe the same fixed problem as new. Their account of an event changes between calls. None of this is a diagnosis, and an office should never offer one; it is a set of observations, and it is the pattern of several, not any single one, that puts a caller in this branch.

What it asks of the office. Three things, in order.

• Stop booking paid work on phone requests alone. Before any visit, the office asks two checking questions ("Is the display showing a number right now? What does it say?") and, if a visit still seems warranted, confirms it with the family contact. A customer who cannot recall agreeing to work cannot reliably have agreed to it. See related: Capacity to Contract: The Signs and What to Do, which owns the question of consent.
• Reach the family or emergency contact on file, with the customer's agreement where you can get it: "Would it be all right if we let your son know the thermostat's been giving you trouble?" Report the observations, not a conclusion: "Your mother has called eight times in ten days, once to pay an invoice that's already paid, and once at 5:40 in the morning." Let the family draw the conclusion.
• If there is no family, or the family is the problem, and there are signs the customer is not managing (no food, no heat, unpaid utilities, someone taking money), that is the reporting question, not this card's. See related: What a Tech Can and Cannot Do About a Welfare Concern, and Calling Adult Protective Services: What to Say.

The failure mode in this branch is a double payment refunded with a note and nothing else. The refund is right; the silence is the error. A second payment attempt on an already-paid invoice is one of the clearest observations an office ever gets.

Branch C: a real recurring problem

Criteria. The complaint is specific and consistent from call to call ("won't go above 64 in the mornings"). It can be observed when a tech checks, or it can be reproduced. It recurs after a repair. It fits a known failure: an intermittent ignition fault, a short-cycling system, a thermostat or control the customer genuinely cannot read or operate. The caller is often frustrated rather than chatty.

What it asks of the office. Treat it as a callback, not a social call. A different or more senior tech, a data logger left in place for a few days to catch the intermittent fault, a check of whether the original repair addressed the cause, and a warranty look. Frequently the real fault is the control itself: a small display, a hold mode that engages at a single touch, buttons that need a fingernail. That fault is real even though the equipment works perfectly, and it is fixed by changing the control, not by explaining it again. See related: Installing Controls a Customer Can Actually Reach and Read.

The failure mode in this branch is the "no problem found" visit repeated three times. Each tech arrives, finds the house warm at 10 a.m., and leaves. The fault happens at 5 a.m.

When two branches are true at once

They often are, and the branches still do not merge: each one keeps its own response. A lonely caller can also have a failing igniter. A customer with declining memory can be calling about a thermostat that is genuinely too hard to use. Run all three sets of criteria against the log every time, act on each one that matches, and resist the relief of finding one explanation that covers everything.

Worked case: reading the February log

Go back to the log. The office had filed customer 4471 under loneliness: the calls were friendly, she asked after the tech by name, and one call was entirely about her grandson. Read against all three branches:

• Branch A criteria present: a friendly tone throughout, a steady morning time on all but two of the eight calls (09 at 05:40 and 11 at 14:30), a call entirely about her grandson (05), and asking for "the young man" by name (11).
• Branch B criteria present: asks when the tech is coming three days after he came (06); tries to pay an invoice paid four days earlier (07); a 5:40 a.m. call about the cold (09). Three separate observations, which is a pattern rather than a bad day.
• Branch C criteria present: three calls about the thermostat specifically (02, 04, 10), the first visit found hold mode engaged with low batteries, and "won't go up" (10) is exactly what hold mode does. The 05:40 cold call followed by a warm house at 08:05 fits a setback schedule or hold engaged overnight. The control is the recurring fault.

So all three apply, and each gets its own response:

• C: the shop replaced the thermostat with a simple non-programmable model with a large display and the hold function disabled, at a visit confirmed first with her son. Calls about the thermostat or the cold stopped: zero in the following three weeks, against four (02, 04, 09, 10) in the first ten days of February.
• B: before that visit, the office called the son, with her agreement, and gave him the three observations by date. He had noticed the same at home and arranged a doctor's appointment. He became the confirming contact for any future paid work, recorded on her account.
• A: she still calls, about twice a week now rather than daily, to one named person in the office, for five minutes. The office gave her the Eldercare Locator number once, and her son set up a friendly-visitor program.

What would have flipped it: had the son been unreachable and the log shown unopened mail, a cold house on every check and a new "nephew" handling her bills, the B branch stops being a family conversation and becomes the reporting question in What a Tech Can and Cannot Do About a Welfare Concern.

How to know the office has this right

Look at any caller who has rung more than ten times in a month. Confirm a log exists, that the emergency screen was noted on each call, and that someone has written which of the three branches the criteria support and what was done about each. If the answer for a frequent caller is "she's just lonely" with no log behind it, that is the case to re-read first.

References

• U.S. Administration for Community Living, Eldercare Locator (1-800-677-1116), for local Area Agency on Aging programs
• See related: What a Tech Can and Cannot Do About a Welfare Concern
• See related: Capacity to Contract: The Signs and What to Do
• See related: Installing Controls a Customer Can Actually Reach and Read
• See related: The Medical Emergency on a Service Call SOP