L1/L2 support assistance: classification, history and Jira and Confluence knowledge lookups with references.
RIZUMU / APPLIED AI
Naya
RequestContextSupport
ILLUSTRATIVE FLOW · Support with context
The challenge
In support, understanding the request and finding the relevant knowledge are recurring steps. Access to information also has to respect each person’s role.
The solution
A service desk project that brings together classification, support context, persistent conversations and cited knowledge lookups. Access controls, curation and satisfaction ratings are part of the workflow.
Naya organizes the support conversation around the context of the request. Classification and persistent history help keep information together throughout the interaction, while knowledge lookups can surface references from Jira and Confluence. The project focuses on the first- and second-level support journey.
Support knowledge needs owners and access limits. That is why the feature set includes access policies, curation and satisfaction ratings, alongside the conversation with the assistant. Any adaptation should choose the request types, the authorized sources and how answers will be reviewed before expanding the assistant’s scope.
What the project brings together
Classification and context for L1/L2 support
Jira and Confluence knowledge lookup
References and access control
Curation, history and satisfaction ratings
FROM PROJECT TO OPERATIONS
Use cases
Illustrative scenarios to picture how this work can be applied in a company’s day-to-day operations.
USE CASE 01
Requests missing context
The scenario
An internal support team receives system access requests without enough information to understand the issue and guide the analysis.
How to apply it
Structure the initial conversation with classification and context gathering, keeping the history available for follow-up.
What the team gets
A structured request record, a persistent conversation and references to the knowledge consulted while guiding the user.
USE CASE 02
Knowledge that needs review
The scenario
A support team has procedures in Confluence and tickets in Jira, but needs to review which content should back the answers.
How to apply it
Define the selected sources, their owners and access rules, using curation and interaction ratings to guide adjustments.
What the team gets
A curated support knowledge base and a review routine with sample questions, references and editorial decisions.
GROUP / AI and knowledge
Offers built on Naya Service Desk.
Choose the starting point closest to your challenge. Each offer proposes a scope of work based on the experience of this project.
Naya Service Desk01
Support triage
Who it’s for Service desks that need better context on incoming requests.
Design the initial conversation for one category of tickets, with the classification and information the support team needs to understand the request and carry the case forward.
Proposed deliverables
Request categories and context fields per ticket
Conversational flow with history and continuity across the interaction
We can combine offers and adapt the deliverables. Data, integrations, acceptance criteria, timeline and investment are defined in the proposal for your company.