Jira Service Management is now more powerful than ever as part of Service Collection. Unlock exceptional service experiences with Rovo, Assets, and our new Customer Service Management app.Try it now
Service request process: How to submit, manage & streamline requests
Key Takeaways
The service request process ensures each service request goes through a standard workflow from submission to resolution
Service request types show users which services they can request through a service request management portal
Common service request process problems include confusing request types, limited visibility into requests, and slow/inconsistent routing
Jira Service Management helps streamline the service request process with features like portals, request types, and forms
Service requests should make it easier to get help, not create more confusion. But when request types are unclear, or intake happens across too many channels, employees can get stuck waiting while service teams spend time chasing down details.
A structured service request process helps teams submit, manage, and resolve routine requests more efficiently. This guide explains how the service request process works, how to submit a service request, and how to streamline service request management.
What is a service request process?
A service request process is the step-by-step workflow teams use to handle routine service requests from submission through completion. Service requests are usually planned, non-urgent requests for things like access to a program, equipment, information, or support.
The service request process isn’t as simple as filling out a form. Service requests go through several stages in an IT service portal, from submission and validation to approval and fulfillment.
Unlike conversational ticketing, which allows users to submit and discuss requests in real time, standard service requests typically move through a more structured workflow.
The main stages of a service request process
Understanding the stages of a service request process helps you get a better idea of how requests move from submission to resolution. Here’s a quick breakdown of each stage.
Stage | What happens | Why it matters |
Submission | The requester submits a request through a portal, help center, or form. | Standardizes intake and captures key details upfront. |
Validation | The request is checked for completeness, accuracy, and eligibility. | Reduces delays and prevents incomplete requests from moving forward. |
Categorization and routing | The request is assigned to the right team, queue, or workflow. | Helps the request reach the right people faster. |
Approval | If needed, the request is sent to the appropriate approver. | Adds oversight for cost, security, or compliance-related requests. |
Fulfillment | The assigned team completes the requested work. | Delivers the service the requester needs. |
Verification | The requester or team confirms the request was completed correctly. | Helps ensure quality and satisfaction before closing. |
Closure | The request is closed and recorded. | Supports reporting and future process improvements. |
Why is a clear service request process important?
A clear service request process benefits everyone involved. Here’s why a clear service request process is essential when building a service desk:
Clarifies where to submit requests and get help. When employees know exactly where to go, they don't waste time searching through Slack channels, emails, or outdated wikis trying to figure out how to ask for something. A single, well-defined entry point reduces confusion and gets requests into the right hands faster.
Improves intake quality. Structured request forms capture the right information upfront, like priority, category, and relevant details. This means service teams get what they need to act on a request without having to guess or ask follow-up questions.
Reduces back-and-forth and manual triage. When requests arrive with complete information and route to the correct team automatically, there's less time spent clarifying requirements or manually reassigning tickets. Teams can start working on requests sooner instead of sorting through them.
Supports approvals and handoffs. Many requests require sign-off from a manager, budget holder, or security team before work can begin. A defined process builds these approval steps directly into the workflow so nothing stalls waiting for someone to notice an email.
Improves request visibility and tracking during every stage. Both the requester and the service team can see where a request stands at any point, from submission through completion. This eliminates status-check messages and builds trust that requests won't disappear into a queue.
Creates a more consistent experience for everyone. Whether someone is requesting software access, new equipment, or a workspace change, the process feels the same. This predictability makes it easier for employees to get help and easier for service teams to deliver it reliably.
How to submit a service request in Jira Service Management
Submitting a service request in Jira Service Management (JSM) starts in the portal, where users can choose the right request type and provide the details the service team needs.
Step 1. Open the Jira Service Management portal or help center
Users start in the Jira Service Management portal or help center, where available request options are organized in a service catalog. This catalog clearly shows users which types of requests they can make.
You can use portal groups to organize request options into clearer categories, making it easier for users to select the right request type.
Step 2. Select the right request type
From the Jira Service Management help center, users can choose a request type such as “Get IT help” or “Request a new account”. Request types are the visible submission options users can see in the portal. They guide users to the correct form so they can get the right help faster.
The list of request types will vary depending on the types of services you offer. Clear descriptions and organized categories help users find the right request type faster.
Step 3. Complete the request form
When users select a request type, a tailored request form opens. These request forms are designed to make sure users are providing all the necessary details to get the help they need.
Teams can customize request forms by adding, removing, and rearranging fields, so the information requested can vary depending on the type of request. Some examples of fields in a request form include:
Access level
Device type
Start date
Business justification
Step 4. Submit the request
Once the user has completed the request form, they can submit the request through the Jira Service Management portal. After a request has been submitted, it’s added as a work item in Jira Service Management.
Teams can review service items in Jira and assign them to the appropriate team members to resolve the request.
Step 5. Follow status updates and respond to follow-up questions
After submitting a request, the user can also monitor the request and provide more information if the team needs it.
The Jira Service Management portal features built-in visibility and status tracking, making it easy for users and teams to keep track of service requests in real time. This helps users monitor the status of their requests and ensures every request is resolved in a timely manner.
Step 6. The service team triages the request
After submission, the request moves into the appropriate queue, where agents can review, prioritize, and assign it.
Tips for managing service requests
JSM helps teams manage submitted requests, fulfill work efficiently, and meet SLAs. Here’s how you can manage service requests:
Reviewing incoming requests: Incoming requests become work items in Jira Service Management, so teams can review them as soon as they’re submitted.
Triaging in queues: Service requests are sent to queues for triage and assignment to the appropriate team, whether that’s the IT team or your HR service center.
Handling approvals: Jira makes it easy for teams to collect and review request details with custom intake forms, so you can quickly approve incoming requests and keep them moving through fulfillment.
Updating request status: Teams can update the service request status directly from Jira Service Management, and users can see these status updates in real time.
Resolving and closing requests: Once a request has been fulfilled, it can be closed in Jira Service Management. When a request is closed, its status will also be updated for users.
Common service request process examples
The following examples show how common service requests move from submission to routing, fulfillment, and closure.
Example 1: Software access
A user needs access to a specific software tool to complete their work. They start in the Jira Service Management portal and select the “Software access” service request option.
From there, they complete a form with key details. These may include the software they need, device type, requested access level, and business justification. Collecting these details upfront helps the service team confirm eligibility and avoid extra follow-up.
Once submitted, the request becomes a work item in Jira Service Management. The user can monitor the request in the portal, respond to follow-up questions, and see when the request status changes.
On the agent side, the request moves into the appropriate queue for review. The service team verifies the request, grants software access, and closes the request once access is complete.
Example 2: Onboarding support
A manager or new employee needs help completing part of the onboarding process. They start in the Jira Service Management portal and choose the “Onboarding support” request type.
The request form may ask for the employee’s start date, department, equipment needs, and system access requirements. It may also ask which part of the onboarding workflow needs support. This gives the right team the context they need to coordinate the request.
After submission, the request becomes a work item in Jira Service Management, where the user can track progress in the portal. Because onboarding requests may involve multiple steps, the request may be routed to HR, IT, facilities, or another internal service team.
The assigned team reviews the request, completes the necessary onboarding support, and closes the request once the work is finished.
Common problems in the service request process
There are a few common obstacles in the service request process, including:
Poorly named or confusing request types make it difficult for users to select the right request type
Limited visibility into request types can cause confusion for users
Slow or inconsistent routing results in longer service request resolution times
Requests coming in through too many channels can make it difficult to prioritize and resolve requests
Build a better service request process
The service request process ensures users receive the support they need in a timely manner. A stronger service request process depends on clear intake, structured management, and continuous refinement.
Jira Service Management supports clear intake, structured management, and continuous refinement with portals, request types, forms, queues, and customizable approval workflows.