ESM software for HR and IT: comparing shared intake with cross-system fulfillment
Every ESM platform gives HR and IT one front door. We read how seven tools handle a moved start date and a swapped manager, and which ones keep up.
15 min read
TL;DR
- Most enterprise service management (ESM) software gives human resources (HR) and IT a shared front door. The harder job comes after: finish the request in the HR system, the identity provider, and the device tool, then prove it happened.
- For teams keeping ServiceNow as the service desk, Workday as the HR system, and Okta as the identity provider, our pick is Computer, by DevRev, as the layer across them. Among the five service platforms we read, Freshservice documents the most writes that report results.
- We read seven tools’ documentation for one onboarding request, then for a moved start date and swapped manager. In the public docs we read as of October 2026, only Freshservice has a help page for a moved start date. Only ServiceNow documents moving approvals to a new manager, through an opt-in setting.
A new hire taps their badge on their first morning, and the door stays shut. Their laptop is still in a courier van, and nobody has created their chat account, yet HR, IT, and facilities each closed a ticket for them. The shared intake did its job, since every team got the request. The morning fell apart at the handoff. No one carried the work into Okta, Workday, and the door reader, and no one checked that it landed.
Shared intake is one place to ask: a portal, a form, and a ticket each department can see. Cross-system fulfillment changes the HR system, the identity provider, and the device tool through an application programming interface (API), System for Cross-domain Identity Management (SCIM) provisioning, or a connector. Then it confirms each change with the system that made it, the record an identity governance review asks for. Our guide to enterprise service management goes deeper on the practice.
This is desk research: on September 30, 2026, we traced one onboarding through seven tools’ documentation and product pages and took every price from the vendor’s own pricing page. We re-checked each claim on October 17, 2026. “Not documented” means we didn’t find it on the vendor’s public pages, so ask the vendor.
Seven ESM software tools at a glance
Of the seven tools compared here, two are execution layers over your existing systems, and five are service platforms that hold the request and the record. Prices follow each vendor’s own billing terms, so compare them at your agent count on the same billing period. The Reddit and G2 comments in the entries each come from one person, with a link and a date, and an entry goes without one where no conversation about that product turned up.
The seven platforms, entry by entry
1. Computer, by DevRev – the layer across the systems you keep
Computer is our AI teammate for ESM work that crosses the service desk, HR system, and identity provider you already run, and our AirSync connectors carry the hire’s context in. It connects to four HR systems: our Workday and HiBob connectors import job title, manager, location, and start date. BambooHR syncs employee records both ways, and our SAP SuccessFactors listing names positions, departments, and managers.
Approvals reach people where they already work: our approval workflow snap-in sends approval requests through Slack and email when a ticket reaches a set stage. Our two-way ServiceNow sync creates and updates ServiceNow tasks and requests, and ServiceNow stays the record.
Actions in other systems are ones you build yourself, as tools or workflows in Agent Studio. Each runs as the asker by default, with the asker’s permissions. Its “Needs Approval” setting starts off; turn it on, and the agent asks before that tool or workflow runs. We publish approval gates on any action and an audit trail.
For the human resources information system (HRIS), our IT page describes Computer “updating HRIS records.” Our IT support guide describes Safe Actions, where the agent acts as the asker, pauses for approval, and keeps an auditable record, and its examples include confirming that provisioning completed.
This DevRev video, from our own channel, shows how to add tools and workflows in Agent Studio, the build step for any action our import-only Okta and Microsoft Entra ID connectors don’t perform.
Best for: IT and HR operations teams that keep ServiceNow, Workday, and Okta as systems of record and want one layer across them, with approval gates and an audit trail.
Pricing: We price on usage credits. Agent Studio is part of the Pro plan. Pro is listed at $30 a month on our Computer site, with a discount for annual billing, and Pro and Max both read “Contact us” on our devrev.ai pricing page.
Limitations:
- Our Okta and Entra ID connector docs, like Workday’s, describe one-way imports. The connector writes we document go to ServiceNow, Jira Software, and BambooHR employee records. For the rest, plan on a tool or workflow built in Agent Studio.
- Our Agent Studio launch post says it’s “optimized for customer experience, support, and operations” and “not a general-purpose horizontal builder,” though it covers IT service desk work.
- We don’t document delegation for an approver who is out.
- Our help center lists agents for internal teams as “coming soon,” so ask us when they reach your workspace.
- Our nearest named customer story is about knowledge search, not onboarding: FAME, a school management specialist, unified data across Zendesk, Jira, and SharePoint with our enterprise search.
Name one HR or IT action you’d want approved before it runs. We’ll show you how to build it in Agent Studio with the approval step switched on and the asker’s permissions applied. Book a demo →
2. Aisera – Automation Anywhere’s AI service desk
Aisera is part of Automation Anywhere, the automation software company, which acquired Aisera in November 2025. Automation Anywhere’s product page calls it “Aisera’s AI service desk.” Its Execute Rest Call action returns a success flag and the status code, its Okta connector assigns app access and security groups, and it creates and updates ServiceNow incidents and approvals.
Best for: Automation Anywhere customers that want a chat agent in front of ServiceNow.
Pricing: Not published. Automation Anywhere’s acquisition announcement says the company “charges for work done rather than underutilized seats.”
Limitations:
- Aisera’s HR page now points to Automation Anywhere’s HR automation page, and we didn’t find an onboarding workflow in Aisera’s public docs, so ask for one in the demo.
- The Entra ID connector documents import only.
- Built-in roles carry IT names. Ask how HR cases stay hidden from IT agents.
On G2, a senior architect at a small business credits Aisera with HR queries as well as IT ones:
“Aisera helps reduce the manual load on support teams by resolving repetitive IT and HR queries automatically.”
Rohit W., Senior Architect. G2, July 2025 ↗
3. ServiceNow – HR cases locked down, and plenty to configure
ServiceNow’s HR security page says the system administrator can’t view HR profile information, and only HR roles see work notes on HR cases. Its onboarding builder assigns each step to HR, IT, or facilities, and you can set a step to stay open until the case or request it created completes.
Spokes create users and assign licenses in Entra ID, create users in Okta and Google Directory, and hire or change jobs in Workday. Each spoke requires an Integration Hub subscription, and the sample flows ship as drafts.
Since the acquisition closed on December 15, 2025, ServiceNow also owns Moveworks, an AI assistant employees ask in Slack or Teams. Moveworks answers from a profile refreshed every four hours and provisions by adding users to Okta groups. Approvals stay in the system of record, with the approve button in chat.
Best for: Enterprises that already run ServiceNow for IT and need HR cases locked down on the same platform.
Pricing: Not published, and HR Service Delivery and IT Service Management are separate package families. Employee Journey Management, the cross-department onboarding product, sits in HR Advanced.
Limitations:
- Bristlecone, a supply chain services provider in the Mahindra Group, builds the Workday and SuccessFactors integrations as Store apps, and the Workday one is a paid listing.
- Calling a third-party system from an onboarding step takes configuration.
- Granular Delegation doesn’t reach flows: “Flows and workflows ignore delegation rules,” so approvals there “must use the existing service delegation features instead.”
On r/servicenow, one commenter rates HR Service Delivery “great as a case management tool for HR,” but had to build a custom HRIS integration.
4. Jira Service Management – no separate HR product, assembly required
Atlassian, Jira’s maker, says HR needs “no separate product or add-on to purchase” once you license Jira Service Management. Its native connectors create users and add them to groups in Okta and pull the start date, location, and manager from Workday. Journeys, still in Atlassian’s feature lab and “currently in development,” link work items across HR, IT, and facilities spaces under one parent.
Best for: Atlassian shops with an admin who likes building, where HR should run on the license you already hold.
Pricing: The pricing page shows Standard at $21.50 and Premium at $55.28 per agent a month, the month-to-month price at the default of 75 agents. Smaller teams pay more: the licensing page prints $26.90 and $61.60 a month for one to 15 agents.
Limitations:
- For HR case notes, finer control than hiding the whole work item “is not yet available.”
- Approval delegation is an open suggestion on Atlassian’s public tracker.
- Workday has no predefined write action, and BambooHR, HiBob, and SuccessFactors come through a third-party Marketplace app.
On G2, a human resources executive at a mid-market company says Jira Service Management makes “collaborating with other departments on the same ticket” possible. The downside: it “might be slow because minor modifications to forms or workflows frequently call for administrator access.”
Swetha V., Human Resources Executive. G2, August 2025 ↗
5. Freshservice – identity writes and returned results on one platform
Of the five service platforms we read, Freshservice covers the most steps of what we call the “write-and-confirm” test: identity writes, plus a result the workflow can act on. Its orchestration guides list actions for Okta, Microsoft Entra ID, and Google Workspace, from creating a user to adding a license. The 2022 guides use the old names Azure Active Directory and G Suite, and the apps they cover were republished in 2026. Each action returns a status code and a system message the workflow can branch on, and the execution log marks it “Success,” “Complete with errors,” or “Failed.”
Restricted workspaces keep out account-wide admins, and approval delegation is a profile setting with dates.
Best for: Mid-market teams that want HR and IT on one platform, where identity steps run on their own and approvals survive a vacation.
Pricing: Starter is $19, Growth $49, and Pro $99 per agent a month, billed once a year. A business agent license for HR is $49 a month, with no billing period printed, and Journeys need Pro or Enterprise.
Limitations:
- Freshservice meters orchestration: Pro includes 5,000 transactions a month, and extra packs cost $250 per 1,000.
- Freshservice labels the HiBob connector beta, and no recipe writes to BambooHR, HiBob, or SuccessFactors.
- A Journey approval with no response keeps its phase in progress. The docs cover reminders, so ask about a timeout or escalation.
On r/sysadmin, at a company of about 120 people, HR starts onboarding in Freshservice, and the identity automation is still a plan: “we haven’t had time to implement that yet.”
6. ManageEngine ServiceDesk Plus – a separate desk per department
ServiceDesk Plus, from ManageEngine, part of software maker Zoho, keeps HR cases private with walls: each department gets its own service desk instance. ManageEngine’s on-premises docs say technicians from one instance can’t take part in another’s activities. Approvals run up to five stages, with delegation to a role or a backup user.
Best for: Budget-conscious teams that want HR and IT in separate desks, with an admin willing to build flows.
Pricing: On Cloud, Standard is $13, Professional $27, and Enterprise $67 per technician a month, billed once a year. ManageEngine bills each instance on its own, and only one can use the free tier.
Limitations:
- The native Entra ID sync “does not modify data in Azure.” Creating the account takes a flow you build in Zoho Flow.
- We didn’t find a Workday or HiBob integration on ManageEngine’s public pages.
- Active Directory actions wait for a technician to run them from a widget.
On G2, a reviewer at an enterprise bank names the catch in that model:
“The fact that you have to buy an instance if you want separate helpdesk portals for each department.”
Verified reviewer in banking. G2, August 2026 ↗
7. TOPdesk – one shared desk with careful filters
TOPdesk puts HR, IT, and facilities in one environment, and filters keep them apart. Its category filter rule reads: “Only cards of a specific category are visible.” By default, a request goes to the requester’s manager for approval, and a change can name a manager group as backup. Its onboarding example is a portal form linked to a template that creates the activities.
Best for: Organizations that want facilities, HR, and IT routed well in one tool and accept that people complete most steps.
Pricing: At 30 agents, TOPdesk’s calculator shows $64, $91, and $128 per agent a month for Essential, Engaged, and Excellent. The page includes hosting and doesn’t state a billing period. Change and workflow management starts at Engaged.
Limitations:
- Workday, SuccessFactors, BambooHR, and HiBob don’t appear on its Marketplace.
- Writing into Entra ID takes a paid third-party Marketplace app or API steps you build.
- You adjust planned dates in the Planner, and we didn’t find a page where a start date updates them on its own.
One onboarding request, traced through seven platforms
We traced one approved hire, starting in 10 days, who needs accounts, a laptop, payroll setup, a building badge, and a software bundle the manager approves.
Intake: what each platform knows about the hire, who sees the case, and who approves.
Fulfillment: what each platform changes in the systems of record, and what confirms each step is done. Confirmation is one of three: a result from the target system, a record a person or flow closes in the platform, or nothing the vendor documents.
When we introduced Agent Studio, Michael Machado put it this way:
“For a CIO, faster resolution is the visible win; the audit trail behind every action is the one that matters at renewal.” – Michael Machado, Corporate Vice President of Product and Brand at DevRev
Our pick is Computer when you’d rather connect ServiceNow, Workday, and Okta than replace them. It brings in the hire’s Workday record, can ask before an action runs, and logs what it did.
When the start date moves and the manager changes
In most of the seven, the hire’s profile updates on its own, but only ServiceNow documents moving approvals and tasks already assigned, and only when the manager changes. The change we traced: the start date moves up a week and the hiring manager changes mid-request, a mover event in “joiner-mover-leaver” terms.
Freshservice’s help page for a moved start date, the only one we found, warns that laptop delivery and access may already sit on the old date.
Intake or fulfillment? Six questions to ask before the demo
- Do employees email three departments because there’s no single place to ask?
- Do requests sit unassigned because nobody knows which team owns them?
- Does HR avoid the shared desk because IT could read its cases?
- After a ticket closes, does someone still log in to Okta or Entra ID to create the account?
- Has a new hire told you on day one that someone missed a step?
- When a start date moves, does someone re-enter it in more than one system?
If you said “yes” to most of the first three, you need shared intake, and one of the five service platforms fits. Each entry’s “Best for” line says which.
If you said “yes” to most of the last three, you need cross-system fulfillment: an execution layer, and Computer if your systems of record are staying put.
In an essay on our blog, Amar Gautam sets out what makes a shared desk safe:
“The answer to the fear isn’t a smarter model. It’s structure: permissions enforced where the data lives so the system never retrieves what the requester couldn’t see, approvals written as policy, an audit record for every action, and explicit decisions about which actions run automatically, which need a human, and which are never automated.” – Amar Gautam, Head of DevRev Labs
Back at that locked door, every team had the request, and nobody had finished it in Okta, Workday, and the door reader. If your systems of record are staying, that unfinished half is the one to test. Bring your last five onboardings to a demo, and we’ll trace one through Computer with you. Book a demo →
