Read the film transcript
If you lead engineering at a robotics company, you're trying to grow the fleet, improve reliability, and keep your engineers focused on building the product. But as more robots enter the field, more support tickets land on those same engineers' desks.
We work with many robotics teams, and we kept seeing the same problem. A ticket comes in, support searches for answers, but the context they need often lives with an engineer as tribal knowledge. So that engineer stops building the product to reconstruct what happened, while support and the customer wait.
As the fleet grows, the tickets pile up. More engineers get pulled into support, and work on the next generation keeps getting interrupted. So how do you grow the fleet without pulling more engineers off the roadmap?
Alloy gives support access to your robot data and what your team has learned from past issues, so they can resolve more tickets without escalating to engineering. And when a case does need engineering, Alloy gathers the evidence and presents its findings. Your engineer can review the case instead of starting the investigation from scratch. Less detective work, more time for engineering judgment, and for building the product.
At SwarmFarm, first-line support went from resolving approximately 30% of tickets to 80%, while time per ticket fell from one or two hours to approximately 10 minutes. At Andromeda, engineering root cause investigations went from weeks to hours.
Here's how that works. When a ticket lands in your support channel, Alloy searches the connected robot data, company context, and previous investigations. It brings its findings and supporting evidence back into the thread. Support can ask follow-up questions, understand the recommended next step, and work with the customer to resolve the issue.
With that context, support can resolve most cases without escalating to an engineer. When the case needs engineering judgment, the engineer joins the same investigation with the context already there.
Getting a robot working again and finding the underlying cause are different jobs. For a deeper investigation, the team can open the case in Alloy's platform to inspect logs, analyze telemetry, and run scripts.
As engineers and support teams investigate with Alloy, they add context, ask questions, and confirm what worked. Alloy retains what they learn, so each investigation builds on the last and the team's shared knowledge naturally compounds.
Ask Alloy a question in Slack. It's like asking your whole team across every time zone without interrupting anyone. Behind the answer is what your engineers and support teams have already learned together. Alloy draws on that shared knowledge, then brings the answer straight back into the conversation.
As more conversations and investigations add to that knowledge, the next person starts with more answers already available. They can get further without repeating work, then contribute what they discover for whoever comes next. The more your team uses Alloy, the more useful it becomes to everyone. With that history in one place, your team can identify recurring issues across the fleet.
Alloy connects to your existing tools and data through a suite of third-party integrations. For more custom needs, our forward-deployed engineers build integrations and workflows tailored to your team.
Resolve more in support. When engineering is needed, engineers can investigate more efficiently. Keep your team focused on building better robots. To see how Alloy could fit your team, talk to us.