If you have never sent a technician into a colocation cabinet on your behalf, the first remote hands ticket can feel like a leap of faith. You are asking a stranger to touch production hardware in a building you may never have walked through. The good news is that a well-run visit is predictable from start to finish. Here is how a typical remote hands job actually unfolds, so you know what to hand over and what you should receive when it is done.
1. The request: tell us the site and the scope
Everything starts with a clear ticket. You open a request through the request form or by phone, and you tell us three things: which facility your gear lives in, which cabinet or cage it sits in, and exactly what needs to happen. The more specific you are, the faster and cleaner the visit goes. Useful details include the rack and unit position, device labels or serial numbers, a photo of the front and rear if you have one, and any remote console or IP information the technician may need on site.
You do not need to know the perfect wording. If you are unsure whether your task is basic physical work or skilled configuration, our services overview lays out what falls under remote hands versus smart hands. Before anyone is dispatched, we confirm the scope back to you along with access requirements, an estimated time on site, and hourly billing, so there are no surprises. Our full process is designed so nothing starts until you have approved it.
2. Access and escort: getting onto the floor
This is the step most people underestimate. Data centers do not let anyone walk to a cabinet. Every facility has its own badging, ticketing, and escort rules, and many require you, the customer of record, to authorize a named visitor in the facility portal before we arrive. For interconnection sites and carrier hotels, there may be a separate work-order or meet-me-room process on top of building security.
Because we are local and already work these buildings, we handle the on-the-ground logistics and tell you precisely what authorization we need from you. If your gear is spread across several buildings, the same team can cover them, which you can see on our data centers page. Practically, this means you should expect one short administrative step on your side (adding the visitor to your access list) and then very little else until the work begins.
3. The work: hands on the hardware, updates as we go
Once the technician is badged in and at your cabinet, the actual task usually moves quickly. Whether it is a drive swap, a reboot, reseating a cable, staging a new switch, or landing a cross-connect, the technician works to the scope you approved and stops to check in if reality on the floor does not match the ticket. That last part matters: if the part you shipped is the wrong model, or a cable is not where the diagram said, you get a message before we improvise, not a surprise afterward.
You should expect photos. Good remote hands work is documented as it happens, not reconstructed later. Typical updates include a shot of the cabinet before work starts, the specific ports or components involved, serial and asset labels, and the final state after the task is complete. This gives you a verifiable record of exactly what was touched, which is especially valuable when your own staff is hundreds of miles away.
How long does it take?
Timing has two parts: dispatch and hands-on time. Dispatch depends on how quickly access is authorized and how urgent the ticket is; a local technician can often reach a metro floor the same day, including nights and weekends. Hands-on time depends on the task. A power cycle or single swap may take minutes once someone is at the rack, while structured cabling, a multi-device rack and stack, or careful diagnostics can run longer. Because billing is hourly and transparent, you are paying for time actually spent, and the estimate you approved sets the expectation.
4. The report and invoice: proof, then billing
When the work is finished, you receive a short close-out: what was done, any deviations from the original scope and why, the photo set, and any readings or outputs the task produced (a link light, a POST screen, a console confirmation). If a follow-up is needed, such as an RMA on a failed part, that is flagged clearly so you can decide the next step.
The invoice reflects the documented time and any agreed materials. There is no padding for a facility smart-hands desk markup; independent hands typically cost a fraction of what a facility charges through its own remote-hands program, and you see the hours rather than a flat mystery fee. The photo record and the invoice line up, so you can reconcile the two at a glance.
What a good visit should leave you with
- A ticket that was confirmed back to you before anyone was dispatched.
- Clear guidance on the one access step you needed to complete.
- Photos of the before state, the work itself, and the after state.
- A written close-out noting any deviation from the original scope.
- An hourly invoice that matches the documented time on site.
None of this is exotic. It is simply what a professional, independent visit looks like when the goal is to make remote hardware feel as close to being there yourself as possible.
Related reading
Remote Hands vs Smart Hands
Where basic physical work ends and skilled configuration begins, and how each is scoped and billed.
GuideWhat Is a Cross-Connect?
How physical interconnections work inside a data center and what a turn-up involves.
ChecklistRack and Stack Checklist
What to prepare and ship so a rack and stack visit goes cleanly the first time.
ResourcesAll resources
Browse every guide and checklist in the RemoteHands.nyc library.
Ready when you are
When you have a task that needs a physical touch, request service and describe the site and scope, or call dispatch at (707) 733-3342. We answer 24/7, confirm access and pricing before any work starts, and send photos when it is done.