Latest Articles

Your Employees Don't Want to Fill Out Forms — They Want Results. AI Agents Are the Answer. The End of the Service Request Form as We Know It Employees don't want to navigate complex portals, decipher technical jargon, or wait days for approval. They want outcomes: access, equipment, answers. And increasingly, they're getting them instantly from AI. Service request management is at a tipping point. Research shows that 87% of organizations are already deploying AI in ITSM or expect to do so within 24 months, and 97% say AI capabilities would influence their next platform decision . The question is no longer whether to deploy AI for service requests, but how to do it effectively and at scale. The Shift from Chatbots to Autonomous Agents Early AI implementations focused on simple chatbots that redirected users to knowledge articles. The new generation of AI agents is fundamentally different. They don't just suggest answers; they take action. AI agents bring context, decisioning, and autonomy to service request management across internal and external journeys . They intelligently orchestrate, prioritize, communicate, and resolve. From triaging requests to guiding resolution paths, these agents transform service delivery into a seamless experience for employees, customers, vendors, and partners alike. ServiceNow describes this evolution as the shift from "AI-assisted" to "AI-led" service delivery. In the AI-led model, agents coordinate workflows across platforms autonomously while maintaining human oversight — a critical distinction from simple chatbots that merely redirect. Why This Matters for Your Organization The shift to AI-powered service requests directly impacts key business metrics: Metric Impact Employee Productivity Employees spend less time waiting for access or approvals Service Desk Efficiency Agents spend less time on repetitive requests Cost Reduction Automation reduces the cost per request Employee Experience Instant resolution creates a consumer-grade support experience Scalability AI handles volume increases without proportional team growth How AI Agents Transform Service Request Management According to industry research, Agentic AI introduces three defining capabilities that fundamentally change service delivery : Contextual awareness to interpret user intent Dynamic reasoning to plan actions and resolve dependencies Multi-agent coordination to execute complex workflows across systems When John, an employee, requests a business trip, an AI agent detects the intent from a Teams conversation, extracts details like destination and duration, and automatically creates a travel request. His manager receives an approval prompt within the same conversation. Upon approval, multiple AI agents spring into action — one validates eligibility against HR data, another checks budget limits, a third verifies device encryption status for remote access . This is the fundamental difference between automation and Agentic AI: Automation Frameworks Agentic AI-Driven Service Delivery Process-driven: executes preconfigured workflows based on static rules Intent-driven: interprets user intent and autonomously fulfills requests Siloed data and fragmented systems Connected intelligence across IT, HR, and Finance One-size-fits-all delivery Personalized service that adapts to each user Reactive: workflows trigger only after users submit a request Proactive: agents anticipate needs and resolve issues before tickets are created Real-World Impact Leading organizations are already achieving dramatic results with AI-powered service request management: BDO Canada achieved an 84% auto-resolution rate across service requests  Organizations report 50% fewer call volumes to service desks and 80%+ auto-resolution rates Time-to-value with first AI agents can be as little as eight weeks The Governance Imperative However, the promise of AI agents comes with a critical caveat: governance. As AI agents gain the ability to take autonomous action, organizations must ensure they operate within defined boundaries. Three critical success factors stand out: the readiness to adopt agentic AI, the quality of knowledge sources to avoid AI hallucinations, and understanding the governance and regulatory landscape . Conclusion: The Autonomous Service Desk Is Here The AI service request agent is not a future concept. It's a proven solution already delivering results at scale. Organizations that embrace Agentic AI will move beyond incremental efficiency gains to build a service ecosystem that is anticipatory, resilient, and personalized at scale . Action Items for Your Organization Assess your current service request volume and identify patterns Evaluate AI agent platforms for service request management Start with a pilot focused on a high-volume, low-complexity request type Establish governance frameworks for AI agent autonomy Measure auto-resolution rates, deflection, and service desk capacity impact  

