Skip to content
Hybot
Request a demo

Contact

Support

This route is for venues already running Hybot. The most useful first message names the site, the robot and what happened, because the platform already reports project health and heartbeat centrally and that context turns a vague report into something diagnosable immediately.

Contact support

For venues already running Hybot.

Optional, but it usually decides who should answer you.

A sentence or two of context is enough to reach the right person.

Frequently asked questions

What information should I include?

Which project and which robot, roughly when it happened, and what the fleet view was showing at the time. Screens help. So does whether the problem is one robot behaving oddly or an entire site that has gone quiet.

Can you see the problem from your side?

Often, partly. Projects report health by heartbeat and internet quality is charted centrally, so a site that has dropped off is usually visible. What happened inside the building, and whether anything physical changed, is something only you can tell us.

Is there a published response time?

No service-level commitment has been agreed, so publishing one here would be inventing it. Response arrangements are part of what is agreed with each deployment rather than a universal promise on a marketing page.

Another kind of enquiry?