Notifications
Clear all
Topic starter
08/07/2026 7:08 pm
TL;DR: Matrix42 describes service management evolving from human-guided assistants to conditional and highly autonomous AI agents, with Gartner-cited gains including up to 40% lower agent churn, 62% fewer inbound calls in three months, and 500 hours a month saved in ticket preparation. The governance question is whether identity, access, and accountability models can keep pace as service workflows become more agentic.
NHIMG editorial — based on content published by Efecte: Gestione intelligente dei servizi, da reattiva a proattiva
By the numbers:
- The 40% of organizations using AI assistants reported lower agent churn, according to Gartner.
- The 62% reduction in inbound support calls was achieved in just three months, according to the article's example.
Questions worth separating out
Q: How should teams govern AI agents that can act inside service workflows?
A: Treat them as non-human identities with bounded authority, not as simple workflow helpers.
Q: Why do AI service agents change IAM and PAM requirements?
A: Because they can execute actions, not just recommend them.
Q: What do organisations get wrong about proactive AI in service management?
A: They often measure speed and deflection while ignoring who authorised the action and whether it can be undone.
Practitioner guidance
- Classify service AI by actor type before granting access Separate assistants from agents and proactive systems in the service catalogue, then assign governance based on whether the system only assists, conditionally acts, or independently triggers remediation.
- Treat access-provisioning agents as non-human identities Inventory every credential, API token, and tool permission used by service agents, then attach owner, purpose, and expiry to each one.
- Define pre-approved action boundaries for proactive remediation Limit what an agent can change without escalation, especially where the action affects access, production services, or user data.
What's in the full article
Efecte's full article covers the operational detail this post intentionally leaves for the source:
- The three-stage service AI model with product-level examples of assistants, agents, and proactive AI.
- Matrix42's deployment choices for on-premise, private cloud, and public cloud AI processing.
- The customer examples behind the cited efficiency gains and service desk outcomes.
- The white paper's practical guidance on moving from reactive service management to proactive service delivery.
👉 Read Efecte's analysis of AI-driven service management and proactive operations →
AI service management and autonomy gaps in IAM teams?
Explore further
08/07/2026 7:32 pm
Conditional autonomy is the point where service management stops being an ITSM efficiency story and becomes an identity governance problem. Assistants can remain a human productivity layer, but agents that provision access or resolve incidents start operating as governed machine identities. The article correctly separates these stages, because the governance burden changes when a system can act rather than merely assist. Practitioners should map service AI to actor type before they map it to process automation.
A few things that frame the scale:
- The 40% of organizations using AI assistants reported lower agent churn, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap.
A question worth separating out:
Q: How do service teams decide when AI should remain an assistant rather than an agent?
A: Use the decision test, not the vendor label. If the system only retrieves knowledge or drafts responses, keep it in the assistant category. If it can independently choose a tool, execute a change, or trigger remediation, it crosses into governed agent behaviour and needs identity controls to match.
👉 Read our full editorial: AI service management is shifting from assistants to autonomy
