# Find out how much of your IT queue can run on its own

> Move the sliders for a first estimate, then send us a ticket export and we work out the real figure for free.

Source: https://stepwork.com/it-ticket-analysis

## Estimate your queue

An estimator with these controls: Tickets a month; Minutes per ticket; How much Stepwork takes on (Cautious, Expected, Ambitious); What to automate. It shows hours back a year.

Starts from a real analysis of 1,923 IT tickets. Hours are modeled.

**Fine-tune the estimate:** Change any group or use case. The sliders above scale what you set here.

These tickets need engineering judgment. They are counted in the queue and never in the hours.

Each use case has a handling time and a share of that time Stepwork removes. The starting minutes are estimates, because the export they came from had no time logged.

Lowest effort is built first, starting in month 2. Nothing is saved until a procedure is live, so year one returns less than a full year.

## Three steps, and the first is a CSV export

1. **Book a call and export your tickets:** Six to twelve months as a CSV, from any helpdesk.
2. **We sort every ticket:** Each one goes into a use case, matched to the flow or procedure that can run it.
3. **You get the report:** What Stepwork can run, what stays with your team, and the hours that come back.

## Works with the service desk you have: Jira Service Management or ServiceNow

Keep your service desk. Let the tickets run.

- **The ticket starts the run:** A webhook fires when a ticket is created or changes status.
- **The work happens in the app:** Stepwork signs in and does the steps, whether or not the app has an API.
- **The ticket gets the answer:** The run adds a note with what changed and resolves the ticket.

Works with: ServiceNow, Jira Service Management, Freshservice, ManageEngine ServiceDesk Plus, Zendesk.

[See how ITSM tickets run as procedures](https://stepwork.com/solutions/itsm-ticket-automation)

## Works with the service desk you have: An AI-native helpdesk

Your helpdesk automates about half. Stepwork works on the other half.

Serval, Ravenna, Console, and other AI-native helpdesks resolve requests through APIs. Stepwork runs the ones with no API to call, in the app's own screens.

- **About 50%, Your helpdesk:** Automated through APIs
- **22%, Stepwork:** Repeatable, with no API to call
- **28%, Your team:** Needs a person

About 50% is what Serval's customers report ([source](https://www.serval.com/)). The rest of the split comes from the analysis the estimator starts from.

## Questions about the ticket analysis

**Q:** What does the free IT ticket analysis include?

A breakdown of your queue by use case, the share Stepwork can run end to end, the share that stays with your team, and the hours that come back in three scenarios, from cautious to ambitious. It also lists the procedures to build and the order to build them in.

**Q:** What do you need from us?

A CSV export of six to twelve months of tickets with the summary, description, labels, and dates. Any service desk works. You can remove requester names before you send it.

**Q:** Do we have to replace our service desk?

No. Tickets stay in Jira Service Management, ServiceNow, Freshservice, or whichever tool you use. A webhook starts the procedure, and the result is written back to the ticket.

**Q:** We already use an AI helpdesk. Is the analysis still useful?

Yes. It shows which tickets people still handle and which of those repeat. Stepwork works in an app's own screens, so it can run a request where there is no API to call.

**Q:** Can I get an estimate without sending my tickets?

Yes. The estimator at the top of this page starts from a real analysis of 1,923 tickets. Move the sliders to your tickets a month and minutes per ticket, switch off the work you would keep by hand, and open Fine-tune to change any use case. An export replaces that company's mix of tickets with yours.

**Q:** How do you estimate the hours?

Each use case gets a handling time and a share of that time Stepwork removes, in three scenarios. Hours back are tickets, times minutes, times that share. When an export has no time logged, the handling times are estimates, and the report says so.

**Q:** Which tickets can't Stepwork run?

Work that needs judgment each time: outages, build failures, network design, and one-off projects. In the analysis this page starts from, that was 28% of the queue. The report lists those tickets separately and leaves them out of the hours.

## Send us your queue. We'll show you the hours.

Book a call, send a ticket export, and get a free analysis of what can run on its own.

---

This is the Markdown version of https://stepwork.com/it-ticket-analysis, built from the same copy as the page. Everything about Stepwork for AI tools: https://stepwork.com/llms.txt. Book a demo: https://calendly.com/shaun-maclellan/1-1-w-shaun-stepwork
