What is the difference between Remote Hands and Smart Hands?
Remote Hands is hands-and-eyes support. Someone on site looks at equipment, reports what they see and performs simple physical actions you authorize. Smart Hands is technically capable support. The on-site person installs or replaces hardware, patches fiber and copper, connects to consoles and helps troubleshoot at the physical layer.
Providers draw the line in different places, so the useful question is not which label to use but which actions you need performed.
Remote Hands vs. Smart Hands at a glance
The table summarizes where providers usually draw the line. Always confirm the exact tasks in the service scope, because the boundary varies.
Scroll the table sideways for more.
| Remote Hands | Smart Hands | |
|---|---|---|
| Purpose | See, confirm and perform simple authorized actions | Install, replace, connect and troubleshoot at the physical layer |
| Typical tasks | Inspection, photographs, serial numbers, cable checks, console connection, authorized power cycle | Switch and router installation, rack and stack, patching, optic and component replacement, RMA handling |
| Skill needed | Careful, reliable and able to follow instructions | Technically capable with network hardware and cabling |
| Who directs | Your remote engineer, step by step | Your remote engineer, with more latitude on how physical steps are done |
| Best for | Routine, recurring or quick checks | Complex, urgent or change-window work |
| Evidence to ask for | Photographs and a record of what was seen | Photographs, serial numbers, port map, exceptions and test results |
What tasks does Remote Hands cover?
- Visual inspection and photographs of equipment and status lights
- Identifying a device in a rack and confirming serial numbers
- Checking that a cable is seated and which port it occupies
- Connecting a console cable so a remote engineer can reach a device
- Power-cycling a device when the remote engineer authorizes it
- Receiving and logging a delivery
What tasks does Smart Hands cover?
- Racking and cabling a switch, router or firewall
- Replacing a failed power supply, line card, optic or hard drive
- Re-patching fiber or copper to a new port map
- Tracing a cable end to end to find a physical fault
- Assisting with an approved software upgrade while the engineer drives
- Coordinating an RMA with the vendor and packing the returned unit
How do you choose between Remote Hands and Smart Hands?
If the job is to look, confirm or press a button, Remote Hands is usually enough. If the job changes what is installed or connected, plan for Smart Hands. If you are unsure, write the full sequence of physical steps and ask whether each can be done as described.
Which scenarios call for which?
- A remote engineer needs to know whether a link light is on: Remote Hands
- A line card has failed and must be replaced in a window: Smart Hands
- A device must be power-cycled after your engineer authorizes it: Remote Hands
- A new switch pair must be racked, cabled and labeled: Smart Hands
- Serial numbers and rack positions need capturing for an audit: Remote Hands
- Fiber needs re-patching to a new port map with optics swapped: Smart Hands
How do you write a good Remote Hands request?
- Location: facility, suite or cage, rack and rack unit
- The exact steps, in order, and which need your approval first
- What will be on site: parts, cables, optics, consoles
- Access window and who can authorize entry
- The evidence you want back, such as photographs or serial numbers
How do you choose the right level for a task?
Match the task to the skill it needs, not to the label.
- Looking at lights, reading labels or confirming a device is on: hands-and-eyes support
- Power cycling or reseating a cable on your instruction: hands-and-eyes support
- Replacing a failed switch, server component or optic: technically capable support
- Patching fiber or copper to a port map: technically capable support
- Connecting to a console and following a script you provide: technically capable support, if the scope allows
