Do I Need to Replace Freshservice to Use an AI Agent?

Do you need to replace Freshservice to use an AI agent? No. Freshservice can stay the system of record, and both routes to an agent are documented. Freshworks sells its own: Freddy AI Agent answers employees in Slack, Microsoft Teams, email and the support portal on the Enterprise plan. Third-party agents connect through the Freshservice API instead, and Serval, Ravenna and Harmony each publish setup pages for a Freshservice ticket sync. Three things decide whether a third-party agent fits. The credential: Freshworks authenticates API calls with an agent’s personal key, which carries that agent’s role, and also supports OAuth. The rate limit: one allowance is shared by the whole account. The sync: vendors differ on which events cross in which direction, and the resolution of a ticket is the event to test on both sides before relying on it. Replacing Freshservice is a separate decision, and a migration.

What does Freshworks offer without a third party?

Freshworks documents an AI layer inside Freshservice. Its help centre article on Freddy AI Agent says the agent “is available with the Enterprise plan” and lists four channels: Slack and Microsoft Teams, an Email Bot, and the Support Portal. On Slack and Teams, ServiceBot has to be installed first; Freddy AI Agent is then configured from the Freddy AI configurations page or the ServiceBot section of the admin settings. The listed features include multi-turn conversations, citations and grounding, and enterprise search across the knowledge base, SharePoint, Google Drive and Confluence.

The pricing page sets the commercial frame. ServiceBot on Microsoft Teams and Slack is ticked in all four plans (Starter, Growth, Pro, Enterprise). Freddy AI Agent (Classic) comes with Enterprise, and “each Freshservice Enterprise license includes 1,200 sessions of Freddy AI Agent (Classic) per year”, a session being “any interaction a unique user has with an AI Agent within a 24-hour period”. Freddy AI Copilot, aimed at the service desk agents themselves, is an add-on at $29 per agent per month. Plans are priced per agent per month: $19, $49 and $99 billed annually for Starter, Growth and Pro, with Enterprise on quote. The same page lists “MCP actions” to “connect Freshservice and external AI systems”, in yearly allowances starting at 1,200 actions.

What does a third-party agent need from Freshservice?

An agent built by another vendor reaches Freshservice through its REST API, addressed at https://yourcompany.freshservice.com/api/v2/. Freshworks documents HTTP Basic authentication with a personal API key: “If you use the API key, there is no need for a password.” The key sits in the profile settings of an individual agent, so the agent that owns it is the identity the API sees. Freshworks states the consequence: “your ability to access data depends on the permissions available for your Freshservice profile”, with the example of a “Newbie Agent” role that may view tickets but not answer them. Username and password authentication is deprecated as of May 31, 2023, and the changelog entry for April 2024 says the APIs support OAuth, with the required scopes listed against each endpoint.

Vendors use these two routes differently, and the role they ask for differs too.

• Serval connects with a domain and an agent API key, and says “there is no OAuth flow and no token refresh”. It recommends a dedicated full-time agent with the Account Administrator role, or a custom role with workspace management permissions, because its health checks list the account’s workspaces.
• Harmony asks for the company subdomain and an API key, with a toggle to turn on bidirectional synchronisation.
• Ravenna connects with OAuth: a dedicated Freshservice agent signs in to FreshWorks and authorizes the connection. Its setup page notes that Freshservice’s separate integration users cannot sign in to the web portal, so they cannot complete that flow.

Whatever the route, the agent reaches what its Freshservice role allows. A dedicated account whose group and workspace membership is limited to the queues the agent will touch keeps that reach readable, and it survives the departure of the administrator who set it up.

The rate limit is the other shared constraint. Freshworks applies its per-minute limit “on an account wide basis irrespective of factors such as the number of agents or IP addresses used to make the calls”. For accounts created on or after 1 September 2020, the overall limit is 100 (Starter), 200 (Growth), 400 (Pro) and 500 (Enterprise) requests per minute, with sub-limits per action, for example 50, 80, 140 and 160 for Create Ticket. Invalid requests count towards the limit, and a call over it returns HTTP 429 with a Retry-After header. Paid add-on packs raise the overall limit to 1,000 or 2,000 requests per minute on Pro and Enterprise. An agent that polls, such as Serval’s default ticket sync every 30 seconds, draws on the same allowance as every other integration on the account.

• 01

  The key belongs to an agent

  Freshworks documents HTTP Basic with a personal API key and no separate password. Whoever owns the key is the identity the API sees.

  Freshworks API v2
• 02

  The role sets the reach

  Freshworks states that access depends on the permissions of the Freshservice profile in use, with a view-only "Newbie Agent" role as its example.

  Freshworks API v2
• 03

  One allowance per account

  Freshworks applies its per-minute API limit account-wide, whatever the number of agents or IP addresses, so every integration draws on the same allowance.

  Freshworks API v2
• 04

  Sync contracts differ

  Ravenna maps statuses through a fixed table, Serval polls every 30 seconds unless webhooks are enabled, and Harmony syncs tickets updated within the last 30 days.

  Ravenna, Serval and Harmony documentation

What syncs between the agent and Freshservice?

“Two-way sync” covers very different contracts. The documentation read for this guide draws it in three ways.

