Remote Hands vs Smart Hands: What Is the Difference?

If you have ever opened a data center ticket, you have probably seen both phrases used as if they mean the same thing. They do not, quite. "Remote hands" and "smart hands" describe two different levels of on-site help, and the line between them decides how a job gets scoped, who performs it, and what you are billed. Knowing which one a task actually needs is the easiest way to keep a visit fast and its cost honest.

The short answer

Remote hands is basic physical work: someone standing at your cabinet acting as your eyes and fingers, following simple instructions. Smart hands is skilled technical work: someone who can log into equipment, read what it is telling them, and make decisions about configuration and repair. Remote hands moves the atoms. Smart hands understands the bits.

What remote hands means

Remote hands covers the physical, low-judgment tasks that only need a trusted person in the building. You already know what needs to happen. The technician simply carries it out and documents it. No login credentials, no protocol knowledge, no troubleshooting required.

Typical remote hands tasks include:

• Power-cycling a frozen server or rebooting an appliance you cannot reach remotely.
• Reading and reporting a status LED, a POST code, or a display panel so you know what state a box is in.
• Reseating a cable, a drive, an SFP, or a memory module that has worked loose.
• Swapping a labeled part you shipped in, following your written steps.
• Receiving a delivery, checking serials against a packing list, and photographing the contents.
• Labeling ports, confirming which cable runs where, and taking cabinet photos for your records.

The defining trait is that the instructions are explicit and the outcome is easy to verify. If you can describe the whole job in a few plain sentences, it is almost certainly remote hands.

What smart hands means

Smart hands is the same physical presence plus real technical skill. Here the technician is not just moving parts, they are making judgment calls: interpreting error output, choosing between fixes, and working from a console rather than a checklist. This is the work that would otherwise pull one of your own engineers onto a plane.

Typical smart hands tasks include:

• Consoling into a switch, router, or firewall to load a config, recover access, or stage new gear.
• Installing or repairing an operating system, and setting up BIOS, BMC, iDRAC, or iLO.
• Diagnostics and troubleshooting: isolating a failing part, testing a run, and confirming a fix rather than just reporting a symptom.
• Running and terminating structured cabling, or turning up a cross-connect to a labeled port and verifying the link.
• A full rack and stack: mounting gear, landing power, dressing cabling, and bringing systems up to a known-good state.

For a deeper look at the skilled end of the spectrum, see our smart hands service page. The short version: if the task needs someone to think on their feet, it is smart hands.

A quick way to tell them apart

Ask yourself one question: could you hand the instructions to any careful person and get the same result? If yes, it is remote hands. If the job needs someone who understands the equipment well enough to react to what they find, it is smart hands. Most real visits are a mix, and that is fine. The point is to scope each step for the skill it actually needs.

How billing differs, and why it matters

Because the two tiers require different skill, they are usually billed differently. Basic remote hands is the lower rate, since it is fast, low-risk work. Smart hands carries a higher rate because it takes a qualified technician and more care. That split is not a catch, it is the whole advantage: you should only pay the skilled rate for the parts of a job that are genuinely skilled.

Our billing is built around that split. A reseat and a photo bill as remote hands, a console session to recover a locked switch bills as smart hands, and a visit that includes both is itemized so you can see where the time went. Time is counted in 30-minute increments. Each visit has a minimum charge that covers the technician's travel to and from the site. On longer jobs we can bill only the hours worked and waive the travel charge. A facility's own smart hands desk bills on its own published terms, and those terms differ by operator and by contract, so read the remote hands section of your colocation agreement and its rate card before you assume how a task there will be billed. We do not claim a price relationship between the two. Compare your rate card against our rate sheet for your own sites.

Our approach is transparent hourly billing with the tier stated up front and every visit photo-documented, so the invoice matches the work. The pricing and billing page lays the whole model out, and we confirm the scope, tier, and an ETA before anyone touches your gear.

The labels differ by provider

The split above is how we scope and bill. Not every provider draws the line the same way, and some do not draw it at all. Equinix, for example, uses "Smart Hands" as the name of its whole on-site support service at its IBX data centers, covering everything from power cycling and moving a shipment from the dock to troubleshooting and installation (Equinix Smart Hands documentation, checked 2026-09-21). Other providers use the two terms as synonyms, and some use "remote hands" for everything.

So when you compare quotes or read a colocation contract, do not rely on the label. Scope by task: write down what has to happen at the cabinet and ask each provider what that specific job bills at. The name on the line item matters less than what it covers.

Which one do you need?

Start from the task, not the label. Write down what has to happen at the cabinet. If it reads like a set of simple instructions, ask for remote hands and keep it cheap. If it reads like a problem to solve, ask for smart hands and get someone qualified the first time, instead of paying for a second dispatch when a basic visit cannot finish the job. When you request service, describe the outcome you want and we will tell you honestly which tier fits.

Either way, the same NYC-local team can reach your gear across the data centers we cover, day or night, so you are not choosing a provider by tier, only a scope by task.

Questions people ask

Is smart hands billed higher than remote hands?

Yes. Smart hands is the higher of our two hourly tiers, because it needs a technician who knows the gear and can make judgment calls. Remote hands is the lower tier. We do not publish the rates; the pricing and billing page explains the model and how to get a rate sheet.

Can one visit include both?

Yes, and most real visits do. A cabinet build is remote hands until the gear powers up and has to be configured. A cross-connect is basic hands to land the cable and smart hands to prove and configure the link. One technician does both, and the invoice is itemized by tier so you only pay the skilled rate for the part that needed it.

Which one should I ask for?

Describe the task, not the tier. If it reads like a set of simple instructions anyone careful could follow, it is remote hands. If it reads like a problem to solve, it is smart hands. When you open a ticket we tell you which tier fits and confirm it before anyone is dispatched, so you do not have to guess.

Do all facilities use the same terms?

No. Some operators use "smart hands" as the name of their entire on-site support service, some treat the two terms as synonyms, and some use "remote hands" for everything. Your colocation contract defines what "basic remote hands" means for your account, and that definition is the one that counts at that site. Scope by task and ask what the specific job bills at.

Related reading