Employees Don't Want to Know Where to Go — They Want One Place for Everything The Fragmentation Problem Employees don't want to navigate multiple tools, remember different URLs, or know which department handles which request. They want a single place to get help. This "single pane of glass" philosophy is driving the evolution of self-service portals. Microsoft's Employee Self-Service Agent was built on the premise that employees should have one place for all support needs — combining IT, HR, and facilities . Why One Portal Matters The Employee Experience Impact As one industry expert noted: "The line between customer support and internal service management has continued to blur. All end users expect consumer-grade experiences all the time. Every service interaction, whether HR, IT, finance, customer support, legal, or facilities contributes to a perception of your organisation's competence" . The Cost of Fragmentation Problem Impact Multiple portals and URLs Employees don't know where to go Department-specific interfaces Inconsistent experience across functions Separate login credentials Friction at every interaction No unified view of requests Employees can't track progress IBM's AskHR: A Case Study in Unified Service IBM's AskHR virtual agent demonstrates the power of a unified approach. The system: Handles over 2.1 million employee conversations annually Achieves a 94% containment rate of common questions Has led to a 75% reduction in support tickets since 2016 Contributed to a 40% reduction in HR operational costs over four years  AskHR operates on a two-tier support model: AI handles routine inquiries while human advisors manage more complex needs. Behind the scenes, complex HR processes are streamlined through deep integration with enterprise systems such as Workday, SAP, and Concur . Key Design Principles for Unified Portals 1. Single Point of Entry All service requests — regardless of department — start in one place. This reduces confusion and ensures all requests are tracked consistently . 2. Consistent Experience The interface should feel the same whether you're requesting IT support, HR approval, or facilities service. Consistency builds confidence and reduces learning time. 3. Departmental Logic Behind the Scenes Users don't need to know which department handles which request. Automation should route the request to the right team based on the request type . 4. Cross-Department Coordination ESM systems thrive when cases can move smoothly from one team to another. Employees use a single, unified portal to request any internal service and track progress in one place . The Benefits of Unified Service Delivery Benefit Impact Higher adoption One place to go for everything Better tracking All requests in one system Consistent experience Same interface across departments Faster resolution No time wasted finding the right place Better data Complete view of all service activity Conclusion The "single pane of glass" isn't just about convenience — it's about delivering a consistent, frictionless employee experience. Organizations that unify service delivery across departments will see higher satisfaction, faster resolution, and better operational efficiency. Action Items for Your Organization Map all service portals and entry points — where is the fragmentation? Identify the most common request types across departments Design a unified experience — one portal, one login, one interface Build automation to route requests to the right team Measure adoption and satisfaction before and after unification  

No More Manual Data Entry — How AI Turns Chat Transcripts into Complete Service Requests The Unstructured Input Problem Employees don't think in forms. They think in natural language: "I need a new laptop," "Can I get access to the marketing drive?" or "My computer is slow." This natural language must be translated into structured data—a service request with the correct category, priority, assignment group, and required fields. Traditionally, this translation required service desk agents to read and interpret requests, manually extract key details, select the correct request type, populate fields, and route to the appropriate team. Each step consumed agent time, introduced potential for error, and delayed resolution. How AI Transforms Request Creation AI-powered service request creation solves this problem by automatically generating complete, structured service requests from minimal, unstructured input. The system intelligently analyzes the unstructured text to : Extract relevant details: Identifies key entities like user identity, requested action, urgency, and context Determine the request type: Matches the intent to the appropriate service catalog item Populate required fields: Automatically fills in categories, priority, assignment group, and other metadata Generate a complete request: Creates a well-structured ticket ready for assignment The Natural Language Detection Advantage Modern AI agents can detect intent from simple conversations. For example, when an employee pings their manager requesting approval for a conference, an AI agent can : Detect the intent from the conversation Extract details such as destination, duration, and purpose Automatically create a service request Route the approval request to the manager within the same conversation context The Benefits Benefit Impact Reduced manual effort Agents spend less time on data entry and request processing Minimized misclassification AI applies consistent categorization criteria Faster triage Complete requests can be assigned immediately Higher-quality data Consistent, accurate request data for reporting Improved agent productivity Agents focus on resolution, not administrative work Conclusion: The End of Manual Data Entry AI-powered service request creation is eliminating one of the most persistent inefficiencies in service management. By automatically converting unstructured inputs into complete, structured requests, organizations can reduce manual effort, minimize errors, and speed resolution. Action Items for Your Organization Assess your current request creation process—what's manual? Identify high-volume request types that could be automated Evaluate AI capabilities for request creation in your ITSM platform Pilot with a single request type, then expand Measure the reduction in manual processing time  

