Serval launches Catalyst to build automations from ticket history

# What Catalyst does

Serval launched Catalyst, an AI agent designed to automate the creation of automations. Instead of having humans inspect ticket logs, design workflows, and build automation scripts, Catalyst examines past tickets to find repetitive work and then builds and configures the automations that resolve those cases.

# How it fits in Serval's platform

Catalyst sits above Serval's AI-native enterprise service management platform. It operates as an agent layer that draws on ticket history and the platform's context to determine what to automate. One public report says Serval can enable Catalyst by default for customers, giving teams of agents the authority to choose and implement automations.

# Roving background agents and preventative work

A described capability for Catalyst is creating roving background agents that continuously monitor systems and identify issues before users file tickets. Those agents can both spot incidents and fix them, reducing ticket volume by addressing problems earlier in their lifecycle. In effect, Catalyst can act both as a finder of repetitive past work and as a proactive maintenance layer.

# What this changes operationally

Organizations that enable Catalyst by default delegate agentic decision-making about what to automate. That reduces friction for scale but requires governance: teams must define guardrails, validation steps, and rollback procedures so agent-built automations meet security and compliance needs.

# How to evaluate Catalyst for your environment

• Ticket quality and context: Agents rely on historical ticket data. If ticket descriptions, categorizations, or resolution notes are sparse, automated discovery will be limited.
• Governance model: Decide whether to allow agents to build and deploy automations automatically or require human review before activation.
• Integration surface: Check how Catalyst configures automations across existing tools and whether it supports your key systems.
• Monitoring and rollback: Ensure visibility into agent actions and clear rollback paths for any automation that misfires.

# Where Catalyst sits in the market

Agentic automation tools are appearing across enterprise software: vendors are introducing AI agents that plan, act, and repair. Serval's approach focuses on service-management workflows and leveraging ticket history to drive automation. Other vendors are launching agent studios, data assistants, and marketing agents that operate over specific business domains, indicating a broader trend toward agent-driven operational layers.

# Practical next steps for teams

Start by auditing ticket data quality and common repeatable resolutions. Define approval workflows and testing environments for agent-built automations. Pilot Catalyst on a narrow set of ticket types with clear success metrics: reduction in ticket volume, time-to-resolution improvement, or automation coverage. Maintain a short feedback loop to adjust agent permissions and guardrails.

Catalyst aims to make automating recurring operational work faster by pushing discovery and construction of automations into an agent layer. Teams that adopt it will trade some upfront manual work for governance and monitoring responsibilities to keep automated behavior predictable and safe.