What is Freshservice? 2026 guide to features, plans and fit
What is Freshservice? See its record model, modules, plans, AI and asset add-on costs, and what breaks when data moves in or out. Read the 2026 guide.
Published Updated 12 min read

On this page
- What is Freshservice?
- How Freshservice ITSM works: records, workspaces and people
- Freshservice features by module
- Freshservice plans and true cost
- Freshservice reviews and analyst standing in 2026
- Common problems teams hit
- Freshservice in a migration: what moves cleanly and what breaks
- Checklist: before you buy or inherit Freshservice
- FAQ
What is Freshservice? It is Freshworks' IT service management (ITSM) platform, where IT teams run incidents, service requests, problems, changes, releases and IT assets in one cloud service desk. HR, facilities and other internal teams can use it too, each in its own workspace.
If you are shortlisting Freshservice or have inherited an instance, this guide explains how its records fit together, what each plan really costs once AI and asset add-ons are counted, and what breaks if you move data in or out.
What is Freshservice?
Freshservice is Freshworks' cloud-based IT service management and enterprise service management platform. It covers incident, service request, problem, change and release management, plus IT asset management with a CMDB, a knowledge base, a no-code Workflow Automator and Freddy AI.
Freshworks says it is "Trusted by 20,000+ businesses worldwide" (Freshworks "What is Freshservice" page, as of 26 Oct 2026). It serves employees, while Freshdesk serves external customers; our Freshdesk vs Freshservice guide compares the two.
How Freshservice ITSM works: records, workspaces and people
Freshservice is a set of linked record types inside workspaces, and those links turn a ticket list into service history.
| Record type | What it holds | Links to | First plan |
|---|---|---|---|
| Ticket (incident) | An unplanned interruption or drop in quality of an IT service | Problems, changes, projects, child tickets, CIs | Starter |
| Ticket (service request) | A request from a service catalog item | Child requests, the parent ticket | Growth |
| Problem | Root cause, impact, symptoms, workaround, known error flag | Incidents, changes, CIs | Pro |
| Change | Change type and CAB approval | Incidents, problems, CIs, releases | Pro |
| Release | Deployment planning after an approved change | Changes | Pro |
| Asset / CI | Hardware, software and services in the CMDB | Other assets, tickets, services | ITAM package |
| Solution article | Knowledge content, visible to all users, all agents or chosen departments | Portal search | Starter |
Sources: Freshservice support articles and the Freshworks pricing page, as of 26 Oct 2026.
In short, the incident is the hub: problems, changes and CIs hang off it, and releases hang off changes.
Workspaces and agent licenses
Tickets, fields, workflows, service items and solution articles live inside a workspace, while user management, billing and default ticket fields stay global (Freshservice support, "What is a workspace", as of 26 Oct 2026). Only IT workspaces get problem, change, release, alert and on-call management; business workspaces use case, query, issue and request ticket types (Freshservice support, IT vs business workspaces, as of 26 Oct 2026).
Agents hold IT full-time, IT occasional or business licenses. Business licenses are "Available as an add-on for Pro/Enterprise plans", and occasional agents log in with day passes (Freshservice support, agent and license types, as of 26 Oct 2026).
Freshservice features by module
Freshservice ticketing, service requests and change management
From an incident, agents can link a problem, change, project, child tickets and CIs, and merge duplicates. Priority comes from a matrix, "Priority = Impact x Urgency," documented for incident tickets (Freshservice support, incident and priority matrix articles, as of 26 Oct 2026). The service catalog nests up to three levels, and each item can raise child requests (Freshservice support, service catalog, as of 26 Oct 2026).
Freshservice asset management and CMDB
In Freshservice, "Each asset is known as a Configuration Item (CI)" (Freshservice support, CMDB introduction, as of 26 Oct 2026). Assets relate through default or custom relationship types, each with a normal and an inverse direction, and can be tied to services.
ITAM is packaged separately: ITAM Growth includes discovery and the CMDB, Pro adds software asset management and contracts, and Enterprise adds service discovery and service mapping (Freshworks ITAM pricing page, as of 26 Oct 2026).
Knowledge base, Workflow Automator and Freddy AI
The knowledge base uses categories, folders and articles. The no-code Workflow Automator is on every plan. Freddy AI Copilot suggests replies, summarizes ticket conversations and drafts resolution notes (Freshservice support, Freddy AI feature overview, as of 26 Oct 2026). AI Agent Studio, for no-code AI agents, is a promotional free service on Growth, Pro and Enterprise through 31 Dec 2026, with pricing "shared closer to the end of the promotional period" (Freshservice support, AI Agent Studio FAQ, as of 26 Oct 2026).
Freshservice plans and true cost
List prices are per agent per month, billed annually, with a 14-day free trial (Freshworks pricing page, as of 26 Oct 2026). Our Freshservice pricing guide covers each add-on in more depth.
| Plan | From price | What it adds |
|---|---|---|
| Starter | $19 | Incident management, knowledge base, Workflow Automator, workspaces |
| Growth | $49 | Service catalog, SLA management, on-call |
| Pro | $99 | Problem, change, release and major incident management |
| Enterprise | Custom | Sandbox, audit logs, Freddy AI Agent (Classic), Freddy AI Insights |
Source: Freshworks pricing page, as of 26 Oct 2026.
Teams that run formal problem and change processes need Pro, so compare Pro, not Starter, with your current platform.
Costs beyond the seat price
| Cost line | List price | Who triggers it |
|---|---|---|
| Freddy AI Copilot | $29 per agent per month billed annually, $35 monthly; Pro and Enterprise | Agents using AI drafts |
| Business Agent License | $49 per agent per month; Pro and Enterprise add-on | HR or facilities agents |
| Day passes | $3, $7, $14 or $18 a day by plan | Occasional agents and their API keys |
| ITAM asset units | From $125 a month per 500 units; a server, VM or network device uses 4, a desktop 1 | Assets in the CMDB |
| Orchestration transactions | 1,000, 2,000, 5,000 or 20,000 a month by plan; packs $250 per 1,000 | Busy integrations |
| MCP actions | 1,200, 6,000 or 12,000 a year on Growth, Pro and Enterprise; packs $15 per 1,000 | External AI systems acting in Freshservice |
Sources: Freshworks pricing and ITAM pricing pages; Freshservice support (license types, day passes); as of 26 Oct 2026.
A worked example: a 20-agent IT team that needs change management pays 20 x $99 x 12 = $23,760 a year for Pro seats, and Copilot for all 20 adds $6,960 billed annually or $8,400 billed monthly (our arithmetic on list prices, not a quote).
The gotchas:
- Servers move the ITAM bill. The pricing page lists 100 ITAM Growth asset units with Growth, Pro and Enterprise, which covers only 25 servers at 4 units each.
- Overage packs expire. Orchestration packs last only until the end of the billing cycle (Freshworks pricing page, as of 26 Oct 2026).
- Integrations can spend day passes. An occasional agent's API key used in workflows or integrations "will consume a day pass" (Freshservice support, day passes, as of 26 Oct 2026).
Freshservice reviews and analyst standing in 2026
Freshworks announced in a press release on 29 Jul 2026 that it was named a Leader in the 2026 Gartner Magic Quadrant for IT Service Management Platforms, a report dated 27 Jul 2026 (checked 26 Oct 2026). For buyers, that signals Freshservice is assessed as a full ITSM platform; it does not show whether it fits your CMDB depth or budget.
On G2 (4.6 out of 5, 1,363 reviews), Ease of Use (158 mentions) and Automation (75) lead the positives (G2, as of 26 Oct 2026).
For US public sector buyers, Freshservice is FedRAMP "In-Process" for Class C (Moderate) and not yet certified (Freshworks, 6 Aug 2026; FedRAMP Marketplace, as of 26 Oct 2026).
See also Freshservice vs ServiceNow and Jira Service Management vs Freshservice.
Common problems teams hit
The most-mentioned G2 cons are Missing Features (54 mentions), Limited Features (42), Learning Curve (36) and Limited Customization (33) (G2, as of 26 Oct 2026). Freshworks' documentation adds three limits:
- Workspace moves. Values in workspace-specific custom fields "are not transferred and will be permanently lost," and bulk moves handle up to 100 items (Freshservice support, moving tickets across workspaces, as of 26 Oct 2026).
- API rate limits. 100, 200, 400 or 500 calls per minute by plan, shared by every integration; packs raising it to 1,000 or 2,000 are Pro and Enterprise only (Freshservice API documentation, as of 26 Oct 2026).
- Exports. Exports stop at 10,000 tickets, and "Standard data exports include ticket-level data only and do not include conversations or internal notes" (Freshservice support, exporting tickets, as of 26 Oct 2026).
If those limits rule it out, compare the Freshservice alternatives before you renew.
Freshservice in a migration: what moves cleanly and what breaks
In or out, the record model decides the work: tickets move well, while links, note visibility and configuration go missing. Our Freshservice platform page shows which records we move in and out.
| Data | Moves cleanly | Breaks or gets rebuilt |
|---|---|---|
| Incidents and notes | Bulk API takes tickets and notes, 50 per request | Ticket type: "Support for only type 'incident' as of now" |
| Private notes | Notes carry a private attribute in the API | Private notes are "only visible to agents logged in to your service desk"; lose the flag and requesters can see them |
| Service requests | Own "Create a Service Request" endpoint | Requested items and catalog context need separate mapping |
| Attachments | Up to 40 MB per entity through the Bulk API | An over-limit attachment is rejected while the ticket is still created |
| Problems, changes, releases, assets | Separate API objects | Links to incidents and CIs, and custom relationship types, re-created on the target |
| Workflows, SLA policies, business rules | Nothing; this is configuration | Rebuilt on the target, with running SLA timers |
Sources: Freshservice API documentation, Bulk API guide and private notes article, as of 26 Oct 2026. The guide caps the Bulk API at 10 requests per minute, limits marked "To be confirmed post load testing."
Workflows, automations, business rules, SLA definitions and running SLA timers are rebuilt on the target, not migrated; Freshworks' own Zendesk to Freshservice guide lists "SLA policies and business rules" for manual configuration (Freshworks, as of 26 Oct 2026).
Three things teams tend to miss:
- Original dates are not guaranteed. The API describes created_at only as "Ticket creation timestamp," and the Bulk API guide is silent on original dates. Test this before you promise SLA history to auditors.
- Automations keep running. The Bulk API guide says Slack, Teams, business rules and workflows "Will not be muted" during a load, so switch them off first.
- The Bulk API is for partners. Freshworks documents it for migration partners; a self-run import uses the standard API.
Checklist: before you buy or inherit Freshservice
- List the ITIL processes you run and confirm which plan includes each.
- Decide on one IT workspace or several, and which business teams join later.
- Count full-time, occasional and business agents, and find occasional agents' API keys.
- Pick the ITAM package you need and count servers separately.
- Estimate orchestration transactions, MCP actions and AI Agent Studio use from January 2027.
- Map your incident, request, problem and change states to Freshservice statuses.
- Decide which custom fields are global and which are workspace-specific.
- Inventory the record links you rely on and every workflow and SLA policy to rebuild.
- Test a full export with conversations and private notes.
- Confirm original dates survive a test import.
Facts checked October 26, 2026 from Freshservice pricing, Freshservice ITAM pricing, Freshservice support, Freshservice API docs and FedRAMP Marketplace. No vendor paid for this article. How we research
FAQ
What is Freshservice used for?
Freshservice is used for IT service management: resolving incidents, fulfilling catalog requests, managing problems, changes and releases, and tracking IT assets in a CMDB. HR, facilities and other internal teams can run their own requests in business workspaces. It serves employees rather than external customers, which is the main difference from Freshdesk.
How much does Freshservice cost?
Freshservice lists Starter at $19, Growth at $49 and Pro at $99 per agent per month billed annually, with Enterprise priced on request. Problem and change management start on Pro. Freddy AI Copilot adds $29 per agent per month on Pro and Enterprise, and ITAM asset units start at $125 a month per 500 units (Freshworks pricing pages, as of 26 Oct 2026).
Can you export all your data from Freshservice?
Not from a standard export. Exports stop at 10,000 tickets and include ticket-level data only, without conversations or internal notes. Freshworks points to the API or the account-wide XML export for complete history, including notes and timestamps (Freshservice support, exporting tickets, as of 26 Oct 2026). Plan for API rate limits, and export record links and attachments too.
Is Freshservice FedRAMP authorized?
Not yet. Freshworks said on 6 Aug 2026 that Freshservice reached FedRAMP "In-Process" status for Class C (Moderate), and the FedRAMP Marketplace lists it in initial implementation, not yet certified (FedRAMP Marketplace, as of 26 Oct 2026). US federal buyers who need an authorization today should confirm the current status with Freshworks before shortlisting it.
How long does it take to implement or migrate to Freshservice?
There is no neutral public benchmark. Freshworks says "On average, Freshservice customers go live in under 90 days" (Freshworks press release, 29 Jul 2026), a vendor claim. Real duration depends on record volume, attachments, workspaces, how many record links you keep and how many workflows you rebuild. Run a test migration on a sample before committing to a cutover date.
Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose. GARTNER and MAGIC QUADRANT are registered trademarks of Gartner, Inc. and/or its affiliates in the U.S. and internationally.
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


