Seven questions that expose a weak smart hands SLA

Almost every field engineering contract advertises a four-hour response. Very few define what is being responded to. In a weak SLA, the clock stops when someone acknowledges the ticket — which a portal can do automatically. In a strong one, it stops when an accredited engineer is physically on site with the parts required to fix the fault.

The gap between those two definitions is where most of the disappointment in this industry lives. Ask for the definition in writing, then ask what percentage of tickets met it last quarter in the specific countries you care about, not globally.

Very few providers directly employ engineers in ninety countries; almost all of them use partner networks. That is not a problem in itself — density beats ownership when travel time is the binding constraint. The problem is when a provider will not tell you which model applies where.

A supplier who says 'our engineers' about every location on the map is either much larger than their revenue suggests, or is not describing the arrangement accurately. Either answer is worth knowing before you sign.

A visit without the right part is a wasted visit that still consumes your window. Strong contracts define parts logistics explicitly: who holds the spares, where they are staged, and what the replenishment cycle looks like after a swap-out.

The related question is scoping. An engineer dispatched against a one-line ticket will diagnose rather than fix. Ask how work instructions are produced and who is accountable when the scope was wrong.

The most reliable indicator of a serious field operation is what lands in your inbox afterwards. A photographic site report within 24 hours, referencing the asset serial and the work instruction, is cheap for a well-run provider and nearly impossible for a poorly-run one to fake at volume.

If a supplier cannot show you a sample report from a real engagement during the sales process, assume the reporting does not exist.

Service credits that must be claimed are rarely claimed, which is usually the point. Automatic application against the following invoice removes the administrative friction that suppliers quietly rely on.

Finally, ask what happens when you leave. Documentation, asset registers and configuration data are yours; a provider who treats exit assistance as a chargeable extra is telling you something about how they expect the relationship to end.