Scene
It's Tuesday morning. The phone rings. A property manager on the other end says, "Hey, one of the AC units is acting up — can you send someone?"
You know the property. There are nine units across three buildings. Which one?
Three minutes of back-and-forth. "The one on the second floor of building two." Which side? "The east side, I think." Indoor or outdoor unit? "The thing inside the closet." Now your dispatcher is searching old work orders for the right serial. The tech still might pull up and find the wrong unit labeled.
That phone call is one of the quiet expensive ones. It eats office time on the front end, 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.
The important part is not the QR code itself. It is where the request lands: already tied to the unit, customer, and property before dispatch touches it.
One physical sticker, two access-controlled experiences
The dedicated HVAC QR code service requests page shows how this turns vague customer messages into equipment-aware requests, and the customer portal keeps the rest of the customer record easy to reach.
Same QR. Same URL. The system knows who's scanning — authenticated tech, or unauthenticated end customer — and serves the right experience.
Authenticated. Full record access.
- Full service history for the unit
- Pending work orders already assigned to this device
- Linked equipment group members and shared system history
- Refrigerant log, leak rate, repair history
- Warranty status and install date
- Customer-facing notes and photos
Unauthenticated. Request flow only.
- A short service-request form, pre-tagged to this exact unit
- "What's the problem?" and contact-details fields
- No service history, no pricing, no internal notes
- No login, no app install, no portal account required
- No exposure of any non-public information about this property or any other
No app. No password. No account.
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.
The fix belongs on the equipment
The shops that pushed us toward this flow were not trying to replace every phone call. They were trying to remove the calls where the only hard question was, "which unit is it?"
That sounds small until you count it. Every vague call has to be answered, triaged, typed into dispatch, and then clarified with the customer. The right fix was not a fancier website form. The right fix was request capture on the equipment itself, with the context the office would otherwise have to ask for already attached.
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
Fewer phone calls
Customers who'd otherwise call to report a problem just scan and submit. Office picks up the time previously spent on intake triage.
No "which unit?" tag
Every request is pre-tagged with the device. The "is it the upstairs one or the downstairs one?" exchange disappears.
Faster dispatch
One click converts the request to a work order, fully attached to the right unit and customer. Assign it to a tech and you're done.
Cleaner records from day zero
Because the work order is device-tagged from the moment it's created, the service history attached to that unit stays accurate without manual cleanup.
No customer app to install
No download, no signup, no password. The customer aims their camera at a sticker. That's the entire onboarding.
Tech context on the same QR
The same sticker the customer uses to file a request is the one the tech scans for service history when they arrive on site. One label, two jobs.
Works with linked equipment groups
If the unit is part of a linked system, scanning brings up the group context — so the tech can see whether the matched evaporator or condenser was visited recently and what was done.
An after-hours intake channel
The form works at 2 a.m. on a Sunday. By the time the office opens Monday, the request is in the queue with everything needed to schedule it.
Why generic booking does not solve this call
Online booking and customer portals are useful intake channels, but they are not the same as a unit-mounted QR that creates a device-tagged request from an unauthenticated scan. The difference is where the request begins: with a generic booking form, or with the exact unit the customer is standing next to.
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.
Those patterns can still leave dispatch asking the same first question. A unit QR request starts with the asset, so the office can move straight to scheduling and triage.
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.
FAQ
Can anyone who scans the QR code see unit history?
No. An unauthenticated scan only opens the service-request flow. Full unit history, pricing, internal notes, invoices, and refrigerant records require an authenticated account with permission to view the property.
Does the customer need a portal login to submit a request?
No. The low-friction flow is intentionally login-free. Portal customers can get a richer experience, but a tenant or property contact can still scan the label and submit the issue.
Where it lives in TuffOps
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.
See how unit QR codes work
Book a 30-minute walkthrough. We'll let you scan a real TuffOps QR sticker on a phone and watch the service request appear in the dispatch board, then walk through the tech-mode experience on the same code.
Book a demo