How do I set up an AI agent in Freshservice? A step-by-step guide

What you actually get when you "set up an AI agent" in Freshservice

When people ask how to set up an AI agent in Freshservice, they usually mean one specific thing: Freddy AI Agent, the autonomous, employee-facing bot that answers questions and raises requests without a human touching the ticket. It's one of three products under the Freddy AI umbrella, so it's worth knowing which one you're turning on:

• Freddy AI Agent is the autonomous layer. It deflects routine requests (password resets, status lookups, access requests) by holding a conversation and pulling answers from your knowledge.
• Freddy AI Copilot is agent-assist inside the workspace: suggested replies, ticket summaries, real-time translation. It helps your humans, it doesn't replace them.
• Freddy AI Insights is the analytics layer for team leads, flagging things like CSAT dips and SLA breaches.

This guide is about the first one, the autonomous agent. Here's the configuration screen you're aiming for, where each channel gets its own switch:

On paper the payoff is big. Freshworks cites 66% ticket deflection and a 77% drop in average resolution time once the AI is doing its job. Those are vendor numbers, so treat them as a ceiling rather than a promise, but they tell you what a clean setup is supposed to deliver.

Before you start: the prerequisites nobody mentions

Most "how do I set up an AI agent in Freshservice" guides jump straight to the toggle. Three prerequisites trip people up first, so check them before you touch Admin.

One more thing if your instance is older: the legacy Virtual Agent (anything enabled before October 18, 2024) was deprecated on May 21, 2025. If you're upgrading from it, you'll re-enable Freddy on each channel after the upgrade rather than starting from a clean slate.

That session model is the first place I'd do real budgeting. 1,200 sessions a year sounds generous until you remember a single confused employee pinging Freddy three days running counts as three sessions. For a 600-person org, the cap gets real fast, which is the recurring theme in the Freshservice AI cost discussion.

How to set up an AI agent in Freshservice, step by step

With the prerequisites cleared, the actual setup is short. Here's the whole flow at a glance, then each step in detail.

Step 1: Confirm you're on the Enterprise plan

There's no workaround here. If you're on Pro or below, Freddy AI Agent won't appear in settings at all. Check your plan under Admin > Plans & Billing, and if you're weighing the jump, the Freshservice Pro plan versus Enterprise gap is the decision to model first.

Step 2: Open Global Settings and search for Freddy

Go to Admin > Global Settings and type Freddy into the search box. You'll see the Freddy AI card surface alongside the ServiceBot entries for Microsoft Teams and Slack.

Step 3: Enable Freddy AI Agent per channel

Open the Freddy card and you'll get a toggle for each deployment surface: Freddy AI Agent for Slack and Microsoft Teams, Email Bot, and Freddy AI Agent for Support Portal. Switch on only the channels you're ready to support. I'd start with one, usually the employee Support Portal, rather than lighting up all four at once. A narrow first rollout is far easier to judge and roll back.

If you're deploying to Slack or Teams, this is where the ServiceBot prerequisite from earlier matters: configure Freddy from the ServiceBot for Microsoft Teams or ServiceBot for Slack section. The Support Portal and Email Bot configure directly from the Freddy page.

Step 4: Connect your knowledge sources

This is the step that decides whether the agent is useful. Freddy grounds its answers in what Freshworks calls Enterprise Search, which can pull from your internal knowledge base, Microsoft SharePoint, Google Drive, and Confluence. Point it at the sources where your real answers live, not just the tidy public ones.

A word of warning that comes up constantly: the SharePoint connector asks for very broad permissions. More on that below, because it's the single most common reason a rollout gets blocked at the security-review stage.

Step 5: Test it, then watch your sessions

Before you announce it to the company, run a handful of real questions through the agent yourself. Then track adoption and accuracy in the Freddy AI Agent overview curated report in the Analytics module, which also shows how fast you're burning through that 1,200-session allowance. If you want to benchmark what "good" looks like, the metrics in our resolution rate guide are a fair reference even though they're framed for a different helpdesk.

That's the entire setup. Maybe 30 minutes if your plan and knowledge are already in place. Which is exactly why the next section matters more than this one.

The part the setup screen doesn't show you

Here's where I'd push back on the framing of the question itself. "How do I set up an AI agent in Freshservice" makes it sound like setup is the hard part. It isn't. The toggle is trivial. What determines whether your agent is any good is everything the configuration screen never surfaces.

These are the processing limits baked into how Freddy reads your knowledge:

• It processes only the first 50 inline images in a solution article.
• It processes only the first 5 attachments per article, up to 5 MB each.
• It cannot interpret .pdf, .docx, or .xlsx documents at all.
• An article can take anywhere from 1 hour to 24 hours to finish processing after you publish it.

Read that list again with your own runbooks in mind. If your IT knowledge lives in PDF SOPs or Word docs, which is the norm, Freddy can't see any of it until someone rewrites it as a native solution article. The agent isn't dumb, it's just reading a fraction of what you think you gave it. An AI agent is only as good as the knowledge it can actually parse, and that's the real setup task hiding behind the toggle.

