How to automate internal IT tickets inside Freshservice using Risotto

Freshservice is a capable ITSM tool that handles ticket intake, queue management, workflow configuration, and reporting. And it does that whether or not your employees ever open the portal. 

Risotto adds an AI intake, triage, and automation layer on top of Freshservice. Employees ask in plain language in Slack, Risotto runs the troubleshooting and takes the action itself, and every step is logged against a Freshservice ticket in the background. 

This article explains where native Freshservice automation stops, what auto-resolution looks like step by step, what bi-directional sync does, and what setup involves. 

TL;DR

• Freshservice works well as a system of record, though it falls short of automatically resolving tickets. 
• ServiceBot brings Freshservice into Slack and Teams for intake and approvals, but Tier-1 volume still lands on your agents once the ticket is created.
• Risotto sits on top of Freshservice as an augmentation layer, so the system of record stays put and your existing workflows, SLAs, and routing rules are untouched.
• A 3-way sync connects the chat thread, the Freshservice ticket, and Risotto’s auto-solve capabilities, and every Risotto action is written back to the ticket for audit.
• Risotto resolves Tier-1 requests end to end in chat, granting access through your identity provider, resetting passwords, and troubleshooting issues. 

Is Freshservice an ITSM tool?

Freshservice positions itself as an enterprise AI ITSM platform built on ITIL best practices. It covers incident management, change management, asset management, and enterprise service delivery across IT, HR, finance, and other business teams. 

Using Freshservice as an ITSM tool gives your team accurate records, defensible audit trails, and reporting leadership will accept. 

What FreshService does well, and where it falls short

Freshservice works well as a system of record. Routing rules send requests to the right group, approval chains hold, and the reporting behind IT operations stands up when your CIO asks why last quarter looked the way it did.

Once a request exists as a ticket, you can see who owns it, what stage it's at, and how long it has been sitting there.

Freshservice also offers an employee chat layer. ServiceBot brings Freddy AI Agent into Slack and Teams, where employees can ask questions, raise requests, and track tickets without opening the portal. Freddy AI Agent is available on the Enterprise plan.

Freddy AI Agent can fulfill some requests, including password resets and access requests, when you’ve already built the corresponding catalog item and orchestration workflow. That means auto-resolution depends on what your team has configured in advance.

In practice, that experience can break down before a request is resolved. One team we spoke to found employees getting stuck mid-conversation with no ticket created, which pushed them back to DMing IT directly. Another organization disabled the Freshservice Slack bot because it mostly redirected employees to service catalog forms.

Knowledge coverage can be another limitation. Teams using tools like Notion or Confluence may find that Freddy can’t use the knowledge where it already lives, forcing them to duplicate content into Freshservice if they want the AI to access it.

The result is that Freshservice can automate parts of the request lifecycle, but end-to-end resolution depends on whether you’ve already built the right automated process and whether Freddy can access the knowledge it needs.

How Risotto turns Freshservice into an automated ITSM system

Infographic request: screenshot of the Risotto Freshservice integration in action

Risotto’s AI IT helpdesk software layer sits on top of Freshservice and connects via bi-directional ticket sync. Your workflows, SLAs, approval chains, and routing rules stay exactly as they are. Freshservice remains the system of record, and your agents keep working the queue they already know.

Every action Risotto takes is written back to the Freshservice ticket as an update: who made the request, what they asked for, what was approved, and when. Every action stays logged in both Risotto and Freshservice, so compliance reporting pulls from the records you already trust. And you get a comprehensive audit trail that’s easy to locate when you need it. 

Because every Risotto interaction is tied to a Freshservice ticket, you can compare automated and human-handled requests in the reporting you already use instead of relying on a separate deflection estimate. 

The mechanics come down to a 3-way sync between the Slack or Teams conversation, the Freshservice portal, and Risotto:

1. An employee asks a question in a thread. 
2. Risotto opens the Freshservice ticket, populates it, and routes it. 
3. Updates made in Freshservice appear in the thread, and replies in the thread land on the ticket. 

The big difference is that with Risotto, auto-resolution finishes the request rather than merely assisting the IT team in resolving it. Risotto runs real multi-step troubleshooting, asking follow-up questions and narrowing down the cause the way an agent would, then executes the action itself. 