• Ravenna replicates per channel, each channel tied to one Freshservice workspace. Outbound, it creates tickets and syncs comments, status, priority and assignee. Inbound changes need a Workflow Automator webhook configured in Freshservice: “Connecting with OAuth alone does not set up the webhook.” The status mapping is fixed, with Ravenna’s Done mapped to Resolved (4) and Closed to Closed (5), and the reverse applied inbound. Attachments and ticket history are not synced, and custom fields go one way, as an HTML comment on the Freshservice ticket.
• Serval polls tickets every 30 seconds by default, or switches to three inbound webhooks. Enabling webhook sync turns polling off, and Serval warns that updates stop arriving if the Freshservice automators are not active first. A resolved or closed ticket’s resolution notes are ingested as a private note.
• Harmony pulls tickets, conversations, approvals, knowledge articles, assets, SLA policies and custom statuses, and, with bidirectional sync on, sends back status, priority, assignee, replies and internal notes. Ticket sync is scoped to tickets updated within the last 30 days.

Whichever vendor is on the shortlist, the same tests apply in a sandbox. Resolve a ticket on each side and record what happens on the other. Check that the status values a vendor maps to are enabled in your instance (Ravenna names codes 2, 3, 4 and 5). Check what happens to attachments. Run the inbound test from an account other than the integration agent, since Ravenna, for example, ignores events performed by its own OAuth agent to prevent sync loops.

A worked example: Siit’s Freshservice connector

Siit’s Freshservice page describes step by step how a request is escalated into a Freshservice ticket, so it serves here as a worked example, limited to what that page says. The connection takes the Freshservice domain and an API key generated from an agent’s profile; the page suggests an optional dedicated “Siit Integration” agent “so the integration survives admin turnover”. From a request’s side panel, Escalate ticket then Freshservice opens a form for group, ticket type, priority and required fields; Siit creates the ticket, links it back to the request and posts the link on both sides. The same step exists as a Create Freshservice ticket workflow action, with approval gating where needed, and every Freshservice action triggered from Siit is recorded on the request timeline. The page’s tips advise starting with one group and one ticket type, and keeping employees in Slack, Teams or the portal while specialists work the Freshservice ticket. How far an agent should act without a human is covered in what autonomy means for an IT agent; what differs between the two chat platforms is in Slack and Microsoft Teams.

Two Siit pages differ on whether the IT Agent can use this action. The Freshservice page says “/Freshservice create ticket is available inside IT Agent playbooks, with optional approval”. Siit’s Ticketing overview shows a dash, “—”, for Freshservice in its “Available in IT Agent” row. Both are quoted as published, and this guide does not reconcile them; confirm the action in the target workspace.

Where do these connections stop?

• Destinations follow the connecting agent. In Siit’s connector, a group missing from the destination picker means the agent “lacks access to that group”, and the integration “only surfaces ticket types the connecting agent can create”. Both are corrected in Freshservice.
• Serval attaches files through notes. Serval writes of its integration that “the Freshservice API v2 has no direct attachment upload”, so it posts files as notes on the ticket; its standalone attachment action defaults to a public note. Freshworks’ API reference lists attachments as supported on Create a Ticket, Update a Ticket and Reply to a Ticket.
• Native AI is plan-bound. Freddy AI Agent requires the Enterprise plan, and its 1,200 yearly sessions per license reset with each billing cycle.

Freshservice alternatives: keep it, or replace it?

A search for Freshservice alternatives often mixes two decisions. Adding an agent keeps Freshservice as the system of record, through Freddy AI Agent or a third-party connection. Replacing it moves tickets, workflows, SLAs and history to another platform. Several vendors that connect to Freshservice also sell that second path. Harmony’s Freshservice integration page lists a “Migration Path” use case: “Gradual transition from Freshservice to Harmony with bidirectional sync”. Serval’s home page presents a “full-stack ITSM built to replace” ServiceNow, JSM and Freshservice, and also “the automation layer on top of your existing ITSM”, with bi-directional sync so a team can “cut over the system of record when you’re ready”. Risotto’s Freshservice integration page says its agent works “within your Freshservice workflows, SLAs, and routing rules” and logs “every action as a Freshservice ticket update”; its FAQ adds that Risotto “can work for end-to-end ticketing as well”. None of the pages read here prices or schedules a migration.

The order that fits a given stack is worked through in adding an agent without replacing your ITSM; the Jira counterpart of this page is Jira Service Management.

Which vendors document an AI agent that connects to Freshservice?

Freddy AI Agent is Freshworks’ own agent, enabled from the Freshservice admin settings rather than connected from outside.

This list includes the vendors whose public documentation for an AI agent connecting to Freshservice documents the connection and what it creates or syncs. The authentication is stated where the page gives it.

• Harmony: its Freshservice integration page asks for the company subdomain and an API key, and lists what syncs from Freshservice and, with bidirectional sync on, back to it.
• Ravenna: its Freshservice setup and ticket replication pages describe an OAuth connection through a dedicated agent, a Workflow Automator webhook for inbound changes, and a fixed status mapping.
• Risotto: its Freshservice integration page says Risotto integrates with Freshservice to label, categorize and route tickets and logs every action as a Freshservice ticket update; the page does not specify the authentication method.
• Serval: its Freshservice integration page documents a domain and agent API key connection, ticket sync by polling or webhooks, knowledge sync and service catalog ingestion.
• Siit: its Freshservice page documents a domain and API key connection and ticket creation from a request or a workflow. Its page documents configurable sync options but gives conflicting instructions on resolution sync.