Remote Fault Fixes: Questions to Ask Before Signing

What can a remote fix actually resolve on a cleaning robot?

Remote fault resolution covers the problems a technician can reach without touching the machine. That usually means reading logs, pushing a firmware patch, correcting a configuration, rebooting a module or changing a schedule. It does not replace a hand on a brush deck, a battery pack or a bumper sensor.

Vendors now lean on this capability heavily. Gausium says its Remote Maintenance Center provides 24/7 cloud diagnostics, with around 70 percent of faults resolved remotely, according to its October 2026 blog post. That is a vendor-reported figure, and the post does not define what counts as a fault or as resolved. Treat it as a reason to ask questions, not as a rate to write into a contract.

The useful question before you sign is narrower: which faults in your fleet will be fixed without a visit, how fast, and how you will know. The sections below work through that.

Where does the 70 percent figure come from, and what does it leave out?

Gausium's figure appears in two separate posts: an October 2026 post on easy to deploy robots and an August 2026 post on performance reporting, which repeats the wording under its cloud platform section. Both are vendor publications. Neither gives a denominator, a time window or a sample of sites.

The missing context matters. A fault that a software patch clears in a few minutes and a failed battery that takes a week to ship could both count as one fault. Ask the vendor for the number of faults in a stated period, how many closed remotely, and how many closed onsite, broken out by category.

Which faults still need a technician on site?

Anything physical. Brushes, squeegees, drive wheels, batteries, lidar windows and bumper sensors all need a person with parts. A remote tool can show that a drive motor is drawing too much current, but it cannot change the motor.

Connectivity is the other limit. Gausium's August 2026 offline post says remote scheduling, start and stop, cloud diagnostics and remote troubleshooting all depend on a connection, and that faults which could have been resolved remotely wait for connectivity to return or require a site visit. The same post says wireless coverage is often incomplete in basement levels, dense racking and outdoor yards. If your building has those zones, a remote-fix rate measured on connected robots will overstate what your floor will see.

How should response times be written into the agreement?

Response time and resolution time are different promises, and many agreements only price the first. Robolist.ai's third-party SLA guide describes response as an acknowledgement, often one to four hours for critical issues, and resolution as often 24 to 72 hours for critical issues. It also notes that response times mean little without geographic coverage.

Tier structures make the gap visible. RobotLAB's services page lists Basic within two business days, Silver within one business day, Gold within 24 hours, and Platinum within four hours with 24/7 support, with same-day or next-day onsite for Platinum where available. These are vendor-stated targets. The same page bills onsite labor and travel by the hour plus mileage on Basic and Silver, which belongs in any cost comparison.

Sproutmation's 2026 maintenance guide makes a related point: high-use facilities care more about response time than about the contract price. A quick acknowledgement with no fix window is a weak promise for a night crew that needs the scrubber running before the first shift arrives.

What should trigger a dispatch?

Ask for dispatch triggers in writing. A sensible one is that a remote session cannot clear the fault within an agreed window, after which a technician is scheduled. Robo Reliance, a third-party field service firm that says it runs a nationwide network of independent technicians for cleaning robots regardless of manufacturer, describes the same pattern. It says it coordinates technician dispatch when remote resolution is not possible.

Define the triggers for the harder cases too. What happens when the robot goes offline mid shift, when the vendor's cloud is down, or when the same sensor fault repeats three times in a week? Agreements that answer only the easy case leave the night supervisor guessing.

As a full-service integrator, Service Robot Co. handles these questions in one place. We are OEM neutral, so we select robots across manufacturers, and we service every unit through our nationwide US engineer network. Customers lease robots from us on a lease term of three years, with one fixed payment quoted after a site assessment, which gives us a chance to agree dispatch rules before a robot reaches the floor.

What questions should you put to every vendor?

These questions take a few minutes to ask and save a long argument later. Get the answers in writing, and compare vendors on the same terms.

• How do you define a fault, and does your count combine repeated alarms that share one cause?
• Over what period, and across how many sites, was the remote-resolution share measured?
• What share of faults in each category, such as software, battery, drive and sensor, closed without a visit?
• What is the response time and the resolution time for a critical fault, and does each clock start at the ticket or when the robot stopped?
• Which failures does the robot log and queue while offline, and do those records upload automatically when the connection returns?
• Which cleaning results does cloud data verify, and which still require onsite inspection scoring?

How should over the air updates be governed?

Gausium states that new features, performance optimization and bug fixes are pushed over the air without additional charge, and its October 2026 post says software updates are not billed as service visits. These are vendor policies. Ask whether the same terms apply to your model and region, and whether they appear in the contract itself.

Free and fast does not mean risk free. Robolist.ai recommends advance notice for firmware updates that affect navigation, citing seven days as a common ask. Outside robotics, a remote telematics update disrupted vehicle communication in October 2025 and led to a recall of 24,238 vehicles with model years 2023 through 2025, according to a 2025 automotive newsletter. A remote push needs a rollback plan and a test window, whatever the machine.