How to choose a remote hands provider: 12 questions 90% don’t 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 that is in the contract, and the difference is discovered just when the problem gets serious.
Most companies choose a remote hands provider by comparing the 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 computer room. These are the twelve questions that separate a cheap quote from a reliable service.
Coverage and real 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 that lives near your equipment and one that dispatches anyone.
- Do they have technicians assigned to my city or area, or do they bring them from another city? Important because response time is measured in actual transit minutes: one hour of travel equals two hours of your waiting time. A red flag is “we cover the whole country”, because it means there is none nearby.
- What hours do they cover and what happens at 2:00 AM or on weekends? Important 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 no one mentioned in the quote.
- Who is the technician assigned to my rooms and since when do they work with our team? Important because accumulated knowledge of a room is worth more than any paper certification. A red flag is “we assign based on availability”, which in practice means you will meet someone new on every visit.
Escalation and who goes up
A technician resolves 80% of what you hand them. What is critical is what happens with the remaining 20%, and that answer is almost never written down.
- What happens when the on-site technician cannot solve the problem? Important because many failures need architectural criteria, not a tool in hand. A red flag is that escalation depends on the technician calling “if they think it’s necessary”, without timeframes or a responsible person.
- Who escalates and with what maximum response time, measured in real time? Important because escalation without a clock is a promise, and promises are not billed. A red flag is a time expressed as “as soon as possible”, which could be at 3:00 AM or next Monday.
Evidence and traceability
Here you decide whether you will be able to demand something later. A provider that does not leave a written record of their work will hardly answer for that work.
- Do they deliver evidence of the work: before and after photos, video, or capture of the change? Important 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.
- Is there a log per intervention with arrival time, exit time, and technician name? Important because that log is the evidence you use for billing, auditing, and negotiating renewals. A red flag is a generic monthly report, without time or person’s name.
- Can they share physical access logs and work orders from last month? Important because it demonstrates that control exists and that it is applied with you as with any client. A red flag is “we do not deliver documentation”, which usually comes with the fact that they don’t have it either.
Security and credentials
A remote technician enters your room and handles keys, users, and credentials. It is an open door to your operation, and it is quoted as if it were the same as the rest of the service.
- Do they handle my remote access credentials and who keeps them when the contract ends? Important because a password that is not revoked is a security debt no one quoted. A red flag is that the technician keeps them “in case we need to return”, or that credentials live in a notebook.
- Do they have information security certifications and two-factor access control? Important 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 for amounts beforehand avoids the uncomfortable conversation during the incident.
- How is an emergency visit charged and is there a minimum of hours or monthly spend? Important because the minimum converts a one-hour call into a fixed charge, and the emergency surcharge must be in writing, 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
No one thinks about this until renewal month arrives, and by then there is no room for negotiation.
- What happens with my keys, credentials, equipment, and documentation when the contract ends? Important because 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 an hour meeting and all are answered in writing in the proposal. A serious provider answers them without feeling like you are interrogating them, because they are the same questions you ask anyone you entrust with the keys to your computer room. What they do not answer clearly… is already warning you what you will suffer the day a failure occurs.
Sources
Want to master this?
Noxtel Academy →
