How to Create a Service Catalog in Freshservice?
Quick Summary
A service catalog is the front door to your IT department, and getting it right makes the difference between a help desk that feels chaotic and one that feels effortless. Freshservice ITSM Software gives teams a structured way to list, organize, and publish every service employees can request, from a new laptop to VPN access. In this article, you will learn how to plan, build, configure, and maintain a service catalog inside Freshservice, step by step, so your users always know what to ask for and how to get it.
What Is a Service Catalog, and Why Does It Matter?
A service catalog is an organized list of services that a department, usually IT, makes available to employees or customers. Instead of sending random emails or Slack messages asking for help, users browse a portal, pick what they need, and submit a request through a standard form. As a result, every request arrives with the same details, which speeds up fulfillment and cuts down on back-and-forth clarification.
Freshservice turns this concept into a working feature rather than just a document. Consequently, administrators can build categories, add service items, attach forms, and control who sees what, all from one admin panel. Because the catalog lives inside the same platform that manages tickets, approvals, and assets, every request automatically becomes a trackable ticket.
Why Should Every IT Team Have One?
Without a catalog, requests come in inconsistent formats and get misrouted to the wrong team. With a catalog, however, employees select a predefined item, fill in a short form, and the ticket routes itself correctly. This reduces misclassification and saves agents from asking follow-up questions before they can even start working.
How Do You Plan Your Freshservice Service Catalog?
Before opening the admin panel, it helps to plan the catalog on paper first. Good planning prevents a messy, oversized catalog that confuses users instead of helping them.
Which Stakeholders Should You Involve?
Building a catalog is not a one-person job. Instead, bring together representatives from IT, HR, facilities, and any other department that plans to publish services. Since each team understands its own processes best, their input ensures the final catalog reflects real workflows rather than guesswork.
Once the team is assembled, assign clear roles. For instance:
- Service Catalog Admin – owns the design and configuration of every service item
- Approvers – reviewers who sign off on specific requests, such as software purchases
- Department Leads – provide the list of services their team offers and the details each request needs
How Do You Map Out Service Categories?
After the team is in place, list every service your organization offers, then group similar items together. For example, “Hardware,” “Software,” “Access Management,” and “HR Services” might become your top-level categories. Afterward, break each category into subcategories where needed, since Freshservice supports up to three levels of hierarchy.
A simple planning table often works better than a long list:
| Category | Subcategory | Example Service Items |
|---|---|---|
| Hardware | Laptops & Desktops | New Laptop Request, Monitor Request |
| Software | Licenses | Adobe License, Microsoft 365 Access |
| Access Management | Accounts | VPN Access, New User Account |
| HR Services | Onboarding | Equipment for New Hire, Badge Request |
How Do You Create Service Categories in Freshservice?
With a plan in hand, you can move into Freshservice itself. Categories act as containers that keep the catalog tidy, so it makes sense to build these first, before adding individual items.
To create a category, follow these steps:
- Go to Admin > {Workspace Name} > Service Management > Service Catalog.
- Click Create service category, then choose whether it is a root category or a subcategory.
- If creating a subcategory, select the relevant parent from the Select parent dropdown.
- Enter a clear category name and a short description.
- Click Create to save it.
Because the Service Catalog supports up to three levels in the hierarchy, you can nest subcategories under a parent category to keep related items grouped logically. This structure reduces ticket misclassification and simplifies complex catalog management for administrators, meeting enterprise-grade industry standards, which matters as your organization scales.
Should You Start With One Department or the Whole Company?
Many teams try to build an entire enterprise catalog on day one, but a phased rollout usually works better. Start with a single department, gather feedback, then extend the same approach to other teams once the model proves successful. This way, mistakes stay small and easy to fix rather than affecting the whole organization at once.
How Do You Add Service Items to Your Catalog?
Once categories exist, it is time to populate them with individual services. Each service item represents something a user can actually request, such as a new monitor or software license.
What Steps Are Needed to Add a Service Item?
To add a new item, go to the same Service Catalog section, then:
- Click the Create dropdown in the top-right corner and select Service Item, or click the Plus icon inside a specific category.
- Enter a name in the Item Name field that clearly describes the service.
- Select a relevant category from the Service Category dropdown.
- Enter a short description and detailed description in the respective fields.
- Enter the cost in USD in the Cost field, if applicable.
- If required, select the Visible in portal checkbox so end users can see it.
- Enter the estimated delivery in hours in the Estimated Delivery field so users know what to expect.
How Do You Configure the Service Item Form?
Beyond the basic details, Freshservice lets you build a custom request form for each item. Because different services need different information, this step matters more than it might first appear. A laptop request, for example, might need a delivery location, while a software request might need a manager’s approval.
You can also add content fields to incident and service item forms, creating sections with content headers and relevant links, which helps users understand exactly what they are requesting before they submit. In addition, Freshservice allows you to search for and include related service items that can be requested alongside the main service, which streamlines the process for users who need multiple things at once, since this eliminates the need for customers to create multiple requests for different service items.
Should Some Items Be Bundled Together?
Yes, whenever items are commonly requested together. For instance, a new hire request might automatically include a laptop, a badge, and a software bundle. Freshservice lets admins mark certain additional items as mandatory and delete any item that no longer applies, which keeps bundles flexible as needs change.
How Do You Manage Visibility and Access for Different Users?
Not every service should be visible to everyone. A specialized software license, for example, might only apply to the design team, while a facilities request might only apply to a specific office location.
How Do You Restrict Items to Specific Groups?
Freshservice handles this through requester groups. To restrict a service item:
- Create a requester group by going to the group settings and clicking Create New, then selecting Requester Group.
- Add members either manually or through rules based on fields like department, location, or job title.
- Open the service item settings, then click the Agent Visibility dropdown.
- Select the groups the item should be available to, then click Save.
Because user groups can be created based on the location, language, time zone, reporting manager, and other dropdown fields of a user, visibility rules can get quite specific. For example, a service item such as an Arabic keyboard could be made available only to people whose language is Arabic and who are located in Dubai, and this setup happens automatically once the rules are defined.
What Happens as the Company Grows?
As your organization scales, manually assigning every new hire to the right group becomes unrealistic. Fortunately, Freshservice handles this automatically, since new requesters are added to the relevant groups based on their department and job title once the rules exist. Therefore, admins set the logic once and let the system apply it going forward.
How Do You Test and Publish Your Service Catalog?
Before rolling the catalog out to the entire company, testing prevents avoidable frustration. A catalog full of broken links or confusing categories will discourage adoption fast, no matter how well it was designed on paper.
Consider testing with a small pilot group first. Ask them to submit a few requests, then review:
- Whether forms capture all the necessary information
- Whether categories make logical sense to someone outside the admin team
- Whether requests route to the correct approvers and fulfillment teams
Once the pilot group confirms everything works as intended, announce the catalog to the wider organization. A short internal communication explaining where to find the portal and how to use it goes a long way toward encouraging adoption, especially for employees used to requesting things through email or chat.
How Do You Maintain and Improve the Catalog Over Time?
A service catalog is never really “finished.” Instead, it should evolve alongside the business, since needs, tools, and teams change constantly.
Set a regular review cadence, whether monthly or quarterly, to check which services are used often and which sit untouched. Remove outdated items, update descriptions that no longer match reality, and add new services as departments request them. Additionally, pay attention to user feedback, since employees often notice friction points that admins miss, such as confusing wording or missing options in a dropdown field.
Conclusion
Building a service catalog takes planning, but Freshservice makes the execution far simpler than doing it manually. By involving the right stakeholders, mapping out categories before touching the software, and configuring visibility rules carefully, you create a catalog that genuinely serves your organization rather than adding another layer of complexity. Once published, treat the Freshservice catalog as a living resource: test it, gather feedback, and update it regularly so it keeps pace with your company’s changing needs. Done well, a Freshservice service catalog turns scattered requests into a smooth, predictable process for both end users and the IT team supporting them.
Frequently Asked Questions
Freshservice supports up to three levels in the category hierarchy, allowing you to organize a root category, a subcategory, and further nested subcategories underneath it. This structure works well for larger organizations with many departments and service types.
Yes. Every workspace can maintain its own list of service categories, subcategories, and items, which means different departments or business units can manage their own sections of the catalog independently while still operating within the same overall system.
You can restrict visibility by creating a requester group and assigning it to a service item’s Agent Visibility settings. Once configured, only members of that group, whether defined by department, location, or another field, can see and request that specific item.
