Self-service portals that are actually used: Service Request Management in Jira Service Management

A self-service portal is used when it helps the employee faster than an email to IT. This is achieved through three principles: a clear category structure with five to seven top categories, automated approval workflows for requests with cost implications, and knowledge articles that are offered directly in the search flow.

In Jira Service Management we implement this with Request Types, Approvals and the integrated knowledge base in Confluence. The key is to build the portal from the users’ perspective and not as a mirror of the internal IT org chart. A well-designed portal noticeably reduces ticket volume and handling time and can be extended beyond IT to HR, Facility and Legal (Enterprise Service Management, ESM).

As an Atlassian Platinum Solution Partner in Switzerland, Swarmit accompanies the portal design from the category structure to the gradual expansion to other departments.

Why many portals remain unused

The majority of self-service portals that we see in initial assessments with new customers have the same fundamental problem: they are built the way the internal IT team works, not the way an employee thinks. Someone who needs new access to a specialist system doesn’t know whether that belongs under “Identity & Access”, “Application Support” or “User Management”. So they send an email. That bypasses the portal and the efficiency gain is lost.

A good portal reverses the perspective. It doesn’t ask “which IT team is responsible?”, but “what do you want to achieve?”. The internal mapping then happens in the background, either via automation rules or, in more complex cases, via a Rovo agent that handles the classification.

Categories and forms: less is more

The portal structure is a design decision, not a technical one. We recommend five to seven top categories, each of which hides concrete Request Types. The top categories are oriented around verbs and goals: “Get access”, “Order hardware”, “Report an incident”, “Request software”.

Two rules have proven effective:

First: Do not ask for more fields than necessary. Forms should remain as lean as possible, with conditional fields that only appear when they are truly needed.

Second: Keep search working. If an employee types “VPN” into the search bar, the VPN request must appear as the first result. This includes sensible names for the Request Types (not “IAM-VPN-P002”, but “Request VPN access”) and appropriate synonyms in the title or description.

Knowledge articles as ticket prevention

The most efficient ticket is the one that never arises. JSM connects the portal directly to a Confluence-based knowledge base. When an employee opens a ticket and types “VPN not working”, the portal suggests relevant articles before the ticket is even submitted.

For this to work, the articles need three properties:

• They answer the question in the first two sentences. If someone has to read through three paragraphs of backstory, they give up.
• They are up to date. An article that refers to a software version from two years ago does more harm than no article.
• They are linked to the appropriate Request Types. Without this link, the portal won’t find them.

We recommend a simple maintenance rhythm: for every closed ticket that appears more than, for example, three times a month, check whether a knowledge article exists. If not, one is created. This rule can be automated in JSM as a task.

Jira Service Management beyond IT

Once the IT portal is established, the second step follows in many organizations: Enterprise Service Management. HR uses the same platform for onboarding requests, Facility for access cards and repair reports, Legal for contract reviews. From the employees’ perspective, there is then exactly one place for all internal requests.

Technically, the step in JSM is manageable: new projects, new portal structure, new workflows. The actual effort lies in the process work with the respective departments. We recommend starting with one department and then transferring the experience to the next.

Frequently asked questions

How do you convince employees to use the portal instead of email?

Two factors work reliably. First: the portal must objectively be faster than email – shorter response times, clearer status information, automatic notifications. Second: the classic email route is gradually made less attractive (for example through auto-replies referring to the portal). Banning by mandate rarely works; rerouting through a better experience almost always does.

Can Jira Service Management also be used for HR or Facility requests?

Yes. JSM is designed at platform level for Enterprise Service Management. Each department can run its own project with its own forms, workflows and approval paths. From the users’ perspective, it remains a unified portal.

How does Jira Service Management handle Swiss data protection requirements?

Atlassian Cloud supports data residency in Switzerland. For HR and personnel data, which are typically particularly sensitive, this is a central criterion. The configuration of data residency is its own checkpoint in the ESM rollout, which we coordinate with the organization’s data protection officers.

Next steps

For organizations that want to assess their existing portal, we offer a portal review: we examine the current structure, the most-used Request Types and the actual usage statistics. The result is a priority list with three to five improvements that can be implemented in the short term.

Would you like us to review your portal? Contact us for a no-obligation conversation.