You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
How can we configure Jira Service Management to effectively notify collaborators when their assistance is needed on a support request and allow them to see which requests they've already responded to with an internal comment?
In our JSM project, we have multiple agents handling hundreds of support requests daily. Often, we require the help of collaborators from different teams (such as dispatching, administration, sales, etc.) to investigate and assist with support requests. When an agent needs assistance, they add an internal note addressed to the relevant collaborator team. However, as there are multiple collaborators within a team, we are looking for best practices to:
We would appreciate any guidance or advice on how to configure JSM to meet these requirements and streamline our support process, perhaps also through automation.
Thx,
JJ
Hi @Chiron ,
have you considered creating a linked issue in the project with a collaborator can work on the assistance?
While this could be a potential solution, it may introduce considerable overhead for our current workflow. For each support request, we gather crucial information from our legacy system, and duplicating this data for linked issues may not be ideal.
In many cases, the assistance required from collaborators involves a simple answer to a comment, which helps the support agent address the support request, initiate an investigation with another service, guide the customer, or ask the appropriate questions or clarifications. Given this context, we are still seeking a more streamlined solution that minimizes data duplication and overhead while still allowing for effective collaboration between agents and collaborators.
Many thanks for your suggestion
Chiron
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.