This is also where getting articles in turns clunky. One admin on r/Freshservice described having to route article creation through an external tool just to get formatting that survives Freshservice's CSS stripping, "no formatting cleanup, no manual styling, just paste and publish." That's a workaround for a setup step that should have been built in.

What real Freshservice admins run into after go-live

The setup docs are tidy. Production is messier. Three patterns show up over and over in user feedback, and they're worth knowing before you flip the switch, not after.

The handoff tax can raise your resolution time. The most cited cautionary tale is a 600-person org whose tier-1 resolution time went up after enabling Freddy:

"Autoresolve is maybe 25% which is fine i guess. But our MTTR actually went UP. About 20% compared to where we were before... Freddy tries, fails, agent picks it up but has to scroll thru the full back-and-forth before they can respond... users who got autoresolved come back 2 days later w/ a follow up, new ticket because the original closed. Dup tickets are up like 15ish percent." - u/Time_Beautiful2460 on r/Freshservice

That's the failure mode an AI agent is supposed to prevent, happening because the bot tries everything and hands off badly. It's avoidable, but only if you set up routing deliberately rather than letting the agent attempt every ticket.

The SharePoint permissions can block sign-off. If you plan to ground Freddy in SharePoint, your security team will likely have questions:

"it requires 'Read files in all site collections' on an Application level to function, Which essentially give it the ability to read everything in our company Sharepoint as far as i'm aware... does anyone know exactly why such a broad permission scope is required for this?" - u/Towelie888 on r/Freshservice

A replier in the same thread confirmed they hadn't turned it on for exactly that reason. Budget time for the security review if SharePoint is in your plan.

Deflection without a learning loop plateaus. A sysadmin summed up the accuracy ceiling bluntly: the AI "is abysmal for incident deflection and offers zero insight into why users found it unhelpful when they rate it and it also doesn't learn from users rating an interaction as unhelpful." That last point is the one I'd weigh hardest, because an agent that doesn't learn from corrections never gets better than its first week.

None of this means don't set Freddy up. It means set it up with eyes open, and spend your effort on the rollout, not the toggle.

How to roll it out without raising your MTTR

After years of putting AI agents on live support and IT queues, the thing I'd attach to your setup isn't a feature, it's a process. The teams whose resolution times drop are the ones who treat go-live as the last step, not the first.

Simulate before you go live. The scariest thing I've watched an agent do wasn't fail, it was confidently confirm something false. One B2B technical support team had a bot tell customers "yes, we support your model" for products that weren't in their database, because the knowledge base said the company "supports all models." Nobody catches that from a settings page. You catch it by running the agent against your real historical tickets first and reading what it would have said. That dry run is the single highest-value setup step there is, and it's the one Freshservice's own flow skips.

Route by confidence, not by hope. The enterprise buyers I talk to almost all land on the same requirement. As one DTC support lead put it, "the AI will never be able to answer 100% of the questions... I need an AI who is only handling the tickets that it's confident to handle and all the other ones, leave them alone." That's the antidote to the MTTR problem above: an agent that only auto-replies when it's sure, and silently escalates everything else, never creates the read-the-whole-thread handoff tax.

Watch the sensitive stuff. IT tickets carry passwords, access requests, sometimes payment details. One buyer gated their entire trial on an internal security review until they were sure ticket data with PII stayed in their environment. Whatever agent you set up, know where the data goes before it touches a real ticket. Done right, the payoff is real: one team, Gridwise, saw eesel resolve 73% of tier-1 requests in the first month, with results showing inside a 7-day trial. The difference between that and a 20% MTTR regression is almost entirely the rollout, not the tool.

Try eesel for Freshservice teams

If the Enterprise gate, the session cap, or the PDF-blind knowledge base is your blocker, this is where I'd look at an AI layer like eesel. To be straight about it: eesel doesn't bolt into Freshservice as a native plugin the way Freddy does. What it does is sit across the same internal-IT surfaces your team already uses, Slack, Microsoft Teams, email, and Jira Service Management, and learn from the knowledge Freddy struggles with, including past tickets, Confluence, SharePoint, and Drive.

Two differences matter most for a team coming from Freshservice. First, the simulation mode runs the agent against your historical tickets before it ever answers a live one, so you see coverage and catch the confident-but-wrong answers up front. Second, the pricing is per ticket, not per Enterprise seat: eesel starts at $0.40 per ticket with no per-seat fee and no platform minimum on the self-serve plan, so you can route 200 tickets a month and pay for 200. If you're comparing routes for an AI service desk, that's a different cost shape than buying every IT agent an Enterprise license to unlock the bot.

It's not the only option, and for some teams staying inside Freshworks is the right call. But if your goal is an AI agent that reads your real knowledge and proves itself before it answers a single live ticket, it's worth a look.