Never miss an after-hours leak call again.

Jim is forty-seven years old. He's been doing commercial plumbing for twenty-three years, the last nine of those running his own shop. His business is the kind of thing that's invisible until it isn't: he services the East Bay's mid-tier commercial properties — office buildings, mixed-use, a few hotels — and the people who pay him are mostly property managers who only call when something has already gone wrong.

His clients call him on a number he's had since 2014. The number is on the side of his truck, in their CRM under "plumber," and in maybe forty different group texts at any given moment. About a third of those calls come outside business hours. A burst pipe on a Saturday night doesn't wait until Monday. A water heater dumping into a lobby at 11pm doesn't either.

The way Jim used to handle all this was: Jim handled all this. Every voicemail, every text, every callback, every dispatch decision. His wife knew the second the work phone buzzed at 9:30 on a weeknight that dinner was over.

The day before OpsLight

Jim's day used to start at 5:45am with him scrolling through voicemails on the work phone. He'd listen to each one, jot the property address on a yellow pad, decide whether it was urgent enough to wake somebody up, and start making callbacks by 6:30. By 8am he'd usually have triaged 6–10 messages and texted the right plumber to head where.

The problem wasn't volume. The problem was that everything lived in Jim's head and on a yellow pad.

If Jim was in a meeting with a property manager and three voicemails came in, those voicemails sat untriaged until he was done. If one of those was a real emergency, somebody was waiting an extra forty minutes for a callback. If Jim was on vacation — which he basically wasn't, because of this — he had to ask one of his plumbers to play dispatcher on top of doing actual plumbing work.

He'd tried two software platforms. The first was ServiceTitan, which is the gold standard for plumbing — but it priced out at roughly $500 per user per month, plus $25,000 in implementation, plus mandatory training, plus a setup cycle measured in months. For a four-person shop, that math doesn't pencil. The second was Jobber, which is friendlier but assumes his plumbers will live inside an app — and his lead tech, Eddie, is 58 and will text but flatly will not install something on his phone "for work."

So Jim's actual operations software was: a yellow legal pad, the Voicemail app on his iPhone, three group texts (one per plumber), and his memory.

That last point matters more than it sounds. Plumbing dispatch isn't really about routing emergencies. That part is easy. The hard part is the dozens of small, contextual judgments: this property manager will tip if her tech is there in under an hour; that one needs a written estimate before her board signs off on anything; that other one will pay double if you can get there before her morning meeting. Those judgments don't fit into a generic ticketing system. They live in the operator's head.

How Jim found OpsLight

One of his property manager clients runs a small portfolio that uses a stone restoration vendor we'd already wired up with OpsLight. She mentioned to Jim that her stone guy was getting back to her on Saturday voicemails inside of ten minutes, and could she give Jim the contact who set it up.

Jim's first call with us was thirty-five minutes. We asked him: what does an emergency mean to you? He gave us seven keywords — burst, flooding, no water, sewage, leak in unit, fire suppression, lobby — and the rule that anything mentioning those gets a callback inside forty-five minutes regardless of time of day.

We asked: which property managers want a written confirmation before you dispatch? He named four out of his roughly twenty accounts. We asked: which plumber takes which kind of call? Eddie does anything commercial that involves a permit. Marcus does after-hours residential. Devon does new construction rough-ins. Anything that doesn't fit those goes to whoever's closest.

That conversation was the OpsLight install brief. We turned it into a classifier prompt, configured the Sheet schema with Jim's account list, wired up his existing Twilio number, and put him live two weeks later. The first day, OpsLight handled 11 inbound voicemails and 4 texts. Jim didn't write anything on a yellow pad.

Three moments from a regular Tuesday

Six months later

The change in Jim's operation is measurable but not in the way you'd expect. He's not handling more calls — he's roughly the same volume he always was. He's not pricing differently. His revenue per plumber is up about 4%, which he attributes to faster callbacks closing more emergency work that used to leak to competitors.

What's different is something harder to quantify. Jim's wife told us that he hasn't gotten up from dinner in four months to take a voicemail. His on-call plumbers say they know exactly which call is "real" without listening to twelve seconds of preamble to figure out if it's an emergency or somebody calling about a dripping faucet at noon on a Wednesday.

And the Sheet — the Sheet has become something Jim didn't expect. Every Friday afternoon at 4pm, OpsLight emails him a one-page recap of every call, every dispatch, every job logged that week. The first Friday recap, Jim said, was the first time in nine years he'd seen his own business at a glance.

What's configured specifically for plumbing

• Plumbing-vocabulary intake classifier. The prompt knows fixtures (toilet, sink, water heater, dishwasher line, sump pump, sewer cleanout), failure modes (leak, burst, slow drain, no pressure, no hot water, backflow), and code-trigger terms (cross-connection, RPZ, anti-scald valve).
• Emergency keyword list. Burst, flooding, sewage, no water building-wide, fire suppression, gas smell, freeze damage. Any of these in a voicemail trigger immediate SMS to the on-call plumber.
• Property-manager account list. Each account has a contact, response-time preference, callback-style preference, and a flag for "wants estimate before dispatch."
• Crew dispatch logic. Eddie / Marcus / Devon rules, plus a fallback to "closest available" based on the last logged check-in location.
• Plumbing-specific reports. Daily Game Plan shows active jobs with permit status. Monthly status emails to property managers include all work performed at their properties that month, parts replaced, and any code-related observations.
• Common-document templates. Backflow test report, repair quote, change-order for scope creep, end-of-month service invoice.

What other plumbing contractors ask us

Related trades