Enterprise IT teams are all too familiar with the frustration that follows a submitted ticket for a intricate software glitch. After filling out the form, users often find themselves staring at a status bar that barely moves, while the clock ticks on productivity losses. The initial wave of AIโpowered chatbots managed to take care of the simplest requestsโpassword resets, basic software approvals, and routine access questionsโby following static decision trees. However, as soon as a ticket veers into ambiguous territory that demands genuine troubleshooting, those early bots hit a hard limit and hand the issue back to a human engineer. This gap creates a bottleneck where skilled staff spend hours reproducing problems that could have been solved programmatically if the system understood context and could learn from past incidents. Recognizing this shortfall, a new breed of AIโnative helpdesk platforms is emerging, aiming to bridge the divide between superficial automation and deep, adaptive problem solving. Risottoโs announcement of its Autonomous IT Engineer marks a significant step in that direction, promising to handle Tierโ2 inquiries that previously required expert intervention. By framing the challenge as one of knowledge retention and iterative improvement, the company sets the stage for a broader conversation about how enterprises can transform their internal support from a cost center into a selfโoptimizing engine.
Firstโgeneration conversational agents were built on the premise that most IT requests follow predictable patterns, allowing developers to encode a finite set of intents and corresponding responses. While this approach works well for highโvolume, lowโcomplexity tasks such as resetting a forgotten password or granting access to a commonly used application, it falters when the underlying issue involves multiple interacting components, unclear error messages, or environmental factors that are not captured in the knowledge base. In those situations, the botโs ruleโbased logic cannot infer the necessary diagnostic steps, leading to a fallback to human analysts who must then sift through logs, reproduce the scenario in a test environment, and devise a remediation plan manually. The inefficiency is compounded by the fact that each novel problem forces the same investigative cycle to repeat, consuming valuable engineer hours that could be redirected toward strategic initiatives. Moreover, the lack of a mechanism to capture and reuse the insights gained from these oneโoff investigations means that institutional knowledge evaporates as soon as the ticket is closed. Consequently, organizations experience a perpetual cycle of rediscovery, where the same root cause resurfaces weeks or months later, demanding the same manual effort again. Overcoming this limitation requires an AI system that can not only interpret natural language descriptions of problems but also dynamically explore system telemetry, hypothesize root causes, and validate fixes in real time.
Risottoโs Autonomous IT Engineer is positioned not as a simple chatbot faรงade but as a digital employee endowed with the ability to reason through unfamiliar IT incidents from start to finish. When a user submits a Tierโ2 ticket describing a puzzling application error or a performance degradation, the agent begins by ingesting the accompanying contextโsuch as the userโs role, device specifications, recent configuration changes, and any attached screenshots or error codes. Simultaneously, it queries monitoring systems, log aggregators, and configuration management databases to construct a temporal view of the system state leading up to the incident. Using a combination of statistical anomaly detection and causal reasoning models, the engineer generates a ranked list of potential root causes, each accompanied by a proposed remediation pathway. Before any change is applied, the platform presents the recommended steps to a designated human reviewer for approval, ensuring that critical alterations undergo a safety check. Once sanctioned, the agent can execute the fix via predefined automation scripts or API calls, update the ticket with a detailed resolution narrative, and close the loop. This endโtoโend capability moves the technology beyond mere suggestion engines into a realm where the AI can act autonomously while still respecting governance controls.
The fundamental weakness of legacy IT automation lies in its static nature: workflows are hardโcoded around known failure modes and expected inputs, leaving little room for adaptation when an unprecedented edge case surfaces. In practice, this means that when a novel combination of software versions, network configurations, or user behaviors produces an error that the preโbuilt scripts do not anticipate, the automation stalls and a human engineer must intervene to perform adโhoc troubleshooting. The engineerโs manual investigationโoften involving log correlation, hypothesis testing, and iterative experimentationโrepresents a nonโscalable cost because each unique incident consumes a comparable amount of time and expertise. Furthermore, because the resolution is typically documented only as a freeโtext note inside a closed ticket, the learned insights are not fed back into the automation library, causing the system to remain oblivious to the newly discovered pattern. As a result, the same class of problem will trigger the same manual effort the next time it appears, eroding any potential efficiency gains from the original automation effort. To break this cycle, an AI system must treat every solved incident as an opportunity to enrich its knowledge base, converting tacit knowโhow into executable, versionโcontrolled runbooks that can be invoked without human assistance in future occurrences.
Beyond the immediate labor expense, the hidden cost of relying on manual troubleshooting is the gradual dissipation of institutional knowledge within IT teams. When a senior engineer spends a day diagnosing a perplexing integration issue between a legacy database and a newly deployed microservice, the mental model they constructโcomprising assumptions about data flow, timing sensitivities, and configuration quirksโis rarely captured in a format that others can reuse. Instead, the outcome is often buried in a ticket comment or a Slack thread that becomes difficult to locate months later when a similar symptom resurfaces. This knowledge loss forces organizations to rebuild expertise from scratch each time, leading to duplicated effort, longer meanโtimeโtoโresolution, and increased frustration among endโusers who experience recurring outages. Moreover, the reliance on tribal knowledge creates a singleโpointโofโfailure risk: if the engineer who solved the original problem leaves the company, the undocumented fix may disappear entirely, leaving the team to rediscover the solution through trial and error. By contrast, an AIโdriven approach that automatically extracts the logical steps, configuration changes, and validation tests from a successful remediation can preserve that knowโhow in a searchable, versionโcontrolled repository. Such a repository not only accelerates future incident response but also serves as a training tool for newcomers, shortening the rampโup period and democratizing expertise across the organization.
When confronted with a previously unseen issue, the Autonomous IT Engineer initiates a multiโstage investigative workflow that mirrors the best practices of seasoned troubleshooters. First, it normalizes the incoming ticket data, extracting entities such as affected services, error codes, timestamps, and userโprovided descriptions. Next, it launches parallel queries against telemetry sourcesโincluding application performance monitoring tools, log aggregation platforms, and configuration management databasesโto gather a holistic view of the systemโs state before, during, and after the reported anomaly. Using a combination of unsupervised learning techniques to detect outliers and supervised models trained on historical incident patterns, the agent scores potential root causes and assembles a hypothesis graph that links symptoms to possible culprits. Each hypothesis is accompanied by a concrete remediation plan, detailing the specific commands, API invocations, or configuration adjustments required to test the fix. Before execution, the platform surfaces the proposed steps to a designated approver via a concise, humanโreadable summary, allowing for validation, modification, or rejection. Upon receiving approval, the engineer carries out the remediation in a controlled manner, verifies the outcome against predefined success criteria, and records the entire processโincluding inputs, actions, and resultsโwithin an auditโready runbook. This closedโloop mechanism ensures that every solved incident contributes to a growing library of verified solutions.
The true differentiator of Risottoโs offering lies in its automatic conversion of each successfully resolved incident into a reusable, selfโimproving runbook. After the humanโinโtheโloop approval step, the platform extracts the precise sequence of actions that led to a verified fix, parametrizes any environmentโspecific values, and stores the workflow as a modular automation component. These components are tagged with metadata such as the affected software versions, symptom patterns, and validation criteria, enabling the system to match future tickets with high precision. When a new request arrives that closely resembles an existing runbook, the Autonomous IT Engineer can propose the stored workflow with a confidence score, dramatically reducing the need for fresh analysis. Moreover, the platform continuously monitors the execution outcomes of these runbooks; if a particular automation begins to fail due to environmental changes, the system flags it for review and suggests updates, thereby maintaining relevance over time. This iterative improvement loop transforms the IT support function from a reactive help desk into a proactive knowledge engine, where each solved problem raises the baseline of automation coverage and reduces the likelihood of repeat incidents. Over months of operation, organizations can expect to see a compounding effect: the proportion of tickets resolved without human intervention climbs as the runbook library expands, while the meanโtimeโtoโresolution shrinks for the remaining complex cases.
Aron Solberg, the CEO and coโfounder of Risotto, emphasizes that while deflecting simple requests like password resets is table stakes for any AI helpdesk, the real bottleneck in enterprise IT stems from the absence of documented workflows for intricate, undocumented processes. He notes that many organizations possess a wealth of tacit expertise buried in the minds of senior engineers, yet lack a systematic way to capture and operationalize that knowledge. The Autonomous IT Engineer is designed to bridge that gap by not only resolving the immediate issue but also by distilling the troubleshooting steps into a standโalone automation that can be invoked by anyone, regardless of seniority. In Solbergโs view, the agents evolve from mere consumers of existing tools to creators of new ones, effectively building the very tooling they need to handle future variability. This perspective shifts the narrative from AI as a costโcutting substitute to AI as a force multiplier that augments human expertise, enabling IT teams to focus on architecture, innovation, and strategic initiatives rather than repetitive firefighting.
To avoid starting from a blank slate, Risotto equips its platform with a โPast Ticket Miningโ capability that scans the previous ninety days of an organizationโs helpdesk data to surface latent automation opportunities. The mining engine parses ticket fieldsโincluding subject lines, descriptions, attachments, and resolution notesโto identify recurring symptom clusters, common root causes, and frequently applied fixes. Using natural language processing techniques, it groups similar incidents together and generates draft workflow templates that capture the essential diagnostic and remediation steps. Administrators can review these drafts, tweak parameters, or approve them outright, after which the system converts them into executable runbooks linked to the appropriate APIs or MCP endpoints. In addition to automated discovery, users can express desired automations in plain languageโfor example, โwhenever a user reports a VPN disconnect after 5โฏp.m., reset the client profile and notify the network teamโโand the platform will synthesize, test, and deploy the corresponding automation. This dual approach ensures that the solution leverages historical patterns while remaining flexible enough to accommodate novel process definitions expressed directly by IT stakeholders, accelerating timeโtoโvalue and reducing the reliance on manual workflow creation.
Risottoโs vision extends past reactive ticket resolution into the realm of proactive IT operations, offering builtโin analytics that transform raw telemetry into actionable insight within minutes. Administrators can design custom dashboards that blend live metrics from monitoring tools, ticket volumes, and runbook execution rates, all displayed through an intuitive interface that requires no separate BI ticket or dataโengineering effort. These visualizations enable leaders to spot emerging trendsโsuch as a gradual increase in authentication failures across a specific applicationโor to validate the impact of recent changes in real time. Moreover, the platform supports the creation of eventโdriven or scheduled triggers that automatically initiate predefined workflows when certain conditions are met. Examples include running nightly health checks on critical services, provisioning standardized developer workstations during onboarding, or rotating credentials in response to a security alert. By shifting the focus from putting out fires to preventing them, IT departments can reallocate skilled personnel toward architecture review, capacity planning, and innovation projects. The resulting operational model not only improves service reliability but also enhances employee satisfaction, as endโusers experience fewer disruptions and faster resolution times when issues do arise.
Early adopters of Risottoโs Autonomous IT Engineer have reported substantial improvements in key support metrics, underscoring the platformโs potential to reshape IT service management. Customers such as Gusto, Instacart, Docker, Retool, ThoughtSpot, Patreon, and Ironclad have integrated the agent into their existing ITSM toolchains and observed measurable gains. According to the company, average firstโresponse times have collapsed to under four seconds, while autoโsolve ratesโthe proportion of tickets resolved without human interventionโrange from forty to ninety percent depending on the maturity of the deployed runbooks. In a highlighted case study with Ironclad, the platform achieved a ninetyโone percent autoโsolve rate, dramatically reducing the load on the Tierโ2 team. Vidyard reported an eighty percent automation rate for Tierโ1 requests within the first thirty days of deployment, and at Gusto the system delivered a fiftyโthree percent resolution rate on day one, translating into an estimated saving of one hundred fourteen thousand hours of user wait time. These figures illustrate a clear ROI: faster user satisfaction, reduced overtime for engineers, and a tangible decrease in the cost per ticket. The breadth of industries represented among the early customers also signals that the solutionโs value proposition transcends sectorโspecific nuances, applying equally to SaaS providers, financial technology firms, and developerโfocused organizations.
Financially, Risotto remains well positioned to scale its ambitions, having closed a tenโmillionโdollar seed round earlier this year led by Bonfire Ventures, with participation from 645 Ventures, Y Combinator, Ritual Capital, Surgepoint Capital, and notable angel investors including former executives from Dropbox and HelloSign. This capital infusion provides runway for product expansion, deeper integrations with enterprise IT stacks, and growth of the customer success organization. Looking ahead, the market for AIโaugmented ITSM is projected to expand rapidly as enterprises contend with increasingly heterogeneous environmentsโmultiโcloud deployments, microservices architectures, and a proliferation of thirdโparty SaaS applicationsโall of which generate complex failure modes that static automation cannot handle. For IT leaders evaluating solutions like Risottoโs Autonomous IT Engineer, a pragmatic first step is to conduct a baseline assessment of current ticket volume, categorization, and meanโtimeโtoโresolution to quantify the potential impact of increased automation. Subsequently, launching a pilot focused on a wellโdefined subsystemโsuch as a specific application suite or a set of recurring onboarding tasksโallows teams to measure autoโsolve rates, user satisfaction scores, and engineer time savings in a controlled setting. Finally, establishing a governance framework that defines approval thresholds, audit logging, and runbook review cycles ensures that the AI operates safely while continuously learning from each incident. By following this phased approach, organizations can convert todayโs reactive support model into a selfโoptimizing, knowledgeโdriven operation that delivers both immediate efficiency gains and longโterm strategic advantage.