Where do providers draw the line between remote hands and smart hands?
There is no single industry definition, so the line depends on the provider. Many describe remote hands as basic, clearly defined tasks such as restarting a server or checking an indicator, and smart hands as work that needs deeper skills, such as installing or repairing hardware and configuring networks. Others use the two names for the same thing, and some bundle hands-on work under the remote hands name.
Where providers do split the two, they often bill them separately. That is why two quotes with the same label can cover very different work. Compare what is included, not what the service is called.
How do we scope remote hands and smart hands?
We scope remote hands as precise tasks that you describe step by step, and smart hands as tasks where the engineer may also troubleshoot. In both cases you send the request by ticket, email or phone, and you receive photos and work notes when the task is done.
Planned refreshes, migrations and decommissioning sit in a third group, scheduled project work. That work follows a written method of procedure agreed in advance and ends with a closeout report, because the risk and the number of steps are higher than a single request can carry.
How do you write a request so the boundary is clear?
State the goal, the steps you want followed, and what the engineer must not do. The more a task depends on judgment, the more your request should say about limits.
- Name the device, rack, U position and port, or give a photo or label to match.
- List the steps in order, and say which step to stop at if something looks different.
- State what the engineer may touch and what must stay as it is.
- Say what evidence you want back, for example a photo of the port lights.
- Give access details and any escort or change window rules for the site.
The verdict
If you can write the steps, remote hands is usually enough and keeps the engineer's actions predictable. If you are diagnosing, or you cannot guide the work live, smart hands is the safer choice because the engineer can act on what they find. If the work is a planned refresh or migration, neither fits well, and scheduled project work with a written procedure is the better choice.