N NoBullshit.wiki 中文

Convenience store equipment technician - repair-call information capture checklist: a nameplate photo and a fifteen-second fault video before the phone rings, five alignment questions for the service side, and breaker, setpoint, and defrost-cycle checks that keep the truck from rolling for nothing

Works with:Claude / GPT-4 classCategories:Convenience StoreLevel:Beginner Updated

You are the equipment technician for a strip of
convenience stores; every repair call from these
stores crosses your desk first. The store phones
in "the cooler's not cooling," you arrive to find
a different model and no part on the truck - and
the second visit costs the cold chain another
day. Turn "what the store captures before a
repair call" into a checkable checklist covering
reach-in coolers, freezers, bun steamers, the
oden soup station, and the breaker panel. Every
item carries a parenthetical note of what it
saves - a saved trip, the right part, a
true-or-false fault call - so the crew knows the
item is not ritual.

One rule fixed up front: cold-chain faults
(cooler not cooling, freezer warming, temperature
alarm) do not wait for a complete checklist -
call the repair line first and use this sheet as
the phone script, item by item. Non-cold-chain
faults (doors, lights, shelving, a bun steamer
that will not heat) get captured first, then
reported. Fresh-food equipment whose outage kills
today's selling follows the cold-chain track.

Section 1 - Four must-captures before the call
[ ] Nameplate photo: brand, model, and serial,
    all on the nameplate. On coolers and freezers
    it usually sits on the inside wall or low on
    the back of the cabinet; on steamers and the
    soup station, on the back or the base side.
    Shoot at an angle if it glares (saves: the
    right part - one wrong digit in the model
    and the part rides along for nothing)
[ ] Fifteen-second video of the symptom: full
    cabinet first - body, display panel, air
    outlet - then a close-up, sound on. A
    compressor that will not start and a dying
    fan announce themselves by sound (saves: one
    visit - a text description reduces to "not
    cooling")
[ ] When it started: who noticed, on which
    shift, and what the display read when they
    did (saves: separates "always been like
    this" from "suddenly started" - two
    different repair paths)
[ ] What has been tried: power-cycled or not,
    and what happened after (saves: clears the
    most common false fault before the truck
    rolls, one less diagnostic step on site)

Section 2 - Three false-fault checks (run these,
then place the call; cold-chain callers run them
in parallel)
[ ] Tripped circuit: check the breaker panel -
    is this cabinet's breaker down? Reset once;
    if it trips again, stop and report it as
    "reset once, tripped again" (saves: an
    entire wasted visit)
[ ] Setpoint bumped: compare the displayed
    temperature against the setpoint - a
    cleaning bump or a leaned-on key changes
    the setpoint, and the display never agrees
    again (saves: a visit that is two
    keystrokes)
[ ] Mid-defrost: during a defrost cycle the
    cabinet reads a little warmer and the
    compressor pauses - that is normal. Wait
    one full defrost cycle before judging;
    report only if the climb continues (saves:
    filing a normal defrost as a fault, both
    sides working for nothing)

Section 3 - Five questions on the phone
(alignment; write the answers on the back)
[ ] Did the model photo arrive? A call without
    confirmed receipt is not a complete report
[ ] Is the part in stock, or does it ship from
    the warehouse? A parts transfer usually
    means a second visit - ask now
[ ] Estimated arrival time? Cold-chain callers
    start holdover actions and the log from
    this number
[ ] What do we do with the product before you
    arrive? "Can it limp along?" "Should we
    move it?" - get the technician's call, not
    the crew's guess
[ ] Could this be a defrost or mode misread?
    Read your Section 2 findings to the other
    side and let them rule it out remotely

Section 4 - Upload and file
[ ] Photos, video, store name and contact, and
    call time go to the repair channel - chase
    tickets and reconciliation both lean on it
[ ] File the checked sheet with the repair
    record; on a second visit, pull it out and
    compare - what was missing last time, is it
    closed this time

Prohibitions:
- No brand-name examples - brand and model are
  whatever the nameplate photo shows
- No "report promptly" or "describe it clearly"
  items - every line must be checkable
- Self-checks read states only (breaker down,
  display off from setpoint); no temperature
  measurement, no invented thresholds
- No promising "they can fix it by phone" - the
  final true-or-false call belongs to the
  technician on site
- Prints on one A4 page, laminated, hung by the
  breaker panel

Why it is written this way

The nameplate photo ranks first because the number-one cause of second visits is the wrong part: the same cooler ships in a DC-fan version and an AC-fan version, and both are "that cooler" in a phone description. The model cannot be talked out over the phone, and "cannot find the nameplate" is where store crews stall - so the item itself says where the plate sits (inside wall, low on the cabinet back), which turns a dead item into a thirty-second task. The fifteen-second video outranks the text description for the same reason: a crew retelling is conclusion language, three words long, while video carries state and sound - a compressor that will not start and a dying fan simply do not travel through text.

The three false-fault checks are the three "nothing wrong" calls a technician takes most often: tripped breaker, bumped setpoint, and a defrost cycle mistaken for failure. Each one costs a full visit - and on a cold-chain cabinet, a visit is a day of waiting. The defrost check is the most deceptive: mid-cycle, the cabinet reads slightly warmer and the compressor pauses, and the display looks exactly like a dead unit. Hence the fixed rule "wait out one defrost cycle before judging," which catches the false alarm before the phone rings. The breaker item says reset once and no more, because repeated resetting may be facing a ground fault rather than an overload, and safety margins are not found by trying.

The five phone questions turn a one-way notification into alignment. "Did the model photo arrive" plugs the single biggest failure point - a blurry photo or a wrong channel, both sides assuming the other has it, and a wasted trip whose root cause was right there. "Does the part transfer from the warehouse" exposes the second visit before it happens, so the store can plan. "What do we do with the product before you arrive" is the most valuable of the five - "can it limp along," "should we move it" - the technician has seen dozens of these, and one sentence saves a cabinet of goods; that is not something the crew should guess at. Answers go on the back of the sheet because a verbal assurance that was never written down cannot be cited when chasing the ticket.

The cold-chain rule sits at the very top because the natural way to misuse this checklist is as a precondition - "capture everything, then call" - and cold chain cannot afford that order. So it is fixed: for cold-chain faults the sheet is the phone script, read item by item during the call; only non-cold-chain faults capture first. The "saves" note on every item is the sheet's life-support system: a crew that knows one checkbox equals one saved trip or one correct part keeps checking; a checklist without reasons decays into blank paper within a quarter.

repair callsfalse-fault triagefirst-visit fix