Your IT team isn't running a service desk. They're running an unindexed DM queue that occasionally produces tickets. Same for HR. Same for Finance. Same, probably, for whichever poor soul in Legal keeps getting pinged about NDAs at 4:47 PM on Fridays.

The work is getting done. The data isn't getting captured. And the people doing the helping have no way to prove how much of their week is spent helping.

There's a fix, and it's been quietly maturing inside the Atlassian stack for years: run Jira Service Management directly inside Slack and Microsoft Teams. With the Team '26 Rovo updates layered on top, this isn't just possible — it's the way you should be thinking about every internal service team in your organization.

The portal problem nobody wants to admit

Every IT director has the same story. They roll out a beautiful self-service portal. They send a launch email. They run a lunch-and-learn. And six months later, 60% of requests still arrive as DMs to whoever the requester knows personally on the IT team.

This isn't a training problem. It's a physics problem. People file requests where they already are. They are in Slack or Teams all day. They are not in your portal. They will never be in your portal.

You can fight that. Or you can route around it.

What “JSM in Slack/Teams” actually does in 2026

The Atlassian-native integrations for Slack and Microsoft Teams have quietly become genuinely capable. The current state of play:

• Raise requests from inside a conversation. Slash command, message action, or emoji reaction. A guided form appears inline. No portal hop required.
• Turn any message into a ticket. Someone DMed the wrong person? Right-click the message, “Create request.” The conversation context travels with it.
• Approvals in chat. Managers approve software access, time off, hardware requests, and contract reviews — all from Slack or Teams without ever opening Jira.
• Two-way sync. Agent comments show up in chat. Requester replies update the ticket. The conversation and the ticket are the same artifact.
• Channel-as-service-desk. Run an active triage channel where your team chats and works publicly — and any message can become a tracked, SLA-bound request without breaking flow.
• Rovo virtual agent. This is the bit that changed everything in the last twelve months. The virtual agent answers from your knowledge base, gathers missing info conversationally, triages priority, and only escalates to a human when it can't resolve. Powered by the Teamwork Graph, it sees the full context across Jira, Confluence, and connected sources — which is why answer quality is roughly 44% better than first-generation virtual agents.

This isn't just for IT

The most common mistake we see: organizations buy JSM, deploy it for IT, and stop. Internal JSM is a service-team chassis, not an IT tool. The same Slack/Teams workflow runs equally well for:

• HR — onboarding checklists, time off, benefits questions, “where's the holiday calendar?”
• Finance — expense help, PO approvals, budget questions
• Legal — NDA requests, contract reviews, policy lookups
• Marketing and Creative — asset requests, brand approvals, design queue intake
• Facilities and Workplace — desk reservations, building access, equipment

Every one of those teams is currently running an invisible queue out of DMs and channel pings. Every one of them deserves an SLA, a knowledge base, and a virtual agent doing the first round of triage.

The metrics that actually move

When this rollout is done well, four numbers shift in the same quarter:

• Time to first response. Drops sharply, because the virtual agent responds in seconds and humans only see what needs them.
• Volume of human-touched tickets. Common JSM customer ranges show 30–50% of repetitive requests resolved entirely by the virtual agent in the first 90 days.
• Hidden work, surfaced. Work that was happening in DMs now shows up in the data. Sometimes this is uncomfortable. It's also exactly what your leadership team needs to make staffing decisions that aren't guesses.
• Employee satisfaction. People don't have to learn another tool. They get answers faster. The two reliably move together.

The gotchas worth flagging before you commit

Three pitfalls we routinely steer clients around:

1. Don't run dual intake. If both Slack DMs and the JSM portal are “official” intake, you've added a tool, not replaced one. Pick the chat-first surface, repurpose the portal as the agent's interface, and communicate the change clearly. The transition needs executive air cover for the first month.
2. Train the virtual agent on what's actually true today. The knowledge base needs to reflect how the company actually operates right now — not the SOP that someone documented in 2021 and nobody has updated since. A virtual agent that confidently delivers stale answers is worse than no virtual agent. Audit and refresh the knowledge base before you flip the switch.
3. Permissions vary by service team. Default visibility settings that work for IT will not work for HR or Legal. Channel-based intake is great for IT triage and a privacy disaster for benefits questions. Plan request-type permissions and notification scopes before you launch, not after the first complaint.

Why this matters more in 2026 than it did in 2024

The Team '26 announcements made it clear where Atlassian is pointing JSM. The Rovo virtual agent is now context-aware across the entire Teamwork Graph. Third-party agents (Cursor, Copilot, Claude, Gemini) can pull JSM context through the MCP server. Rovo Studio lets non-developers build automations that tie incoming requests to downstream actions across Confluence, Jira, and connected tools.

Translation: the chat-based service desk is no longer just a convenience. It's the surface where AI gets to be genuinely useful to your internal teams. The organizations that wire this up in 2026 are going to have a meaningfully different cost-to-serve curve than the ones still defending their portal a year from now.

This is the kind of project where the tooling is mature, the integrations are first-party, and the gating factor is design and rollout discipline. As an Atlassian Solution Partner, Avaratak Consulting helps internal service teams stand up Slack and Teams-based JSM with the virtual agent properly tuned, the request types properly scoped, and the change management properly handled — so the rollout actually gets used. If your team is one DM avalanche away from burnout, find us at avaratak.com.