Design a service portal around the request

Design a service portal around the request

Design a service portal around the request

BRASIKO • Practical Operations Guides

What to clarify before implementing a Jira Service Management portal for customers, suppliers, or internal teams.

A service portal should help people submit the right information and understand what happens next. The design work starts with the request and its lifecycle. List the services you intend to offer, who can request them, who owns delivery, and which decisions or approvals are required.

Make intake understandable

Group request types in language the requester recognizes. For each type, identify the information an agent genuinely needs to begin work. Keep optional questions separate from required ones and explain unusual fields. Review draft forms with both requesters and the team that will handle the work; their perspectives often reveal different sources of confusion.

Define ownership and exceptions

Agree on assignment rules, escalation paths, response expectations, and what each status means. Decide how a request returns to the requester for clarification and who follows up when it stalls. Document cases that need specialist review rather than assuming one workflow will fit every situation.

Treat access and sensitive requests separately

For supplier or customer requests, define who is allowed to see each record and how access is reviewed. A portal login should be one part of the process. Sensitive actions, including banking changes, also need a separately designed verification and approval process. Avoid putting sensitive information in a general enquiry form.

Before implementation, prepare a service catalogue, example requests, workflow rules, access requirements, and acceptance criteria. Test ordinary and exception cases with real users. BRASIKO can help translate these requirements into a practical Jira Service Management implementation and supporting operating procedures.

Discuss this with BRASIKO