Starting from Zero — A Practical Guide to Building a VRM Program That Scales The VRM Journey Building a VRM program from scratch can feel overwhelming. But a structured approach makes it manageable. Phase 1: Foundation (Months 1-3) Assess Current State What vendors do you have? What data do they access? What is your regulatory environment? What is your current risk posture? Define VRM Policy Document formal VRM policy Define risk tolerance levels Outline governance structure  Establish Vendor Inventory Create a comprehensive list of all vendors Identify critical vendors Document vendor relationships Define Risk Appetite What risks are you willing to accept? What risks must be avoided? What is your risk tolerance? Phase 2: Implementation (Months 3-9) Implement Vendor Tiering Classify vendors based on risk levels  Critical, moderate, and low risk  Determine assessment frequency by tier Develop Assessment Process Create vendor risk assessment questionnaires  Define assessment criteria Establish evidence requirements Conduct Initial Assessments Assess critical vendors first Document findings Develop remediation plans Establish Contractual Controls Embed risk clauses in vendor contracts  Include breach remediation and warranty obligations Define data access and transparency requirements Phase 3: Maturity (Months 9-18) Implement Continuous Monitoring Move from periodic to continuous assessments Implement automated monitoring tools Set up real-time alerts Automate VRM Implement VRM software Automate evidence collection Automate risk assessments  Integrate with Other Functions Collaborate with procurement, IT security, and compliance  Establish cross-functional governance Adopt a hub and spoke model  Phase 4: Optimization (Ongoing) Continuous Improvement Review and update VRM processes Identify improvement opportunities Implement improvements Proactive Risk Management Horizon scanning for emerging risks Predictive analytics Vendor risk quantification  The Risk-Based Approach Adopting a risk-based approach is paramount to drive efficiency across the TPRM lifecycle . This involves focusing efforts on third parties that pose the highest risk to the firm . Governance Structure Hub and Spoke Model: Hub: Central leadership team responsible for setting policies, standards, reporting and risk appetite  Spokes: Subject matter experts from relevant risk domains (privacy, cyber, BC, DR, etc.)  Lines of Defense: First line: Business owners Second line: Risk and compliance Third line: Internal audit Conclusion Building a VRM program is a journey, not a destination. By following a phased approach and leveraging technology, organizations can build a scalable, effective VRM program . Action Items for Your Organization Define VRM policy and risk appetite Establish vendor inventory Implement vendor tiering Develop assessment processes Implement continuous monitoring Automate where possible    

