Solutions / Use case

IT service desk automation, from first request to closed ticket.

Every ticket runs across the ITSM platform, the identity provider, the HR system and chat. When those systems don't talk, requests sit in a queue until somebody copies them across. Tray.ai connects every handoff, so IT only works the tickets that need a person to solve them.

Start free trial Book a demo
One software request moving through the IT service desk: asked in Slack, opened as a ticket in ServiceNow, checked against the role in Workday, the group added in Okta, the Adobe licence assigned, the ticket resolved, and the confirmation posted back in the Slack thread.

The short answer

What is IT service desk automation?

IT service desk automation handles the routine work behind employee IT requests: sorting each ticket to the right team, resetting passwords, fulfilling software and access requests, running incidents and taking back unused licences. It runs across the ITSM platform, the identity provider, the HR system and chat, and most tickets wait in the handoff between those systems rather than inside any one of them.

  1. 1 Triage
  2. 2 Reset passwords
  3. 3 Fulfil requests
  4. 4 Approve access
  5. 5 Resolve incidents
  6. 6 Reclaim licences
of IT tickets deflected in the agent's first two weeks at Apollo
40%
first-response time at Apollo
1 sec
IT satisfaction score Apollo kept with the agent live
4.95/5
a month saved on IT provisioning by Auctane's IT team
50 hrs

The IT service desk, stage by stage

Six stages, each with what breaks and a how-to guide for building it.

  1. 1

    Intake, triage and routing

    Every channel feeds one queue, and each ticket goes to the one team that fixes it.

    Where it breaks: The requester picks the wrong category, and the ticket moves three times before anyone works it.

  2. 2

    Password resets and lockouts

    People reset a password or clear a lockout themselves, after a check with a second factor they already use.

    Where it breaks: A reset anyone can trigger with a name and a manager's name, which is the first thing a phishing attempt tries.

  3. 3

    Request fulfilment

    Common requests like software, groups and mailing lists are done end to end when the role already allows them.

    Where it breaks: A request the role already allows still waits a day for somebody to click the same three buttons.

  4. 4

    Access requests and approval

    Access goes to the owner of the system for approval, and every grant gets an end date by default.

    Where it breaks: Access granted for a project in March is still there at next year's access review.

  5. 5

    Incident to resolution

    One action opens the channel, pages the right people and starts the timeline from system events.

    Where it breaks: The timeline is pieced together from Slack a week later, and the times are wrong.

  6. 6

    Licence reclamation

    Unused seats are found, the holder is asked, and the seat comes back before the renewal.

    Where it breaks: A seat taken without asking, and requested back the same week.

Three ways to connect the systems

  • The ITSM platform’s own add-ons. Quick for the systems the vendor chose to support, and each one stops at the edge of that list.
  • Custom scripts. Full control, and your team owns the fixes, the credentials and the monitoring for as long as they run.
  • An integration platform. Every handoff in one place, with the same error handling, logging and access control, and the same workflows available to an AI agent. This is Tray.ai: IT builds the workflows and governs who can change them.

The Tray.ai platform behind it

Tray.ai is the enterprise orchestration platform for data and AI. These are the parts of it that run IT service desk.

Merlin Agent Builder

Build AI agents that act, not just chat.

Intelligent Integration

The iPaaS built for the AI era.

iPaaS Governance

AI governance built in, not bolted together.

The metrics IT service desk automation moves

What service desk and IT operations teams measure, and which stage each number depends on.

Share resolved without a person
Tickets closed with nobody on the IT team touching them.
What moves it Fulfilling the requests a role already allows, end to end. How to build IT service desk fulfilment 
Reassignments per ticket
How many times a ticket moves between teams before it is resolved.
What moves it Classifying from what the ticket says, and attaching context before routing. How to build IT ticket triage and routing 
Password and lockout share
Share of all tickets that are password resets or locked accounts.
What moves it A reset people run themselves from chat, after a second-factor check. How to build self-service password reset 
Time to access
Hours from an access request to the person having the access.
What moves it Routing straight to the system owner and granting the moment they approve. How to build access request and approval 
Mean time to resolve (MTTR)
Average time from an incident being declared to the service working again.
What moves it Opening the channel, paging and building the timeline in one action. How to build incident to resolution 
Unused licence spend
What you pay for seats nobody has used in the last 60 or 90 days.
What moves it Reclaiming idle seats on a schedule that runs before each renewal. How to build SaaS licence reclamation 

IT service desk connectors

The systems the IT service desk runs on, grouped by the seat each one fills. Each links to its connector page.

ITSM and ticketing

Where tickets are raised, routed, worked and closed.

Identity and access

Where accounts, groups, passwords and app access live.

Devices and apps

Where laptops are managed and software seats are assigned.

Monitoring and on-call

Where incidents start, who gets paged, and where the fix ships.

People and finance

Where roles, managers and start dates come from, and where licence spend is paid.

Chat and knowledge

