Utility Shutoff Scam: A Callback Rule for Roommates
Pause all payment when a caller, text, or visitor demands money to prevent same-day shutoff.
Pause all payment when a caller, text, or visitor demands money to prevent same-day shutoff. One roommate should find the utility number on a bill or the provider’s official site and call it independently. Nobody should use a number, link, QR code, or payment method supplied by the person making the threat. The household rule should name one coordinator, one backup, and the point where ordinary coordination becomes an emergency call. Review the authoritative FTC scam guidance before adopting the plan.
Set the boundary before the problem
Put a two-person callback rule beside the utility account record. The account holder makes the independent call while another housemate records the time, number dialed, and result. Keep the actual account number private in the group chat. A last-four-digits reference is enough for coordination. Write the rule while the home is calm, then test whether a new roommate could follow it without private background knowledge. The record should state what residents may do, what they must not do, who owns the next step, and where official instructions live.
This rule should also fit the household’s related process for utility shutoff payment plan. Linking the records prevents one urgent event from producing two contradictory assignments. If the lease, product manual, clinician, insurer, utility, or local authority sets a stricter requirement, that requirement wins.
Use a short, observable workflow
1. Write down the claimed balance and deadline without confirming personal details.
2. End the contact, then open a saved bill or type the provider address yourself.
3. Call the published number and ask whether the account has a notice, past-due balance, or field visit.
4. If the demand was fake, save screenshots and report it to the FTC and the utility fraud team.
Avoid turning the workflow into a diagnosis or blame exercise. Record observable facts, direct actions, and timestamps. Keep sensitive account, health, or access details in the narrowest appropriate place, not a broad house chat. After the event, fix the process gap without rewriting what happened.
Use this conflict-free script: “We do not authorize urgent payments from incoming contacts. We will call the provider using our saved bill and update the house record.” This keeps the account holder from being pressured by housemates who fear an outage.
How HomeCo helps
Create a HomeCo task with a named owner, backup, due trigger, and checklist. Attach the official guidance or manual, plus a redacted photo when it clarifies the location or equipment. Use recurring reminders only for genuine inspections or reviews, not for emergencies that require immediate action.
Keep discussion in the task so the final status is visible to everyone who needs it. Record “verified,” “reported,” “replaced,” or another concrete result instead of “handled.” HomeCo coordinates the household record; it does not replace emergency services, professional advice, lease notices, or the equipment maker’s instructions.
At the next house check-in, review whether the trigger, owner, and evidence were clear. Close the task only after the named verifier can see the stated result. If the process failed because a person was unavailable, assign a backup rather than adding repeated reminders. Archive obsolete photos and redact details that other residents no longer need. A useful household record proves the handoff occurred while exposing as little private information as possible.
FAQ
Could a real utility contact us about arrears?
Yes. The point is not to ignore the issue. Verify it through a channel you locate independently before paying or sharing account data.
What if someone already paid?
Contact the payment company immediately, tell the utility fraud team, preserve messages, and report the incident. Do not shame the payer.
Should every roommate have the account password?
No. Record who owns the account and how others can reach that person. Shared access can create unnecessary security and offboarding problems.