The Customer Network Is Not Your Job Until It Is

Why this matters

You came to install a thermostat, a water heater with a Wi-Fi module, a camera or a leak hub. It will not stay connected, and the customer, standing beside you, says "can you just fix the Wi-Fi?" Say yes the wrong way and you own every device in the house that misbehaves for the next month, for free. Say no the wrong way and the device you installed keeps dropping and you own that instead. The network is the customer's property, but your device depends on it, and the line between the two is a decision you make out loud, on every job, with the clock and the customer's permission both visible.

Where your scope ends by default

The default scope of a connected-device install is narrow and worth saying plainly to yourself before you start: you join your device to the customer's existing network, using credentials the customer provides, and you confirm your device works on it. That is all. Everything else on the network, the router, the modem, the other devices, the passwords, the settings, is the customer's, or someone else's.

"Someone else's" matters more often than it sounds:

• The internet provider's gateway. Many homes have a combined modem and router supplied by the provider. Its settings may be managed remotely by the provider, who can overwrite a change you make, and its use is governed by the customer's subscriber agreement, not by you.
• A landlord's or association's network. In apartments, condos and some rentals, the Wi-Fi belongs to the building. The tenant cannot authorize changes to it.
• An employer's equipment. A work laptop or a work phone on the home network is managed by the employer's IT, often over a VPN that breaks when network settings change. The customer does not own it either.
• Medical devices. Home monitoring equipment that reports to a clinic or a device maker over the home network is something you do not want to be the reason went offline.

When touching their network is fair: five rungs

Interventions climb from harmless to consequential. Each rung up needs its own explicit yes, and the top two need a written record. The procedure for getting and recording that permission belongs to a sibling SOP; this is the map of when you need it.

1. Observe. Read signal strength where the device lives, see which networks and bands are visible, check whether the internet is up. Touches nothing. Always fair.
2. Use. Join your device to the network with a password the customer types or reads to you. Fair; it is the job.
3. Guide. The customer makes a change on their own router or app while you tell them what to tap. Fair with a yes, because the customer is acting on their own property and sees every step.
4. Change. You log in to their router and change a setting yourself. Needs explicit authorization from the person entitled to give it, and a record of what you changed from what to what.
5. Add or replace. You install an extender, a mesh node, a new router, a switch. This is a sale with its own line on the ticket, and it carries the same authorization and record as rung 4.

The practical rule: stay as low on the ladder as solves the problem. Rung 3 solves a surprising amount, keeps the customer in control of their own equipment, and leaves them knowing how to undo it.

What goes wrong when you change settings

A router setting looks like one switch and behaves like a policy for every device in the house. The changes that generate the "since your tech was here" call:

• Changing the Wi-Fi name or password. Every device in the house disconnects at once: cameras, televisions, printers, the other thermostat, the irrigation controller, the work laptop. Some will need to be re-joined by someone who knows their own account.
• Splitting or merging the 2.4 GHz and 5 GHz bands. Fixes one device's onboarding and quietly breaks another's.
• Turning off a security feature, or turning on port forwarding or automatic port opening, to get a device to connect. That can expose a camera or a hub to the internet.
• Changing DNS or a firmware update on the router. Usually harmless, occasionally not, and you are the last person who touched it.

The legal layer. At the federal level, the Computer Fraud and Abuse Act (18 U.S.C. 1030) makes it an offense to access a computer without authorization or to exceed authorized access, and a router is a computer for this purpose. What makes your login lawful is authorization from someone entitled to give it: the customer for their own router, not the tenant for the landlord's, not anyone for the provider's managed settings beyond what the subscriber agreement allows. Every state also has its own computer crime statute on top of the federal one, and some reach further. Civil exposure is a separate layer: a customer who loses work, footage or a business day after your change can bring a negligence or contract claim under their own state's law. This is not legal advice. The fork: if a customer tells you a change you made caused a loss, a data exposure or a business interruption, stop changing anything, write down exactly what you did and when, and call your insurance agent and your attorney before you admit, promise or refund anything.

The insurance layer. Many general liability policies written for trade contractors exclude errors in professional or technology services, which is a fair description of reconfiguring someone's network. Whether your policy covers it, and whether you need a technology errors-and-omissions policy, is a question to put to your agent with a description of the work, before a tech does it, not after.

Charging for network time

Network work is real work, and the customers who complain about paying for it are mostly the ones who were not told before the clock started.

