A customer calls support. The agent knows what to do, except the CRM won’t load properly, or their permissions have vanished, or the knowledge base is serving yesterday’s answer while the customer sits there wondering why something simple is taking 15 minutes.
Internally, that’s an IT problem. To the customer, it’s just bad service.
Ty Givens put it perfectly during our May resilience roundtable:
“There are two questions. Can the customers get help? And can the agents do their job? Those are the two things that actually make an organization resilient.”
That disconnect has bothered us for a while. I’ve kept thinking about it since our Opsgenie coverage. Now Workday Rising has given us Sana Concierge, an HR-and-IT agent designed to deal with requests before employees need to open tickets. Atlassian has expanded Service Collection, while Salesforce's Paige can work above third-party ITSM systems. The employee-service front door is getting rather crowded.
ServiceNow’s added another talking point. Flow, announced October 1, is designed to bring IT support into Slack and Teams, while its October 6 AI Workflow Factory gives companies a governed way to build and run AI workflows. The service front door is getting easier to separate from the machinery underneath it.
That’s a lot of movement around employee service management in a very short window.
But does ITSM and customer service convergence really mean dumping every request into one queue? Or should we be asking why the same technical problem still needs so many different teams and systems to put it right?
TL;DR
-
Workday wants to deal with IT requests before anybody opens a ticket. Rising introduced Sana Concierge, bringing HR and IT work into the new Workday Home. Concierge is only in early access, with general availability planned for Q1 2027. I'd want to see actual IT support results before calling this a serious challenge to established ITSM vendors.
-
Atlassian's help desk ambitions are getting harder to ignore. Team ’26 Europe brought proactive employee support, Customer Service Management and Rovo closer together. Meanwhile, the Opsgenie migration keeps pulling more operational work into Jira Service Management. That's a lot more responsibility for what used to be an IT ticketing platform.
-
Salesforce wants to own the front door, even when someone else owns the plumbing. Paige now spans IT and HR support and can work above third-party ITSM platforms. Clever, certainly. But when work moves between systems, who's accountable if the customer or employee still doesn't get an answer?
-
ServiceNow would quite like to keep control of what happens behind the scenes. Flow is bringing IT help into Slack and Teams, while Action Fabric lets external agents kick off workflows without bypassing ServiceNow's approvals and controls. That's useful if you want employees to get help wherever they're working. I'd still want to know who's responsible when something goes wrong, particularly if several different systems have had a hand in it.
Why Are ITSM and Customer Service Converging Now?
The case for ITSM and customer service convergence gets pretty hard to ignore once you stop treating an agent’s working environment as an internal concern.
If authentication fails or the CRM becomes unusable, the employee has an IT incident. The customer waiting for help has a rather different name for it.
We heard another interesting perspective from Fin’s Brian Donohue. His team already uses separate agents for customer support, human-agent assistance, and service operations. How much context should those specialists share as their work overlaps? Surely that's more interesting than giving everyone the same ticket list.
ISG’s September 17 research describes enterprise service management as an emerging “enterprise execution layer,” extending into HR and finance. ISG Partner Andy Miears puts the challenge neatly:
“The defining test for ESM is whether intelligent execution can scale while keeping decisions linked to accountability.”
That accountability bit deserves attention. Riverbed’s October 6 survey found 77% of respondents hesitant to let AI make operational decisions without human approval, while just 17% reported fully unified visibility across their infrastructure.
More automation doesn't necessarily mean less work, either. SolarWinds’ 2026 ITSM survey found 84% said AI met or exceeded ROI expectations, yet 52% reported increased workloads.
One queue might mean fewer handoffs and better context. It could also concentrate failure and authority in fewer places. That's something buyers should be asking about before celebrating another merged service desk.
What Is Workday Rising 2026 Bringing to Employee Service Management?
Workday gave us a much clearer answer at Rising on October 13. Sana is becoming the new Workday Home, and its new Sana Concierge brings HR and IT requests into one employee-service experience.
That's quite a step beyond Workday's May Sana for ITSM announcement. Concierge combines those capabilities with Workday Help and Case Agent, covering onboarding, payroll questions, password resets, and application access. It is designed to resolve requests before someone has to open a ticket.
Chief AI Officer Joel Hellermark put the thinking together at Rising:
“AI is the new UI.”
Workday already knows an employee's role, reporting structure, and approval rules. Why make them explain it all again whenever they need IT support? Workday also plans to bring Sana into Slack, Teams, Copilot, Gemini Enterprise, and Claude, with permissions staying under Workday's control. The fuller Sana integrations aren't all available yet.
The new Workday Home is available now. Sana Concierge is in early access, with general availability expected in Q1 2027. I'd still like a named ITSM customer result showing how many requests it completes without human help. Workday's made the service-front-door pitch clearer; proving the difficult cases is another matter.
How Is Jira Service Management Expanding Beyond IT?
Atlassian's October 7 announcements at Team ’26 Europe gave us plenty to think about. Workforce Management in JSM is now generally available, with skill- and capacity-based routing. Solution Composer is in open beta, while proactive device monitoring and service actions through Slack, Teams, and Claude remain in closed early access.
Atlassian's announcement roundup adds more texture. Agents in JSM are generally available, allowing teams to assign work to Atlassian, Rovo Studio, and third-party agents connected through MCP. AI Change Risk Assessment is also GA, while new hardware asset-management capabilities connect device records to service context.
There's a customer-service angle too; you might be familiar with Customer Service Management, introduced in 2025, which supports live chat, WhatsApp, voice and email. Its newer MCP capabilities connect AI agents to external knowledge and services, while Optimize identifies knowledge gaps in human-resolved conversations.
Atlassian's Head of Product, IT Solutions, Shamik Sharma, summed up the ambition:
“The best service is the kind that unblocks teams to do their best work across dev, IT, business, and customer service teams.”
Atlassian wants employee problems, customer complaints, and operational signals meeting in the same service environment. One queue might be the wrong phrase. One service layer makes more sense.
There's a forced move in that direction, as well, of course. Opsgenie support ends April 5, 2027, with unmigrated data deleted. JSM is Atlassian's recommended destination for IT operations. Our Opsgenie flagship covers the migration headaches. Here, the bigger story is how alerting and service work are coming together.
Are Zendesk and Freshworks Opening the Same Service Front Door?
Zendesk’s October 2 announcement takes Employee Service AI Agents toward broader availability, with rollout scheduled from November 3 to December 1. The agents work inside Slack and Teams while respecting source-level permissions. I’d still check resolution allowances and overage charges before celebrating.
Zendesk’s October product update offers an arguably more useful development: automated IT asset synchronization from Jamf Pro and Microsoft Intune, alongside department spaces and custom roles. The same service interface can access device records while keeping departmental permissions separate. A connected front door still needs to know which back-room door it’s allowed to open.
Freshworks is taking a similar route with its MCP Gateway, spanning Freshservice and Freshdesk. Both integrations reached general availability in September, with standard limits and pricing taking effect for early-access customers on October 5.