Same QR, two modes: how TuffOps replaces the "which unit is it?" phone call.

That phone call is one of the most expensive things in field service. It happens dozens of times a week at any active shop. It eats office time on the front end, eats tech time on the back end when the wrong unit gets diagnosed, and creates a service record that's missing a clean device link from the moment it's created.

We replaced it with a sticker. Every unit in TuffOps has a QR code on it. When you scan that QR code, what you see depends on who you are.

One physical sticker, two access-controlled experiences

Same QR. Same URL. The system knows who's scanning — authenticated tech, or unauthenticated end customer — and serves the right experience.

The customer never has to know your phone number, your website, or which unit is broken. They aim a phone camera at a sticker on the equipment that's giving them trouble. The form they get is already tagged with which unit it is, who owns it, where it lives, and what's been done to it before. They fill in "making a loud noise" and hit submit.

Where the requests land — and why that matters

The submitted request appears in the TuffOps dispatch dashboard as a service request, with the unit, the customer, and the property already linked. From there, it's a one-click conversion to a work order, then assigned to a tech.

The thing to notice is what didn't have to happen:

• No call answered, no triage script, no time on hold.
• No "which unit are you talking about?" exchange.
• No customer-data entry by the office. The QR is property-aware, so the request lands attached to the right account.
• No re-keying of equipment data. The unit is already in the system; it's already on the request; it's already on the work order.

Because the QR is device-specific, the request — and the work order it becomes — is also device-specific. That tag travels with the job from intake through invoice. The tech rolls up to the property already knowing which physical unit needs attention. The work order, the photos, the parts, the labor, the refrigerant, the warranty record, and the eventual invoice are all pinned to the right asset from the first second.

Want to see the customer flow on a real phone? Book a 30-minute demo and we'll let you scan a TuffOps QR sticker and watch the request appear in dispatch in real time.

Where the idea came from

Like the rest of TuffOps's HVAC-specific feature set, this one came out of conversations with The Finished Touch Limited — the largest HVAC contractor in St. Kitts and Nevis, ten years in business, primarily commercial, running TuffOps in production.

TFTL's original website was a single page. It wasn't well developed because it didn't have to be — most of their work was arriving by phone call. That sounds fine until you start counting the actual cost: every call had to be answered, triaged, transcribed into the dispatch system, and then re-clarified with the customer to figure out which physical unit on which property was actually the issue. At their volume, that was several full hours of office labor a week burned on intake friction alone, before a tech ever turned a wrench.

The right fix wasn't "build a fancier website." The right fix was: put the request capture on the equipment itself, with all the context the office would otherwise have to ask for already attached.

So we did. Same QR sticker the techs were already using for in-field lookups. Same URL. Different experience for an unauthenticated visitor.

Privacy by design

The customer-mode flow shows a service-request form. That's it. It does not display:

• Other customers' information.
• This customer's service history, pricing, invoices, or notes.
• The unit's full equipment record, refrigerant log, or warranty terms.
• Any internal-facing data, ever.

If the QR is scanned by someone with no relationship to the property — a curious neighbor, a delivery driver — the only thing they can do is submit a service request that lands in the dispatcher's queue with a flag for review. They cannot read anything sensitive. There's nothing to read.

The same sticker, scanned by an authenticated TuffOps tech account, returns the full record. Permission is determined by who's holding the phone, not by what's printed on the label.

What this gets you, day-to-day

What competitors offer (and don't)

We looked. None of the major HVAC field service platforms — Housecall Pro, ServiceTitan, Jobber, FieldEdge, ServiceTrade, BuildOps — offers a unit-mounted QR code that lets an unauthenticated end customer scan it and submit a service request that lands pre-tagged in the dispatcher's queue.

The closest things on the market today are:

• Generic online booking forms. Most of the platforms above offer a "request service" form on the contractor's website. The customer types out their address, picks a service category, and writes up the problem. Nothing is auto-tagged. Dispatch still has to figure out which unit.
• Tech-only QR scanning. A few platforms offer QR codes for internal use — techs scan them to pull up an equipment record. That's useful, but it doesn't replace the customer-side phone call.
• Third-party add-ons. A handful of niche tools (mostly built for facility management, not residential or commercial HVAC contracting) offer QR-driven request forms, but they don't integrate cleanly with field service dispatch and don't give the customer access-controlled experiences.

None of those is the same product. None of them put a single sticker on every unit that serves both audiences with the right access-controlled experience and lands the request directly in the dispatcher's queue, pre-tagged to the device. We built ours that way because that's the way it actually replaces the phone call.

How it pairs with the customer portal

The QR-and-form flow is the unauthenticated front door — the no-friction way for a customer to start a service request without having to dig up your contact information. Once a customer is set up with a portal account (free for them, included on Pro and Enterprise), the same QR can take them to a richer experience: their service history on this unit, prior invoices, warranty status, and the request form.

For a property manager with twenty units across five buildings, that means scanning a sticker on a misbehaving condenser pulls up: "Your last service on this unit was March 14, here's the invoice, here are the photos the tech took, the warranty is active until 2031, and yes — please send someone." All from a sticker.

For a one-time scan from a tenant or a neighbor, the same sticker just opens a request form. No account. No history. No leakage. More about the customer portal here.

Available where

The customer-facing QR scan-to-request flow is included on the Pro and Enterprise plans, alongside the rest of the customer portal (online invoices, payments, equipment status, quote approvals, service history, and direct messaging).

Tech-side QR scanning for in-field service-history lookups is available on every plan. Every unit you create in TuffOps has a unique QR you can print and stick on the equipment.

The bottom line

The "which unit is it?" phone call has been a hidden tax on every HVAC shop in the country for as long as the trade has existed. Most contractors stopped noticing it because there was nothing they could do about it.

There is now. A sticker on the equipment. A camera on a phone. Two access-controlled experiences served from the same URL. A request that lands in dispatch already tagged with the right device, the right customer, and the right history. One click to a work order. The tax goes away.

It's the same architectural choice behind linked equipment groups and the way checklists are bound to the equipment rather than to the appointment: in HVAC, the durable thing is the equipment. Build the workflow around it, not around the next visit.

← Back to all posts