A starting default worth adopting: the first 15 minutes of network time to get your own device joined is included in the install. Past that, network time is billed at your standard labor rate in 15 minute increments, and the customer agrees to it before you continue. Adding equipment is a separate line for the hardware plus its setup time. Tune the included minutes and the increment to your shop; the point is that both exist and the customer hears them. How that reads on the estimate and the ticket belongs to a sibling card.

Why not fold it into the install price? Because network time varies by an order of magnitude between houses, and a price that covers the bad house overcharges the good one. A visible clock also stops "while you're here, can you fix my printer" from becoming an unpaid hour, since the customer can now decide whether the printer is worth the time.

The words that make it work are said at the moment the device fails to connect, not at the end:

TECH: The thermostat's in, but it keeps losing
      your Wi-Fi. The signal at this wall is weak.
CUSTOMER: Can you just fix the Wi-Fi?
TECH: I can find out why. Your Wi-Fi is your
      equipment, so it's not part of this job.
      The first fifteen minutes are on us. After
      that it's our normal rate, in quarter hours.
CUSTOMER: How long will it take?
TECH: Fifteen minutes to tell you what I'd do.
      I won't change anything on your router
      without asking you first.
CUSTOMER: Okay, go ahead.

Three things are done in that exchange: the boundary is named without refusing, the clock is stated, and the customer is told the router stays theirs.

Worked example: the thermostat at the end of the hall

The job. An HVAC tech installs a connected thermostat, quoted at 1.0 hour. The thermostat joins the Wi-Fi during setup and then drops off within minutes, repeatedly. The house runs on the internet provider's gateway in the basement, at the far end of the house from the hallway. The customer works from home on an employer laptop.

Rung 1, observe. The thermostat's own diagnostic page reported its received signal at about -79 dBm, and a phone app read about the same at that wall. The thermostat's sheet asks for a stronger signal than that (read from the sheet; how to measure and judge a reading belongs to a sibling card). The cause is distance and two floors of house, not a fault in the thermostat.

The conversation. The exchange above, word for word in substance. The customer agreed to the extra time.

What the tech did not do. The gateway is the provider's, possibly managed remotely, and the employer laptop runs a VPN on the same network. Changing the Wi-Fi name, the bands or the gateway's channel settings would risk breaking the customer's working day for a thermostat. Those were rung 4 changes on a network with two other owners in the picture, so they were off the table without the provider's involvement.

The options put to the customer. (a) Move the gateway to a more central spot, which needs the provider's cable moved, so it is the provider's job. (b) Add a mesh node on the stair landing, wired into the gateway's network by the gateway's own pairing button, a rung 5 sale. (c) Leave it and accept a thermostat that drops. The customer chose (b).

The time, with the arithmetic shown. Diagnosis and the conversation took 0.4 hour. The first 0.25 hour was included, leaving 0.4 - 0.25 = 0.15 hour, which bills as one 15 minute increment, 0.25 hour. Setting up the mesh node, guided by the customer on her own provider app (rung 3, so she pressed the buttons), took 0.5 hour, billed on its own line with the node itself. Total billable network time: 0.25 + 0.5 = 0.75 hour, on top of the 1.0 hour install as quoted.

The record. The ticket notes: signal at the thermostat before (-79 dBm) and after the node (about -58 dBm at the same wall), no gateway settings changed, node added and paired by the customer, Wi-Fi name and password unchanged. That last line is the one that ends the "everything broke after your visit" call before it starts, because nothing the tech did could have disconnected anything else.

What would have changed the call. If the customer had said the work laptop dropped every afternoon too, the problem is the network itself, not the thermostat's corner of it, and the right answer is that the network needs its own visit, from you as a separate quoted job if your shop does that work, or from the provider. If the tenant of a rental had asked for the gateway's settings changed, the answer is no until the landlord or the account holder authorizes it, whatever the tenant says.

References

• Computer Fraud and Abuse Act, 18 U.S.C. 1030, and your state's computer crime statute
• Your insurance agent, on whether your general liability policy covers technology or professional services, and on technology errors-and-omissions coverage
• Internet provider subscriber agreements and gateway documentation, read by the customer
• See related: The Customer Network Change Authorization SOP; Writing the Scope Line for Network and App Setup; Home Wi-Fi for the Trades; Measuring Wi-Fi Signal Where the Equipment Lives