Skip to content
Home · Guides

Robot vacuum problems: write a useful service request

08.10.2026 · Redakcja RoboMorrow
ECOVACS DEEBOT X11 OmniCyclone official robot and bagless dock product image

“The robot is broken” gives a service team little to investigate. A more useful description is: “After cleaning the kitchen, the robot reaches the dock, tries to dock twice and stops without charging. This happened in four of the last five cycles.”

You do not need to diagnose the failed component. Describe the symptom, conditions and checks already completed. The workflow and copyable template below help turn an unclear complaint into a reproducible report.

First decide whether further operation is safe

For a burning smell, visible battery damage, liquid affecting electrical parts or a damaged cable, stop using the equipment and follow the manual and service instructions. Do not recreate the event for a video.

For an ordinary navigation problem, record the event before resetting the map. A factory reset may remove useful information and is not the correct first step for every fault. If support requests logs, follow its documented procedure.

1. Describe the symptom in three parts

Explain what you started, what you expected and what happened. Name the stage of the cycle. “It does not mop” could mean no water delivery, no mop movement, an excluded area or a poor cleaning result.

Use observations: “the tank level does not change”, “the app displays this code”, or “the robot stops before the threshold”. Do not present “the pump has failed” or “the LiDAR is broken” as an established diagnosis without confirmation.

2. Identify the device and software

Detail Why it helps
Full robot and dock names Similar names can describe different equipment
Serial number Identifies the unit; share through a private support channel
App and firmware versions Establishes the configuration
First occurrence Helps relate the symptom to a change
Exact error code or message Replaces “something flashes”
Purchase date and seller Helps route the request

If you cannot locate a version number, say so and attach the relevant screen. Do not guess. Send purchase documents through the channel specified by the seller or service team.

3. Record frequency and recent changes

Use already observed cycles, such as four unsuccessful returns out of five. Do not provoke extra failures. State whether the issue affects one room, every route, a particular rug or operation following an update.

List the latest relevant change: a moved dock, new router, replacement bag, new map or changed mopping mode. Timing alone does not prove causation, but it helps narrow the investigation. Say whether the same configuration previously worked.

4. Choose useful evidence

Symptom Useful attachment
Failed return or docking Short approach video and dock-location photograph
Threshold problem Side profile with a measure and travel direction
Missed area Annotated map and zone settings
Remaining dirt Before-and-after photos in similar light
Dock operation fails Message and condition of accessible tanks or components

Show the beginning and end of the event. A caption such as “00:18 — second failed docking attempt” makes a short clip easier to interpret than several unexplained minutes.

Remove documents and unnecessary personal details from the background. Do not publish the home map, serial number or account details in a public comment. Share only what the legitimate support team needs.

5. List approved checks and outcomes

Perform only user-maintenance steps permitted in the manual, such as checking the dock location or cleaning an accessible component. Record each outcome: “cleaned according to the manual; no change” is more useful than “already cleaned”.

Do not dismantle batteries or electrical modules, cover sensors or bypass safeguards. Avoid changing every setting at once. Otherwise, neither you nor support can tell which step changed the result.

Copyable service-request template

Subject: [model] — [short symptom] — support request

Hello, I would appreciate help with my [full model] and [dock variant].

I start [task and setting]. The expected result is [brief description]. Instead, the device [observed symptom]. The app displays [exact message / no message].

The issue started on [date] and occurred in [number] of [number] observed cycles, under these conditions: [room, floor and route]. The latest relevant change was [description / no known change].

App version: […]. Firmware: […]. Checks performed according to the manual: [action and result]. Attached: [evidence list]. I am providing purchase information and the serial number through the requested form or attachment.

Please advise the next diagnostic step and any additional information needed. If the equipment needs to be sent in, please confirm which components to include and how to prepare the shipment.

Before sending anything

Confirm whether support needs the robot, dock, cables or other accessories. Ask about tank preparation, packaging and the shipping label. Do not assume another model’s transport instructions apply.

Keep the case number, an inventory of included components and photographs of their condition. After return, repeat the scenario that previously failed and record the result.

This guide concerns symptom documentation. It does not specify legal claim routes, return rights or response deadlines. Those depend on the applicable purchase and jurisdiction.

Related: the home test and dock-space guide. The template is an editorial tool; technical checks must come from your own device’s documentation.

Search robots
RoboMorrow Sverige · Svenska →