Source: Automate 80% of IT Tickets in 24 Hours
Source: serval.com/updates/automate-80-of-it-tickets-in-24-hrs — Sep 30, 2025 (recapping JNUC 2025)
What It Covers
Recap of Serval’s Jamf Nation User Conference (JNUC) 2025 keynote. Centers on deployment velocity as Serval’s core demo claim: from Jamf Pro screenshot → working automation in under a minute.
Key Claims
- Demo: screenshot of Jamf Pro Mac status interface → Serval Builder reads the screenshot → calls Jamf Pro API in code → builds an automation that lets users self-serve “what’s wrong with my Mac?” via Slack. Demo completed in under 60 seconds. (extracted)
- API breadth: Serval lists ~16 Jamf Pro APIs that automations can call: get computer details, lock/unlock/wipe/restart, FileVault recovery key retrieval, MDM commands (DEP enrollment, name update, OS update, kernel-extension management, Bluetooth restriction, lost-mode entry), patch policy update, and more. (extracted)
- Composability claim: Builder agent reads docs, screenshots, or unfamiliar APIs and generates a working tool. “Today’s IT teams want self-service AI agents that can resolve simple help desk tickets and understand the unique configuration of every individual Mac.” (extracted)
- Mac-IT specificity: Serval’s narrative is unusually deep on Mac-IT (Jamf, Kandji elsewhere) — historically a hard surface for legacy ITSM, especially for fleet patching, FileVault recovery, and MDM commands. ^[inferred]
Notable Phrasing
- “Automate 80% of IT tickets in 24 hrs”
- “From screenshot to automation in under a minute”
- “Self-service Mac-IT” as a wedge
Strategic Implications
- This is Serval’s strongest public proof that “vibe coding” is more than marketing — building on top of an unfamiliar API from a screenshot is a real capability differentiator.
- Mac-IT depth is a smart wedge: Mac fleets are growing, Jamf is the dominant MDM, and ServiceNow / Jira Service Mgmt have weak Mac stories. Serval can be the “AI for Mac-first IT” before becoming the “AI ITSM for everyone.”
- The 80% / 24-hour framing is aggressive but anchored to a specific deployment claim, not generic marketing. It functions as a proof-of-concept commitment Serval makes to prospects.
Limitations
- Demo is single-vendor (Jamf) and single-flow (“what’s wrong with my Mac”). Real ITSM rollouts cover hundreds of flows.
- 80% / 24-hr claim does not specify what counts as a “ticket” or which subset of customers achieved this.
- Screenshot-to-code is impressive but it’s not clear how the agent handles malformed APIs, rate limits, or auth edge cases in production.