Most companies don't find out how many intake channels they've built until a new hire's first morning goes sideways. IT was waiting on HR to confirm the start date, HR assumed IT had shipped the laptop, and Facilities heard about the new desk when someone walked up to it looking for one. Every team closed its own ticket. Nobody closed the request.
Consolidating IT, HR and operations requests is mostly about deciding who owns the whole outcome, because at most companies the honest answer is nobody.
TL;DR:
Onboarding, offboarding and role changes break at the handoffs, because each team owns its own queue and completion record.
Fixify's 2026 benchmark found 4.4-hour median resolution with heavy automation and 71 hours without it.
Real consolidation needs one intake point, one workflow across every system, and one shared record.
Automate the requests that resolve the same way every time (password resets, software access, PTO) before you touch the messy cross-department ones.
Ravenna orchestrates this inside Slack and Teams and logs every step to one record.
Why Fragmented Request Channels Break Down Across IT, HR, and Operations
Every department built its request process for its own work, and it shows. IT has a queue and a form, HR has a shared inbox, and Operations has a spreadsheet somebody started as a stopgap. Each works fine for a request that stays inside it. The trouble starts when one request needs all three.
The cost shows up in three places.
Duplicate effort. Each team asks the employee for context the other two already collected, because nobody inherits a record. You've seen it in your own queue: the same new hire's start date, manager and location typed into three systems by three people.
Latency. Fixify's 2026 IT Help Desk Benchmark Report covers 50,000+ tickets across 30+ organizations. Heavily automated help desks hit a median resolution of 4.4 hours; desks where people do most of the work took 71. The number worth sitting with is the partially automated one: across ticket categories, those medians swung between 49 and 102 hours. That's what half a consolidation looks like: a bot takes the request and a human still walks it across three teams. Fixify sells help desk automation, so hold the gap loosely.
Compliance exposure. Without one execution log, nobody can show that IT suspended the Okta account and HR closed the HRIS record before the employee's last day. That's a security gap and an audit finding at once, and your SOC 2 auditor will ask for exactly that evidence.
The systems underneath don't help. Korn Ferry's 2026 Global Talent Analytics Survey of 1,600 senior leaders found 84% run three to 10 talent platforms and only 5% have them fully connected. It measures talent data, not request queues, so don't quote it as the price of your intake mess. It does tell you the HR systems your requests land in weren't built to talk to each other either.
Which requests actually cross departmental lines?
More of them than your ticket categories suggest. Onboarding is the obvious one: IT sets up the Okta account, HR updates the HRIS, and Operations ships a device, all before the first morning. None of them can finish without knowing where the other two stand.
The same shape repeats across:
Offboarding: IT suspends accounts and reclaims licenses, HR closes the employment record, Operations recovers hardware
Role changes: IT adjusts access and group memberships, HR updates title and department, a manager approves the new access tier
Department transfers: access policies, distribution lists and desk assignments all move at once
Device provisioning for new projects: MDM enrollment, software licensing and cost-center assignment travel together
Treat any of these as a single-team ticket and you get the familiar failure. The IT ticket closes, the HR task never gets filed, and the laptop ships to the old office. Cross-department requests are the highest-stakes work in the building, which is exactly why service management beyond IT exists as a category.
How to Audit Your Current Request and Resolution Environment
Audit what employees use, not what the wiki says they use. Those are different lists at almost every company.
Step 1: Inventory every intake channel
Count the ones nobody would admit to designing: DMs to whichever IT or HR person answers fastest, channels like #it-help that grew without a plan, a shared inbox nobody owns, and the portal people open when they remember it exists.
Step 2: Map who owns resolution
For each request type, write down who receives it, who resolves it and which system they update when it's done. You'll find the same request entering through three channels depending on who the employee knows.
Step 3: Flag every request that crossed a team
Pull the last 30 days of resolved requests and mark every one that needed more than one team. Look for requests where you asked the employee for the same context twice, where one team waited on another with no signal, or where someone typed the same data into two systems. That list is your consolidation backlog.
What a Consolidated Request Layer Has To Do
Plenty of tools will unify your intake forms. Fewer will unify the work behind them, and that's the part that matters. Four requirements separate the two.
Intake where people already work. If employees DM IT in Slack today, the system should catch that message and route it. A new channel people have to learn is one more channel they'll route around.
One workflow across systems. The request has to reach your identity provider, HRIS and MDM as one sequence. Unified intake without cross-system execution just moves the fragmentation one layer down.
Shared request state. Every team on a request sees the same completion record, so the gap between what IT has set up and what HR has updated shows up as an open step before day one, not as a complaint after it.
Approvals that match each department's rules. An HR approval on a policy change and an IT approval on privileged access are different decisions, and one generic gate flattens them into a step nobody trusts. You want sequential routing to each department's approver, rules that auto-approve low-risk requests and escalate privileged ones, and skip conditions for routine work. Every decision should land on the same record, which is how a Slack approvals workflow across departments should behave.
Approval Workflows That Work Across Departments
Cross-departmental approval logic is where most consolidation attempts fall apart. Each department has different requirements, and a generic confirm-or-deny gate flattens them into a single step nobody trusts. What cross-departmental approval actually requires:
Sequential routing to the right stakeholder in each department (the foundation of a well-designed Slack approvals workflow across departments) in the right order, without the employee re-submitting context at each stage
Attribute-based routing so a low-risk request auto-approves while a privileged one routes through IT security and a department head simultaneously
Skip conditions that bypass approval stages when predefined criteria are met, cutting resolution time for routine requests without creating a governance gap for sensitive ones
When IT and HR each track approvals separately, the composite record exists nowhere. A consolidated execution layer closes that gap by writing every approval decision to a single shared record tied to the original request.
Which Requests Should You Automate First?
Start with the ones that resolve the same way every time, where a human in the loop adds delay but no judgment. Fixify's benchmark found app assignment alone makes up 1 in 4 tickets, so software access is usually the biggest single win on the board.
Request Type | Owning Department | Resolution Path | Human Judgment Required? |
|---|---|---|---|
Password & MFA resets | IT | Same trigger, same resolution every time | No |
Software access requests | IT | Employee requests → manager approves → Okta provisions | Approval only |
Employment verification letters | HR | Fixed template pulled from HRIS data | No |
PTO requests | HR | Employee submits → manager approves → HRIS updates | Approval only |
Google Group creation & inbox delegation | IT / Operations | Repetitive, low-risk, fully scriptable | No |
These are the requests that consume the most cumulative hours precisely because they're so frequent and so predictable. A team automating even three of these categories recovers meaningful capacity without touching anything complex or judgment-dependent. Automate the consistent paths first, and let human agents handle requests that genuinely require judgment. The goal is removing the manual work that shouldn't exist at all.
Where does routing stop and resolution start?
A rules-based router reads the request, matches it against a condition tree and drops it in the right queue. That gets it to the right person; it doesn't get it done. The coordination work still falls to whoever picks up the ticket.
I believe most of what gets sold as AI triage in ITSM today is a routing upgrade dressed up as a resolution upgrade. Classifying a request faster is nice. Closing it faster is the point.
Agentic workflows go further. An agent reads the intent, pulls context from connected systems and runs the resolution through multi-agent orchestration instead of handing it person to person. Your onboarding request doesn't split into an IT ticket and an HR ticket; one sequence triggers the Okta workflow, updates the HRIS and kicks off device enrollment. That's the gap AI-native ITSM is built to close.
Ambiguous requests are where this earns its keep. A router seeing "I need access to the benefits portal" picks a queue and hopes. An agent reading the context can tell whether that's an Okta app assignment or an HR enrollment question, and nobody has to explain themselves twice.
How Ravenna handles requests that cross IT, HR and Ops
Ravenna runs as a Slack and Teams-native workflow automation platform, which means the shared intake layer already exists where employees work. No portal to adopt. Requests arrive in Slack or Teams, and Ravenna routes, executes, and resolves without asking anyone to context-switch.
Two named agents handle domain-specific work over one shared orchestration layer. The IT Agent manages access provisioning, MFA resets, and device workflows. The PeopleOps Agent handles onboarding sequences, employment verification, and PTO routing. When a request crosses department lines, they coordinate as a single operation instead of filing separate tickets in separate queues.
Take onboarding as the clearest example. One employee submits through Slack. Ravenna's AI agents provision the Okta account, update the BambooHR or Workday HRIS record, create the Google Workspace alias, and add the employee to the right Google Groups as one atomic sequence. IT, HR, and Operations see the same request state in real time.
One fit boundary worth stating plainly: Ravenna is purpose-built for Slack-native and Teams-native organizations; teams that need deep ITIL process compliance or formal change advisory board structures are a different fit.
Final Thoughts on Consolidating IT, HR, and Operations Requests
Most of the manual coordination holding your team back follows the same pattern: three departments, three queues, no shared view of whether the full request is actually done. The consolidation work starts with a clear-eyed inventory of what employees actually use, not what you think they use. Get that right, and the rest of the sequence, unified intake, cross-system execution, shared completion records, falls into place. Reach out to Ravenna to see how the execution layer works across IT, HR, and Operations.
FAQ
How do I automate onboarding across Okta, BambooHR and Google Workspace without three separate tickets?
Use a workflow layer that treats onboarding as one request with several steps. In Ravenna, one Slack request triggers the Okta provisioning workflow, updates BambooHR or Workday, and requests the Google Workspace alias and groups. Each step is verified and logged to the same record.
How is Ravenna different from Freshservice for cross-department requests?
Freshservice has workflow automation of its own, so the difference is where the work starts and how it gets stitched together. Ravenna takes requests directly in Slack or Teams and runs cross-department workflows as one sequence with a single shared record, rather than a set of linked tickets inside a portal.
How do approvals work when one request needs IT, HR and Ops sign-off?
Each stage routes to the right approver in order, with rules that auto-approve low-risk requests and escalate privileged ones. Every decision writes to one audit trail tied to the original request, so compliance reviews one timeline instead of three partial ones.
Which IT and HR requests should I automate first?
Start with requests that resolve the same way every time: password and MFA resets, software access, verification letters, PTO and Google Group changes. The signal is when the same request keeps landing in your queue and the human in the loop adds wait time but no decision.
