What Tier-1 Support Problems the JSM Virtual Agent Actually Solves?
Jira Service Management’s Virtual Agent targets the repetitive, low-complexity requests that consume the largest share of Tier-1 support capacity. It handles five core problem areas:
Repetitive, low-complexity requests consume the largest share of Tier-1 support capacity — and Virtual Agent handles them automatically.
- Password and MFA resets – resolves credential recovery before it reaches a human agent
- Access and permissions requests – collects details conversationally and escalates only when approvals are required
- Policy and knowledge-base lookups – answers process and how-to questions directly from connected sources like Confluence
- Ticket triage – routes misdirected requests to the correct queue with full context attached
- Status updates – deflects progress-check messages that otherwise consume agent time
When an issue exceeds what the virtual agent can resolve, it escalates to a human agent with the full conversation history attached. However, surfacing a knowledge base article and handing it to the employee still requires that employee to read it, judge its applicability, and troubleshoot independently, which means many employees give up and submit a ticket anyway — a limitation that separates deflection from true resolution. Adopting ITSM best practices like incident management helps ensure the virtual agent aligns with broader service management goals.
Where the JSM Virtual Agent Runs and How Employees Use It
Because employees work across different tools, the JSM Virtual Agent meets them where they already are rather than forcing a single intake path. It runs across multiple channels:
- Slack – Employees submit requests without leaving work conversations.
- Microsoft Teams – Useful for organizations running Microsoft 365 workflows.
- JSM Customer Portal – Employees chat directly within the service experience.
- Email and web widget – Currently in beta availability.
Regardless of channel, employees type requests in natural language. The agent interprets context, surfaces answers from connected Confluence content, and escalates unresolved issues to human agents with the full conversation attached. Once active, the virtual agent can also be added to other channels beyond the defaults to extend coverage across additional employee touchpoints. The virtual agent also supports all major languages, dynamically translating content from existing knowledge articles so employees receive consistent assistance regardless of the language they use. It is designed with scalability needs in mind to handle increasing request volumes without degrading performance.
How to Set Up the JSM Virtual Agent With Intents and a Knowledge Base
Setting up the JSM Virtual Agent begins with two foundational components: intents and a knowledge base. Intents handle structured, repetitive requests. Effective B2B integration improves data accuracy and streamlines partner communications, which helps the virtual agent operate across systems with real-time visibility.
The knowledge base supports article-driven self-service through Confluence.
To configure intents:
- Navigate to Jira Service Management project settings under the virtual agent area
- Create an intent using a template or build one manually
- Add a display name, description, and confirmation question
- Include at least three training phrases to improve recognition
For knowledge base setup:
- Connect an existing Confluence knowledge base
- Enable AI answers in virtual agent settings
Together, these components reduce human escalations considerably. When a customer sends a message, the virtual service agent first attempts to match existing intents before falling back to AI answers. Rovo can also detect knowledge base gaps and suggest new article topics based on recent ticket trends.
How Much Ticket Deflection Can the JSM Virtual Agent Deliver?
Key factors that influence outcomes include:
- Intent coverage – how many request types the agent handles
- Knowledge quality – whether Confluence articles actually answer common questions
- Channel availability – deploying across Slack, Teams, and the customer portal increases reach
The native virtual service agent requires JSM Premium or Enterprise to activate, meaning teams on Standard must upgrade before any deflection measurement can begin. Admins retain full control over the experience, as intents and AI answers can be deactivated at any time through virtual agent settings. Studies show that well-implemented ITSM practices can deliver over 70% cost savings through process optimization and automation.
How the JSM Virtual Agent Hands Off to Human Support Without Losing Context
One of the strongest arguments for adopting the JSM Virtual Agent is what happens when it cannot solve a problem. Rather than dropping the conversation, it escalates with full context intact.
The handoff includes:
- The complete conversation transcript
- Pre-filled ticket fields based on collected details
- A summary of what was already attempted
The human agent picks up exactly where the AI stopped. No re-entry. No repeated questions. JSM automatically creates the ticket and routes it to the service desk queue. This keeps resolution time lower and prevents customers from explaining their issue twice.
The virtual agent operates 24/7 across support channels, ensuring customers receive instant help outside of business hours without requiring human staffing around the clock. This approach also supports service request management to streamline workflows and improve efficiency.
Atlassian has reported a 50% increase in resolution rate through this automation-driven approach, demonstrating the measurable impact of combining virtual agent deflection with structured human escalation.
