Jira Service Management is the Atlassian service desk built on Jira. Teams set up service projects with request types, a customer portal, queues and SLAs, and many use Assets to track the things requests are about. IT teams started with it; facilities, HR and operations teams followed. When a facilities request needs a technician, the ticket often has to be retyped into a maintenance system, and the requester waits without news until someone remembers to update it.
With Agentic CMMS, Claude, ChatGPT and other AI agents work across Jira Service Management and your CMMS. Your service desk can triage the queue, create the maintenance work and update every customer without switching between tools.
What your AI agent can do with Jira Service Management
- Work the queue. "Show me the facilities queue, with anything about to breach its SLA at the top."
- Triage by request type. "Which new requests this morning are building repairs and which are cleaning?"
- Reply to customers. "Let the person who reported the broken blind in Room 3.12 know it will be fixed on Thursday."
- Leave internal comments. "Add an internal comment that the contractor needs access to the roof."
- Transition requests. "Move every request about the car park barrier to Waiting for supplier."
- Look up Assets. "Which requests this year were about air handling unit AHU-2?"
- Clean up duplicates. "Find the requests from today that report the same flooded toilet on Floor 4 and link them together."
- Check pending approvals. "Which requests for new office equipment are still waiting for a manager's approval, and for how long?"
- Report on the month. "How many facilities requests did we resolve in October, and which request type took longest?"
Jira Service Management with your other systems
- Turn a building repair request into a work order in UpKeep or MaintainX, and add the work order number to the request.
- Find the right procedure in Confluence and send the first steps to the customer while they wait.
- Link a recurring fault to an engineering issue in Jira when the problem needs a project, not another repair.
- Post new urgent requests to the facilities channel in Slack, each with its location and SLA.
For organisations already on Atlassian
If your company runs on Jira and Confluence, the service portal is where people already go to ask for help. Moving building requests somewhere else would only confuse them. The agent connects the portal to the maintenance side instead, without new forms, another login or a custom integration to maintain.
Each person approves their own agent and chooses read-only or read and write. Owners and admins decide which roles may reply to customers, and every reply, comment and transition appears in the activity log.