How to Set Up Freshservice IT Helpdesk Without a Consultant

November 2, 2026

Freshservice is an IT service management platform — tickets, assets, change management and a self-service portal in one system. A working first setup takes a day: import requesters, define two agent groups, build one service catalogue item with an approval, then link assets. Anything beyond that is refinement.

It is more structured than a helpdesk and less bureaucratic than ServiceNow, which is exactly the middle ground most IT teams with 100–2,000 employees need.

What makes Freshservice different from a plain helpdesk?

A helpdesk handles requests. Freshservice also tracks the things requests are about — laptops, licences, servers — and ties tickets to those assets. When someone reports a failing laptop, the agent sees the model, purchase date and warranty status on the ticket without asking.

Pricing, as of 2026: Starter $19/agent/month, Growth $49, Pro $95, Enterprise $119. A free plan exists for up to 5 agents with limited features.

Step 1: import requesters before agents

Requesters are your employees. Import them from your directory — Freshservice supports Azure AD, Google Workspace and Okta sync as well as CSV.

Use the CSV route if your directory is messy (mixed naming conventions, shared mailboxes in the user list). Columns needed: First name, Last name, Email, Department, Job title, Location. Do not import shared mailboxes as requesters; they generate phantom tickets.

Step 2: define two groups, then stop

Groups drive assignment. Start with:

  • IT Support — first line, handles standard tickets.
  • IT Infrastructure — second line, handles requests escalated out of first line.

People want a group per system (a “Network” group, a “SaaS” group, an “App Support” group) on day one. Don’t. Groups are cheap to create and expensive to clean up, because historical tickets get orphaned when you merge them.

Step 3: build one service catalogue item

The service catalogue is the part that changes how employees behave. A good first item: New Employee Laptop Request.

  1. Go to Admin → Service Catalog → New Item.
  2. Name it plainly and set the display category to Hardware.
  3. Add custom fields: laptop type (standard/performance), required software, start date.
  4. Add an approval node: approver = requester’s reporting manager, using the manager field from your directory sync.
  5. Attach a task list for IT: prepare device, image, assign asset tag, ship.

Once live, an employee fills the form and the manager approves inside the portal. No email thread, no lost spreadsheet row.

Admin → Asset Management → Import Assets takes a CSV. Import laptops and servers first. Licences and peripherals can wait.

Asset linking matters because it powers the asset-related ticket reports and the warranty logic. A quick sanity check: after importing 200 laptops, open one and confirm the associated user field is filled. Blank user fields mean your email column didn’t match any requester — usually a casing or alias problem.

Is Freshservice’s free plan enough to try it?

The free plan covers up to 5 agents with ticketing and the portal but no asset management and no workflow automation. That’s enough to test the portal experience with real employees and not enough to run an IT department.

Start on Growth ($49) if you need approvals and the service catalogue — Starter ($19) lacks the approval node the laptop request depends on.

Step 5: check the notifications before go-live

Default notification templates are loud. Freshservice will mail requesters on every agent comment, every status change, every reassignment. Open Admin → Notification Settings and turn off “agent comment added” for requesters. Otherwise your first week of tickets trains people to filter you into a folder.

Freshservice ships with a full set of templates; better to delete three than to explain why you sent eleven emails about one reset.

Where Freshservice is the wrong call

If you’re a non-IT team — marketing ops, legal, a 40-person startup’s random requests — the asset and change modules are dead weight and the price per agent is high. A lighter helpdesk handles the same volume for less.

If you’re at 2,000+ employees with regulated change control, ServiceNow or Jira Service Management have deeper compliance workflows. Freshservice is strongest at 100–2,000 users.

Quick Summary

  • Freshservice = IT helpdesk + assets + change management; setup takes about one working day.
  • Pricing 2026: Starter $19/agent/month up to Enterprise $119; free plan for 5 agents with no assets.
  • Import requesters first, exclude shared mailboxes, then create two groups only.
  • One catalogue item with a manager approval beats ten items with none.
  • Turn off comment notifications for requesters before go-live or they’ll filter you into a folder.