How to choose a remote hands provider: 12 questions 90 percent do not ask

It’s 3:00 AM and your UPS is alarming. The technician arriving at nine comes from another city, knows your cabling from memory, and your coordinator doesn’t answer the phone. None of this is in the contract, and the difference is discovered just when the problem gets serious.

Most companies choose a remote hands provider by comparing hourly price, as if all hours cost the same. They don’t. An hour of someone who arrives blind costs more than three hours of someone who already knows your compute room. These are the twelve questions that separate a cheap quote from a reliable service.

Real coverage and availability

The hourly price says very little about who arrives, at what time, and with what preparation. These three questions define the distance between a provider who lives near your team and one who dispatches just anyone.

1. Do you have technicians assigned to my city or area, or do you bring them from another city? It matters because response time is measured in real minutes of travel: one hour of travel equals two hours of your waiting time. A red flag is “we cover the whole country,” because it means there isn’t one nearby.
2. What hours do you cover and what happens at 2:00 AM or on weekends? It matters because half of the incidents that justify remote hands occur outside business hours. A red flag is a published schedule without a person backing it up, with a night surcharge that no one mentioned in the quote.
3. Who is the technician assigned to my rooms and since when do they work with our team? It matters because accumulated knowledge of a room is worth more than any paper certification. A red flag is “we assign according to availability,” which in practice means you’ll meet someone new every visit.

Escalation and who goes up

A technician resolves 80% of what you hand them. What’s critical is what happens with the remaining 20%, and that answer is almost never written down.

1. What happens when the on-site technician cannot resolve the problem? It matters because many failures require architectural judgment, not a tool in hand. A red flag is that escalation depends on the technician calling “if they think it’s necessary,” without times or a responsible person.
2. Who goes up the escalation level and with what maximum response time, measured by the clock? It matters because escalation without a clock is a promise, and promises aren’t billed. A red flag is a time expressed as “as soon as possible,” which could be 3:00 AM or next Monday.

Evidence and traceability

Here you decide whether you’ll be able to demand anything later. A provider who doesn’t leave a written record of their work will hardly answer for that work.

1. Do they deliver evidence of the work: before-and-after photos, video, or capture of the change? It matters because without evidence, any subsequent failure becomes a memory discussion. A red flag is “we left everything as it was,” which also sounds like they hid the change.
2. Is there a log per intervention with arrival time, departure time, and technician name? It matters because that log is the evidence you use to bill, to audit, and to negotiate renewals. A red flag is a generic monthly report, without time or person’s name.
3. Can they share physical access logs and work orders from last month? It matters because it demonstrates that control exists and that it’s applied to you as with any client. A red flag is “we don’t deliver documentation,” which usually comes with them not having it either.

Security and credentials

A remote technician enters your room and handles keys, users, and credentials. It’s an open door to your operation, and it’s quoted as if it were the same as the rest of the service.

1. Do you handle my remote access credentials and who keeps them when the contract ends? It matters because a password that isn’t revoked is a security debt that no one quoted. A red flag is that the technician keeps them “in case we need to come back,” or that credentials live in a notebook.
2. Do you have information security certifications and two-factor access control? It matters because an audited certification demonstrates that someone external reviews their processes. A red flag is “we are ISO certified” without number, scope, or verifiable auditing entity.

Costs, minimums, and penalties

This is where the quote changes shape after signing. Asking the amounts beforehand avoids the uncomfortable conversation during the incident.

1. How is an emergency visit billed and is there a minimum of hours or monthly spend? It matters because the minimum turns a one-hour call into a fixed charge, and the emergency surcharge must be written, not assumed. A red flag is a “depends on the case” without a table, meaning the price is decided by the technician who arrives.

Exit and transition

Nobody thinks about this until the renewal month arrives, and by then there’s no room for negotiation.

1. What happens with my keys, credentials, equipment, and documentation when the contract ends? It matters because the exit defines whether you can change providers without stopping your operation for two weeks. A red flag is that documentation is delivered “if you request it,” without deadline or format.

The twelve questions fit in one hour of meeting and all are answered in writing in the proposal. A serious provider answers them without feeling like you’re interrogating them, because they’re the same questions you ask anyone to whom you entrust the keys to your room. What they don’t answer clearly… is already warning you about what you’ll suffer the day a failure occurs.

Sources

1. ISO/IEC 20000-1 — Service level agreements: what an SLA must define — https://www.iso.org/standard/20000-1.
2. Google SRE: Service Level Objectives — https://sre.google/sre-book/service-level-objectives/.
3. Google SRE Workbook: error budget policies — https://sre.google/workbook/error-budget-policy/.
4. PeopleCert: ITIL 4 for incident management — https://www.peoplecert.org/itil-4.