Where people ask for help, and where the answers are written down.

Data and reporting

Where ticket outcomes and licence usage are reported.

Connections between them

Field mapping, templates and common problems for the pairings IT service desk depends on.

Anything not listed connects through the full connector library, or directly through its API.

Teams running IT service desk on Tray.ai

“The agent only responds when it knows it can fully or partially solve the problem. If it can't, it escalates. That's why people trust it.”

— Ramiro Meyer, Head of IT Automation and AI Solutions, Apollo
Read the study

Processes next to the IT service desk

These share systems and data with the service desk without being stages of it.

People operations

How to build employee onboarding provisioning

Drive it from the HRIS, derive access from the role instead of a copied colleague, sequence around the start date, and prove it happened. The prompts that build it.

People operations

How to build employee offboarding deprovisioning

Revoke on the leave date, cover every system instead of the ones you remember, transfer what they owned, and prove it. The Headless prompts that build it.

IT and security

How to build a device lifecycle sync

Reconcile what management sees against what finance owns and what HR says, and make an unassigned device an exception instead of a row. The prompts.

AI operations

How to build a knowledge base to vector sync

Chunk on structure, carry permissions into the index, delete on delete, and re-embed only what changed. The Headless prompts that build it.

AI operations

How to build human approval for agent actions

Decide what needs approving by blast radius, show the approver what will happen, expire cleanly, and keep the record. The Headless prompts that build it.

Customer success

How to build support ticket routing

Route on the skill needed and the account, not on who is free. Derive priority from contract and impact, and time the clock from the customer. The prompts.

Reading and resources

Infographic

Your help desk needs help

A practical six-step framework for deploying ITSM AI agents that go beyond chatbots to resolve help desk tickets, with built-in governance and measurement.

On-demand webinar

Apollo’s path to 40% IT ticket deflection with Tray agents

Watch how Apollo moved from a proof of concept to live IT agents that deflect 40% of tickets and improve response times. Join the webinar to hear their story.

On-demand webinar

Beyond chatbots: Deploying AI agents that actually solve IT tickets

Learn how to cut IT ticket volume going to a human by 75%—with a real AI agent built for action, not just answers.

From the blog

BlogIT service desk process: where requests stallBlogIT ticket triage: why tickets keep getting movedBlogPassword reset automation: who is really asking?BlogWhy IT needs an AI-powered support agent (and how it works)BlogIT onboarding process: access before day oneBlogIncident management: why incidents come backBlogHow to automate software license optimizationBlogEverything you need to know about ITSM agentsBlogAI Agents in action: Lessons from tech innovators

Speaking the same language

Definitions for the terms that come up in this conversation.

AI agent

An AI system that can reason about a task, use tools to act on it, and learn from feedback — not just generate text.

Human-in-the-loop

A design pattern where human approval or review is a step inside an otherwise automated process — keeping people accountable for the decisions that matter.

Workflow automation

Software that executes a defined sequence of steps automatically — moving data, triggering actions, and routing decisions without manual intervention.

Frequently asked questions

How is an IT service desk different from customer support?

+

An IT service desk serves employees, and most of its work is changing something in a company system, such as an account, a group or a licence. Customer support serves customers, and most of its work is answering them. The two sometimes share a ticketing tool, but they act on different systems for different people.

Which systems does Tray.ai connect for the IT service desk?

+

ITSM and ticketing (ServiceNow, Jira Service Desk, FreshService, BMC Remedy), identity (Okta, Azure Active Directory, OneLogin, JumpCloud), devices and apps (Microsoft Intune, Adobe, Zoom), monitoring and on-call (Datadog, OpsGenie), HR (Workday, BambooHR, Personio) and chat (Slack, Microsoft Teams). Anything without a connector is reached through its own API.

Where do AI agents fit on the IT service desk?

+

In the conversation at the front and the routine fixes behind it. Apollo's IT agent, built with Merlin Agent Builder, deflected 40% of IT tickets in its first two weeks, answers in about a second, and escalates to a person when it can't solve the problem. The agent calls the same workflows described on this page, so a reset or an access grant follows the same checks whether a person or an agent asks.

Does an agent get free run of our systems?

+

No. An agent can only call the workflows it has been given, with credentials held in Tray.ai rather than in the agent, and every step is logged. Anything outside the rules, such as access to a sensitive system or an account with admin rights, goes to a person on the IT team.

Can IT build this without engineering?

+

Yes. Auctane's small IT team built its own provisioning automations on Tray.ai and saves 50 hours a month. Apollo's IT team built the IT agent that now handles routine tickets in Slack.

Do we have to replace our ITSM platform?

+

No. Tray.ai connects the ITSM platform you already run to the identity, HR, device and chat systems around it. The stages above describe what moves between systems, not which ones you use.

Last reviewed 2 October 2026.

See IT service desk running on your stack.

Walk through your systems and stages with a Tray.ai expert.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.
Browse the how-to guides