The Freshservice service catalogue is one of the highest-value investments an ANZ IT team can make. And one of the most consistently underdelivered parts of an implementation. Most teams configure a catalogue in week four, name items in IT language, and then wonder why self-service adoption sits at 4% six months later.
This guide covers how to build a service catalogue users actually use. From design principles through to step-by-step configuration in Freshservice.
TL;DR
- A Freshservice service catalogue succeeds or fails on design, not the platform. Low adoption is almost always a design problem.
- Start with the top 20 to 35 contact reasons by volume. Name items in plain user language, not IT language.
- Keep to four to eight categories, and only the form fields IT genuinely needs.
- Remove approval from routine, low-risk items like password resets. Reserve it for cost, elevated access or sensitive systems.
- Test with real end users before go-live, then drive adoption. Target 25 to 40% within 90 days.
Why Most Service Catalogues Fail
Built for IT, not users. Items named and structured from an IT view: “Submit a Hardware Request”, “Request Application Access via IAM”. Not how a non-technical user thinks. When users cannot find what they need in two clicks, they call IT instead.
Too many items, not enough structure. A catalogue with 80 items and no clear categories is worse than one with 20 and good organisation. Users facing a wall of options choose none.
No fulfilment design behind the items. Creating a service item takes 10 minutes. Designing what happens after submission takes longer. That design is often skipped. A service item with no workflow behind it creates a request that sits in a queue until someone notices it.
Step 1: Design Before You Configure
Identify Your Top Contact Reasons
Pull the last 12 months of ticket data. Identify the top 20 to 30 contact reasons by volume. These become your Phase 1 service catalogue items. Do not start with what IT thinks users should request. Start with what users are actually requesting.
Common top contact reasons for ANZ mid-market teams: password reset, new user setup, software access request, hardware request, VPN access, email account setup, printer access, software installation, account unlock and building access. Every one should have a catalogue item before anything else is added.
Design the Fulfilment Process for Each Item
For each item, answer these questions before touching Freshservice:
- What information does IT need to fulfil this? (These become your form fields.)
- Does this require approval? If yes, who approves and what is the timeout?
- Which agent group fulfils it?
- What are the fulfilment steps? (These become Workflow Automator tasks.)
- What is the realistic fulfilment time? (This becomes your SLA target.)
This work takes time. It is also what makes the difference between a catalogue that works and one that looks complete but fails in operation.
Step 2: Plan Your Category Structure
Structure the catalogue from the user’s view. Not the IT team’s org chart. Four to eight top-level categories. Here is a structure that works for most ANZ mid-market organisations:
| Category | What It Covers | Example Items |
|---|---|---|
| Account and Access | Passwords, system access, accounts | Password reset, account unlock, VPN, building access |
| Hardware and Equipment | Devices, peripherals, repairs | New laptop, monitor, mobile device, equipment repair |
| Software and Applications | Software, licensing, application support | Software install, app access, licence request |
| New Starters and Leavers | Onboarding and offboarding | New employee setup, offboarding, contractor access |
| Communication and Collaboration | Email, Teams, phone | New email account, Teams channel, shared mailbox |
| Facilities and Office | Office IT requests | Printer access, meeting room AV, desk setup |
| IT Support and Incidents | Issues that do not fit a structured type | General IT issue, app not working, slow performance |
Maximum eight top-level categories. Users facing more than eight start to feel overwhelmed. Test sub-categories with real users before adding them.
Step 3: Configure in Freshservice
Create Your Categories
Admin, then Service Catalog. Create top-level categories first. Write user-facing descriptions. “Account and Access: Need help with your password, system access or account?” beats “Identity and Access Management Requests.” Set display order so highest-volume categories appear first.
Create Your Service Items
Each item has five core components.
Item name. Plain language. “Reset My Password” beats “Password Reset Request”. “Get a New Laptop” beats “Submit a Hardware Procurement Request”. Test names with a non-technical colleague. If they hesitate, rename it.
Description. Clear, brief. Include the fulfilment timeframe. “Request access to a new application. We will set you up within 2 business days after manager approval.” Sets expectations and reduces follow-up queries.
Form fields. Only fields IT genuinely needs. A password reset needs an email address. It does not need a department, cost centre and justification paragraph. Start with the minimum. Add fields only when experience shows they are needed.
Approval workflow. Single-level manager approval with a 24-hour timeout covers most items. Not every item needs approval. Password resets and standard software installs should flow directly to the agent queue.
Fulfilment assignment. Set the agent group that receives this item. Set the SLA target for fulfilment. Not just response. Fulfilment.
Add Workflow Automator Rules
Configure automations for service items:
- Auto-assignment: Route to the correct agent group based on item category
- Approval notification: Notify approver with a clear action link and request details in the message body
- Requester acknowledgement: Confirm receipt, who has it and the expected timeframe
- SLA escalation: Alert the team lead when a service item is approaching fulfilment SLA
Configure the Portal Layout
Brand the portal with your logo, colours and name. A portal that looks generic will be used less. Set the welcome message to something friendly: “Welcome to IT Support. Find what you need below or search for your request.” Enable search and verify it surfaces the right results for common terms: “password”, “laptop”, “new phone”, “access”, “printer”, “Teams”.
Step 4: Test With Real Users
Test with five to ten end users who have not been involved in the build. Give each three tasks: find and submit a password reset, a software access request and a hardware request. Observe without helping. Note where they hesitate and what they cannot find.
This typically surfaces three to five changes that significantly improve adoption. A category users interpret differently. An item name users search for under a different term. A form field users do not know how to answer. Cheap to fix before go-live. Expensive after.
Step 5: Launch and Drive Adoption
Communicate to all staff. Plain-language announcement at least one week before go-live. What the portal is, where to find it, why it is faster than emailing IT. Repeat in the intranet, onboarding materials and all-staff channels.
Embed the portal link everywhere. IT email auto-reply. Email signatures. Intranet. Remove all friction between a user having a request and knowing where to go.
Train agents to guide users. When users call or email, resolve the request first. Then guide them through the portal item. This builds the habit one interaction at a time.
Enable Teams or Slack integration. Meeting users where they already are is the fastest path to adoption. Users who never visit the portal directly will use it when it surfaces inside Teams.
Measure adoption weekly. Target 25 to 40% portal adoption within 90 days. Below 15% at 60 days means the portal design or promotion needs review.
Want help? Book a diagnostic call with KlickFlow and we will review your catalogue and identify the highest-impact improvements.
Best Practices
| Best Practice | Why It Matters |
|---|---|
| Name items in user language, not IT language | Users who cannot find what they need in 10 seconds abandon the portal |
| Limit form fields to what is genuinely needed | Every unnecessary field reduces form completion rates |
| Set realistic SLA targets per item | Overpromising and underdelivering damages trust fast |
| Remove approval from routine, low-risk items | Approval delays on password resets drive users back to email |
| Test with real end users before go-live | Issues obvious to users are invisible to IT staff who built the catalogue |
| Review quarterly | Contact patterns change; keep the catalogue relevant |
| Add items as new contact types emerge | A contact with no catalogue item defaults to unstructured email |
| Enable Teams or Slack integration | Fastest path to adoption |
What Good Looks Like
| Element | Poor | Good |
|---|---|---|
| Item name | Submit Application Access Request via IAM Portal | Get Access to a New Application |
| Description | Use this form to request access to business applications managed by IT. | Need access to a new app? Submit this and we will set you up within 2 business days after manager approval. |
| Form fields | Name, Employee ID, Department, Cost Centre, Application, Justification, Urgency, Approver Name, Approver Email, Comments | Which app do you need? (dropdown), Your manager’s name and email |
| Approval | IT manager, department head, CISO | Direct manager, 24-hour timeout |
| SLA | 4 hours | 2 business days |
| Fulfilment steps | None configured | 1. Approval received 2. Provision in AD 3. Confirm with requester 4. Close ticket |
What KlickFlow Sees
A 450-person financial services firm in Brisbane came to us six months after their Freshservice go-live with 6% self-service adoption. The catalogue had 94 items across 12 categories. Items named in IT department terminology. The software access form had 11 fields. Every item required approval including password resets. The portal had never been tested with an end user.
KlickFlow ran a four-week redesign. Item library reduced to 28 items across 6 categories. All renamed using the language from the contact reason analysis. Form fields capped at four for routine requests. Approval removed from 14 items where it added no real risk control. Rebuilt catalogue tested with eight end users before relaunch. Five of the six categories were renamed based on that testing.
Within 60 days: self-service portal adoption reached 31%. Same platform. Completely different design.
Frequently Asked Questions
20 to 35 items in Phase 1 is the right scope for most ANZ mid-market teams. This covers the top contact reasons that make up 80% of volume. Start focused. Measure adoption. Add items where gaps emerge.
No. Approval should reflect genuine risk. Password resets, standard software installs, peripheral requests and account unlocks carry no meaningful risk. Adding approval to these drives users back to email. Reserve approval for items involving cost, elevated access or sensitive systems.
Quarterly review. Check: are there high-volume email contacts with no catalogue item? Are any items getting zero submissions? Have approval workflows changed? Are any SLA targets being missed? A catalogue reviewed quarterly stays relevant. One that is never reviewed becomes outdated within 12 months.
Yes. Freshservice’s Workspaces feature allows separate catalogues for HR, Finance and Facilities within the same platform. Each department gets its own catalogue, agents, SLAs and reporting. Available on Freshservice Pro without additional licensing.
What to Do Next
If your catalogue exists but adoption is low, the problem is almost always in the design. Not the platform.
Book a diagnostic call with KlickFlow. We will review your structure, item naming, form fields, approval workflows and portal layout. And give you a prioritised improvement plan your team can implement within 30 days. No obligation.