Methodology: We used Freshworks' product and pricing pages, Freshservice support articles and API documentation, the Freshworks Gartner announcement and G2 reviews, all checked on 5 Oct 2026. No vendor reviewed or paid for this article. We did not run hands-on tests.
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 includes, what it really costs, and what breaks if you move data in or out.
Key takeaways
- Freshservice lists Starter at $19, Growth at $49 and Pro at $99 per agent per month billed annually, plus a custom-priced Enterprise plan (Freshworks pricing page, as of 5 Oct 2026).
- Problem, change and release management start on Pro (Freshworks pricing page, as of 5 Oct 2026).
- Freshworks says it was named a Leader in the 2026 Gartner Magic Quadrant for IT Service Management Platforms (Freshworks press release of 29 Jul 2026, checked 5 Oct 2026).
- G2 users rate Freshservice 4.6 out of 5 across 1,359 reviews (G2, as of 5 Oct 2026).
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. Workspaces let HR, facilities and other teams run their own service desks on the same account.
Freshworks says it is trusted by more than 20,000 businesses (Freshworks "What is Freshservice" page, as of 5 Oct 2026). It serves employees; customer support is Freshdesk's job.
How Freshservice ITSM works: records, workspaces and people
Freshservice is a set of linked record types inside workspaces. The links between records are what 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, with its requested items | 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 request | Incidents, problems, CIs, releases | Pro |
| Release | Deployment planning after a CAB-approved change | Changes | Pro |
| Asset / CI | Hardware, software and services in the CMDB | Other assets, tickets, services | ITAM package |
| Solution article | Knowledge content, public or private | Portal search | Starter |
Sources: Freshservice support articles on incident, problem, change and release management and the CMDB; plans from the Freshworks pricing page; all as of 5 Oct 2026.
In short, the incident is the hub: problems, changes and CIs hang off it, and releases hang off changes.
Workspaces
Tickets, form fields, workflows, service items and solution articles live inside a workspace, while user management, billing and default field settings stay global (Freshservice support, "What is a workspace", as of 5 Oct 2026). Agents hold full-time, occasional or day-pass licenses (Freshservice support, agent and license types article, as of 5 Oct 2026). Only IT workspaces get problem, change, release, alert and on-call management. Business workspaces use cases, queries, issues and requests instead (Freshservice support, IT vs business workspaces article, as of 5 Oct 2026).
Freshservice features by module
Freshservice ticketing and incident management
From an incident, agents can create or link a problem, change, project, child tickets and configuration items, and merge duplicates (Freshservice support, incident management article, as of 5 Oct 2026). Priority comes from a matrix, "Priority = Impact x Urgency," which applies to incident tickets, not service requests (Freshservice support, priority matrix article, as of 5 Oct 2026).
Service catalog and service requests
The service catalog nests up to three levels. Each item has its own form fields, and submitting one creates a service request, optionally with child requests (Freshservice support, service catalog article, as of 5 Oct 2026).
Freshservice change management, problems and releases
Problems hold root cause, impact, symptoms and workaround, plus a known error flag. Changes carry a change type and CAB approval, and link to a release that plans the deployment (Freshservice support, problem, change and release articles, as of 5 Oct 2026).
Freshservice asset management and CMDB
In Freshservice, "each asset is known as a Configuration Item (CI)" (Freshservice support, CMDB introduction, as of 5 Oct 2026). Assets relate through default or custom relationship types and can be tied to services (Freshservice support, asset relationships article, as of 5 Oct 2026).
ITAM is packaged separately. ITAM Growth includes discovery and the CMDB, Pro adds software asset management and contracts, and Enterprise adds service discovery, application dependency mapping and business service mapping (Freshworks ITAM pricing page, as of 5 Oct 2026).
Knowledge base, Workflow Automator and Freddy AI
The knowledge base uses categories, folders and articles, public or private (Freshservice support, knowledge base article, as of 5 Oct 2026). The no-code Workflow Automator is on every plan. Freddy AI Copilot drafts replies and summarizes tickets (Freshservice support, Freddy AI overview, as of 5 Oct 2026), and Freddy AI Agent Studio is free for Growth, Pro and Enterprise through 31 Dec 2026 (Freshservice support, AI Agent Studio FAQ, as of 5 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 5 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 |
| Pro | $99 | Problem, change, release and major incident management |
| Enterprise | Custom | Sandbox, audit logs, Freddy AI Insights |
Source: Freshworks pricing page, as of 5 Oct 2026.
The plan line matters more than the price gap: a team that runs formal problem and change processes needs Pro, so compare Pro, not Starter, with your current platform.
Costs beyond the seat price
| Cost line | List price | Who triggers it | Source (as of 5 Oct 2026) |
|---|---|---|---|
| Freddy AI Copilot | $29 per agent per month, billed annually | Agents using AI drafts | Freshworks pricing page |
| Business agent license | $49 per agent per month | HR or facilities agents | Freshworks pricing page |
| ITAM asset units | From $125 per month per 500 units; a server, VM or network device counts as 4 units, a desktop as 1 | Assets in the CMDB | Freshworks ITAM pricing page |
| Orchestration transactions | 1,000, 2,000, 5,000 or 20,000 per account per month by plan; extra packs $250 per 1,000 | Busy integrations | Freshworks pricing page |
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 20 x $29 x 12 = $6,960. One 500-unit asset pack covers 125 servers at 4 units each. This is our arithmetic on list prices (as of 5 Oct 2026), not a quote.
The gotchas: servers move the ITAM bill more than laptops, busy integrations can exhaust the orchestration allowance mid-cycle, and business teams bring their own license line.
Freshservice reviews and analyst standing in 2026
Freshworks announced 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 (Freshworks press release, checked 5 Oct 2026).
On G2, Freshservice holds 4.6 out of 5 from 1,359 reviews, with ease of use (229 mentions) and automation (101) among the top positives (G2 Freshservice reviews, as of 5 Oct 2026).
Common problems teams hit
The most-mentioned G2 cons are missing features (83 mentions), limited customization options (47), a steep learning curve (45), inadequate reporting features (30) and expense (27) (G2 Freshservice reviews, as of 5 Oct 2026). Freshworks' documentation adds three limits:
- Workspace moves. When records move between workspaces, 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 5 Oct 2026).
- API rate limits. The limit is 100, 200, 400 or 500 calls per minute on Starter, Growth, Pro and Enterprise, shared by every integration (Freshservice API documentation, as of 5 Oct 2026).
- Exports. List-view exports stop at 10,000 tickets and carry ticket-level fields only (Freshservice support, exporting tickets article, as of 5 Oct 2026).
Freshservice vs Freshdesk
Freshworks positions Freshservice for employee service delivery and Freshdesk for customer service (Freshworks Freshdesk vs Freshservice page, as of 5 Oct 2026).
| Freshservice | Freshdesk | |
|---|---|---|
| Built for | Employees: IT, HR, facilities | External customers |
| Assets and CMDB | ITAM package with CMDB | Not positioned for ITSM |
| Entry price (billed annually) | Starter $19 per agent/month | Growth $19 per agent/month |
| Top listed price | Pro $99; Enterprise custom | Enterprise $89 per agent/month |
Sources: Freshworks Freshservice and Freshdesk pricing pages, as of 5 Oct 2026.
Freshservice in a migration: what moves cleanly and what breaks
In or out, the record model decides the work. Tickets and conversations move well through the API; links, workspace structure and configuration are where data goes missing.
| Data | Moves cleanly | Breaks or gets rebuilt |
|---|---|---|
| Incidents and notes | Through the API; the Bulk API takes tickets and notes, 50 per request | The ticket type attribute says "[Support for only type 'incident' as of now]" |
| Service requests | Have their 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 | Separate API objects | Links to incidents and CIs re-created once both records exist |
| Assets and relationships | Both are API resources | Custom relationship types must exist on the target first |
| Workflows, SLA policies, business rules | Nothing; this is configuration | Rebuilt on the target, with running SLA timers |
Sources: Freshservice API documentation and Bulk API guide, as of 5 Oct 2026. The guide sets the Bulk API at 10 requests per minute and marks its limits "[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, business rules, automation rules and triggers for manual reconfiguration (Freshworks Zendesk to Freshservice migration page, as of 5 Oct 2026). The SLA timer for Pending and custom statuses is a per-status toggle, so check it before you compare SLA reports (Freshservice support, service desk statuses article, as of 5 Oct 2026).
Three things teams tend to miss:
- Requests need their own lane. Incidents and service requests use separate API paths, so a source that mixes them must be split before load.
- Original dates are not guaranteed. The API describes created_at only as "Ticket creation timestamp," and the Bulk API guide does not say whether original dates are kept (Freshservice API documentation and Bulk API guide, as of 5 Oct 2026). Test this before you promise SLA history to auditors.
- The Bulk API is for partners. Freshworks documents it for data migration partners, so a self-run import uses the standard API and its limits.
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 separately.
- Pick the ITAM package that covers your CMDB and discovery needs.
- Count servers separately from laptops, and estimate monthly orchestration transactions.
- Map your incident, request, problem and change states to Freshservice statuses.
- Decide which custom fields are global and which are workspace-specific.
- Inventory the links you rely on: incident to problem, change to CI, asset to service.
- List every workflow, SLA policy and automation to rebuild.
- Check your plan's API limit, test a full export, and confirm original dates survive a test import.
FAQ
Methodology
We used Freshworks' product and pricing pages, Freshservice support articles and API documentation, Freshworks' Gartner announcement and G2 data, all checked on 5 Oct 2026. Cost examples are our arithmetic on list prices. We did not run hands-on tests. Disclosure: MigrateX, the publisher of this article, runs ITSM data migrations, including between platforms named here. No vendor reviewed or paid for this article.