It grants software access through your identity provider, resets passwords, collects approvals, and turns a resolved thread into a knowledge base article. It learns from your existing knowledge sources, past resolutions, and the conversations your agents are already having, so coverage grows without someone having to build a workflow for every scenario in advance.

Ironclad, for example, uses Risotto with Freshservice and reached around 91% auto-solve on access requests across 40–50 apps.

Importantly, you’re up and running in days, or in some cases, hours. Risotto customer Fundrise had the platform operational within an hour, implemented entirely by their internal IT team, after their previous chatbot had taken months of meetings with a vendor implementation team. And Gusto reached a 53% auto-resolution rate on day one.

‍

What happens when an employee asks for help in Slack

Need a better idea of what Risotto’s service desk automation process looks like in action? Here's a software access request, a big Tier-1 category for many companies, from first message to closed ticket.

1. The ask. Someone messages Risotto in Slack: 'I need access to Notion.' There’s no need to fill out a form or head to a portal and wait in a queue. 
2. Identification and policy check. Risotto recognizes this as an access request rather than a question, then checks the access rule you've configured for Notion against your identity provider. Rules can be scoped by department, seniority, and duration, so a senior engineer and a new marketing hire get different access.
3. 3. Approval. Where your policy requires sign-off, Risotto collects it in Slack, where approvers are more likely to see and respond to it than an email or ticket notification. It can DM the employee’s manager, notify an approver group, or post to a channel, depending on how the rule is written. Where policy allows the grant to proceed without approval, it proceeds. Rejections require a comment, so the reason is captured.
4. Provisioning. Risotto makes the grant itself through the IdP. If the rule specifies a time limit, the access expires on schedule without anyone having to manually revoke.
5. The record. All of this is writing to Freshservice as it happens. The ticket exists from the first message, with the requester, category, and department populated, along with the approval, the action taken, the result, and timestamps for each. 
6. Escalation. Anything outside policy goes to a human with the context already assembled. Risotto routes it to the right department based on the intent of the request, and the Tier 2 Assistant pulls the request context into a private view for the agent, along with a proposed resolution plan.

Keep Freshservice as the system of record, let Risotto do the resolving

When you sign on with Risotto, Freshservice keeps doing everything it already does. The system of record stays where it is, the workflows remain the same, and the audit trail stays complete. What changes is how much of your queue reaches a human at all.

With an IT automation layer that resolves instead of logging, most Tier-1 requests finish before anyone on your team opens a ticket, and auto-solve rate starts to shoot up. Risotto customer Vidyard, for example, saw 60% faster Tier-1 ticket resolution, with 80% of Tier-1 requests resolved instantly during the first month. 

To see the impact Risotto can have on your ticket queue, try it free for 30 days. Before you start, pull your current Tier-1 numbers and Freddy auto-resolution rate so you have a baseline to measure against.

Focus on auto-solve rate rather than deflection. Deflection means a question was answered or prevented from becoming a ticket, while auto-solve means the request was resolved end to end, including any action required.

Then start with your two heaviest ticket categories, and connect Risotto to Freshservice and your identity provider. If access requests and password resets are resolving end to end without an agent touching them, that's your answer.

FAQs about Freshservice ITSM

Is Freshservice an ITSM?

Freshservice is an IT service management platform from Freshworks, covering incident, problem, change, asset, and request management. It also reaches past core ITSM into IT asset management, IT operations management, and enterprise service management for teams like HR and finance. 

Freshworks positions it as ITIL-aligned and aimed at teams who want a faster setup than a legacy enterprise suite.

What exactly is Freshservice?

Freshservice is Freshworks' cloud-based service desk for internal support, meaning employee requests rather than customer tickets. Freshservice takes requests from a portal, email, and chat, then creates and routes tickets. AI tools like Freddy give IT teams context and suggestions that help them resolve requests faster.

Is Freshservice ITIL compliant?

Yes, to the extent software can be. Freshservice holds PinkVERIFY certification for six ITIL processes: incident, problem, change, asset, request, and service catalog management. Freshworks also lists Gold Accredited Tool Vendor status across 14 ITIL practices. Certification attaches to named processes rather than the product as a whole, so check the current listing for the practices your RFP actually asks about.

Is Freshservice the same as ServiceNow?

No. They're separate products from separate companies, but both cover core ITSM processes. The practical difference is scale and setup effort. ServiceNow is built for large enterprise deployments with heavy customization, while Freshservice is usually chosen for faster time to live.