Stop Guessing Which Team Gets the Request — AI Predicts Workgroup, Category, and Priority Automatically The Triage Bottleneck Even when a service request is created, the work isn't done. It still needs to be categorized, prioritized, and assigned to the right team. This triage step is often manual, inconsistent, and a major source of delays. Service desk agents routinely spend significant time on triage decisions: What category? What type of request is this? What priority? How urgent is it? Which team? Who should handle it? These decisions are often based on experience and judgment, leading to inconsistency. Two agents might categorize the same request differently; urgency might be over- or under-estimated; requests might be routed to the wrong team, causing delays. How Predictive Auto-Fill Works Service Desk Intelligence leverages AI predictions to automate and enhance the efficiency of service desk operations. It auto-fills, assigns, and predicts key service request fields — including workgroup, category, classification, impact, and urgency — to streamline the analyst workflow . The system works by: Analyzing historical records: Scanning past requests for similar patterns Learning from prior responses: Understanding how human agents categorized and prioritized similar requests Predicting the best fit: Evaluating analysts based on resolution time, probability of reopening, current workload, and SLA violation history Suggesting or applying values: Providing recommendations that agents can accept or override Implementation Approaches Approach Description Best For Apply by Default AI automatically populates values without agent review High-confidence predictions Show as Recommendation AI suggests values; agents can accept or override Building trust and accuracy Show Remarks AI provides reasoning alongside suggestions Transparency and learning Key Advantages Reduced Response Time Triage decisions happen instantly, not after agent review. Lower Error Rate for Categorization AI applies the same criteria consistently, reducing misclassification. Fewer Interactions Needed for Resolution Correct categorization and routing from the start means fewer handoffs. Improved CSAT Faster, more accurate triage means faster resolution and better user experience. The Rovo Service Triage Agent Atlassian has introduced the Service Triage agent as part of its Rovo AI portfolio. This out-of-the-box agent provides : Automatic case summaries Urgency and priority assessment Request type recommendations The agent is designed to work without custom builds, making AI-powered triage accessible to organizations of all sizes. Conclusion: The Predictable Service Desk Predictive auto-fill transforms the service desk from a reactive, manual triage operation into a predictable, automated system. Requests are categorized, prioritized, and routed consistently and instantly, freeing agents to focus on resolution rather than administration. Action Items for Your Organization Review your current triage process—what decisions are made manually? Clean your historical data—AI is only as good as the data it learns from Start with a pilot using "Show as Recommendation" approach Build confidence, then expand to "Apply by Default" Measure accuracy rates and reduction in triage time  

One Systemic Issue, Multiple Requests — How Service Request Linking Saves Time and Ensures Consistency The Systemic Issue Problem When a systemic issue affects multiple employees, handling each request separately creates inefficiency and inconsistency. For example, when a VPN issue affects 50 employees, processing each request independently: Wastes agent time on duplicate work Results in inconsistent communication Makes it harder to track the overall impact Reduces visibility into the root cause How Service Request Linking Works Service request linking enables support teams to connect multiple service requests to a single case . How it works: Multiple employees submit requests about the same issue An agent identifies they're related The requests are linked to a single case Actions are applied consistently to all associated requests Communication is sent to all affected employees The Benefits Benefit Description Efficiency One action applies to all linked requests Consistency Same communication, same resolution, same timeline Better tracking Understand the full scope of the issue Root cause analysis Identify systemic issues Reduced burden Agents handle systemic issues once, not 50 times When to Link Requests Good candidates for linking: Systemic outages: VPN issues affecting multiple employees Service degradation: Email delays affecting a department Process changes: New policy affecting all employees Major incidents: Security issues requiring coordinated response Not good candidates for linking: Individual issues: Password reset for one employee Unique requests: Each request has different requirements Non-systemic issues: Issues with different root causes The Reporting Benefit One often overlooked benefit of service request linking is better reporting . By linking requests, you can: Understand the true volume of systemic issues Identify root causes more quickly Track resolution across multiple employees Measure the impact of systemic issues on service delivery Service request dashboards provide visibility into metrics like : Total open requests Pending requests Open overdue requests Unowned requests Reopened requests Linking helps ensure these metrics accurately reflect the work being done, rather than counting multiple duplicate requests for the same issue. Conclusion: Linking Turns Chaos into Clarity Service request linking transforms a flood of individual requests into a manageable set of systemic issues. It saves time, ensures consistency, and provides better visibility into what's really happening in your organization. Action Items for Your Organization Train your team on when and how to link requests Identify patterns of duplicate requests Create a process for handling systemic issues Use linking data for root cause analysis Include linked requests in your reporting