Why Legacy ITSM Creates Tickets Without Resolving Them
Legacy ITSM platforms are built around logging work, not finishing it.
Legacy ITSM platforms were designed to record problems, not resolve them. The work gets logged. It rarely gets done.
The system prioritizes intake over resolution.
Before any fixing begins, tickets must be categorized, prioritized, and assigned.
Each handoff adds waiting time and erases context.
Several structural problems drive this:
- Tickets enter general queues even when specialists are needed immediately
- States like “Open” and “In Progress” measure movement, not outcomes
- Repetitive requests such as password resets consume capacity that automation could eliminate
- Weak routing sends tickets to the wrong team first
The result is a process optimized for tracking problems rather than eliminating them. Walkup desks often resolve issues instantly on the spot, yet tickets go unlogged because the system offers no fast path to simultaneous creation and closure.
Cost per ticket can range from $22 to over $100 depending on complexity and handling time, meaning every unresolved or misrouted interaction carries a measurable financial consequence beyond the time lost. ITSM aims to shift focus from components to delivering complete technology services aligned with business goals.
How Serval Automates ITSM Without Replacing Your System of Record
The most disruptive IT transformations are not always the ones that tear everything down.
Serval operates as an automation layer on top of existing ITSM platforms rather than replacing them.
It runs bidirectional sync with ServiceNow, keeping incidents, problems, changes, and HR cases aligned across both systems.
Teams can automate work immediately without migrating their system of record.
Serval polls ServiceNow for updates, writes back through REST APIs, and keeps supporting data like groups, roles, and departments current.
Audit trails, approvals, and reporting stay intact inside the incumbent platform while Serval handles resolution on the front end. When the organization is ready, teams can cut over the system of record to Serval without disrupting the automations already running.
ServiceNow knowledge articles sync into Serval and are made available as read-only mirrored knowledge bases, preserving folder hierarchy and formatting so AI agents can draw on the same content without requiring manual duplication.
Robust integrations also require careful attention to data security and compliance to protect sensitive information across systems.
The Real Results: 50–80% of IT Tickets Resolved Without Human Touch
Automation rates in enterprise IT have moved well past the proof-of-concept stage. Mature ITSM programs now resolve 50–80% of tickets without analyst involvement. Organizations that align automation with business objectives report better outcomes and measurable gains in service quality and efficiency alignment metrics.
Some large deployments exceed 80% when request types are standardized.
When request types are standardized, large deployments push automation rates past the 80% threshold.
The highest rates come from completed work, not deflection or faster routing.
Specific ticket categories drive the strongest numbers:
- Password resets and account access: 75–90% automation
- Software license requests: 55–70% automation
- Network access and VPN: 40–60% automation
Resolution time also drops sharply.
Some teams report median resolution falling from 71 hours to 4.4 hours. Agentic ITSM platforms can trigger workflows before a ticket is ever filed, meaning work starts earlier and resolution clocks begin ahead of the first user request.
Agents in AI-supported environments handle 22% more tickets per day due to AI pre-processing and classification, freeing senior staff to focus on complex escalations rather than routine intake.
How Serval Keeps Automated ITSM Actions Auditable and Compliant
Resolving 50–80% of tickets without human involvement is only sustainable if every automated action can be explained, reviewed, and defended. Serval logs every workflow step, including inputs, outputs, timestamps, and approvers. This level of traceability helps meet compliance requirements across integrated systems.
Compliance teams get structured exports ready for auditors without assembling screenshots.
- Every API call and role change is logged with full context
- Approval chains show who authorized what and when
- Logs export as CSV files filtered by user, date, or action type
- Audit events stream to external tools like Splunk or Datadog
SOC 2 Type II certification and HIPAA-aligned controls support regulated-industry deployments. Offboarding workflows are triggered by the HRIS status change rather than an IT ticket opened after HR has already processed the departure. The Insights Agent analyzes ticket patterns across the help desk to identify work still handled manually and suggest which workflows to build next.
Which Enterprises Are Already Using Serval for ITSM Automation
Who is actually using Serval in production? Several enterprises are already running the platform at scale.
Several enterprises are already running Serval in production — and the list of names might surprise you.
Named customers include:
- General Motors and Fox Corporation — the clearest mainstream enterprise names tied to Serval
- Perplexity, Together AI, Verkada, Cribl, and Mercor — confirmed across Serval and third-party coverage
Together AI publicly exceeded 50% ticket automation and 95% just-in-time access automation.
These organizations use Serval for access workflows, onboarding, offboarding, and help desk resolution.
Some have replaced their previous ITSM tools entirely.
Serval now serves as their system of record.
Adoption has also expanded beyond IT into HR, Finance, and Security. Automation has even displaced dedicated software vendors in functions like Legal and Engineering as workflows spread across the organization.
Perplexity reports saving each admin 1–2 hours per day while scaling headcount three times without linear IT growth.
Many of these use cases demonstrate how Serval supports broader IT service management goals such as aligning IT operations with business objectives.
