Across the lifecycle · Support
Answer the ticket without the site visit
Insaion gives support teams the robot's telemetry, incident history and the recording from the moment the customer complained. Tickets start with evidence.
Built for: Support, field-service and customer success teams
Where support time goes
“It did something weird around lunchtime.”
Tickets without evidence
Reports are vague and late. Day one goes on finding out what happened.
“We need someone on site to pull the logs.”
Site visits just to collect data
Flights and truck rolls to copy files off a robot.
“Engineering can't reproduce it.”
Escalations that bounce back
No recording, no context. The ticket bounces for days.
The engineer's view, for whoever has the ticket
Telemetry, incidents and recordings in one place.
The robot's history in one place
Dashboards and incidents on one timeline, at the moment the customer noticed.
Recordings without a visit
Upload the minutes around the event from the robot's buffer. Replay in the browser.
Copilot does the first pass
A summary, the related signals and a likely cause before anyone digs in.
Starter plan and above
Change config from the browser
Edit the template. The agent picks up the change by itself.
Support bundle in one command
Redacted config, system status, recent logs and the ROS 2 graph in one archive.
Roles for the whole team
Admin, Member and Viewer. Support, engineering and stakeholders in one workspace.
Team invites on Starter, per-user roles on Growth
A ticket, start to finish
- 1
The customer reports an issue
Open the robot. Jump to the time they mentioned.
- 2
Check telemetry and incidents
Did an alarm fire? What were CPU, battery and the topics doing? Many tickets end here.
- 3
Pull the recording
Upload the window from the robot's buffer. No SSH, no site visit.
- 4
Escalate with evidence
Device, time range, recording and Copilot's summary, in the same workspace.
What Insaion does not do yet
- There's no integration with ticketing tools like Zendesk or Jira yet.
- Support bundles are created from the command line on the robot. You can't request one from the web app yet.
- Insaion isn't a remote-control or teleoperation tool.
Frequently asked questions
How do you troubleshoot a robot remotely?
Use an agent that streams telemetry and records data locally on the robot. With Insaion, support teams open the robot's dashboards at the reported time, check its incident history and upload the MCAP recording from its buffer, without SSH access or a site visit.
Can support engineers use Insaion without knowing ROS?
Yes. Dashboards, incident history and Copilot's incident summaries make sense without any ROS knowledge. The raw ROS 2 topics and MCAP recordings are still there when a ticket goes to engineering.
Does Insaion need inbound network access to the robot?
No. In normal operation the agent only makes outbound connections over port 443, so robots behind customer firewalls can be monitored without a VPN or port forwarding.
How does Insaion reduce site visits?
The rolling buffer on the robot keeps full-fidelity data for a configurable period, and anyone on the team can upload a time window remotely. Collecting data, the most common reason for a visit, no longer needs someone on site.
Close robot tickets faster
Free plan, unlimited devices, no credit card.