> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# What an IT Manager Should Automate First
- URL: https://blog.jestor.com/what-it-manager-should-automate-first/
- Published: 2026-09-17T22:31:39.000Z
- Updated: 2026-09-17T22:31:39.000Z
- Author: Bruno Bannach

Deciding **what IT should automate first** usually means starting with the requests the team answers most often and understands best — which is also where an **AI** agent performs most reliably.

## Why IT automates everyone else first

IT teams build systems for other departments and leave their own process last.

- Requests arriving by message, email, and in person
- Priority determined by who asked most recently
- No resolution data to argue for headcount
- The same questions answered repeatedly

## An order that works

| Stage      | What to automate                                                |
| ---------- | --------------------------------------------------------------- |
| **First**  | Intake — a dedicated email address creating tickets             |
| **Second** | Classification — status, priority, and category set by an agent |
| **Third**  | Answering — the agent replying from your documentation          |
| **Fourth** | Closure — the agent closing when the requester confirms         |
| **Fifth**  | Measurement — classifying how much AI contributed               |

## How to set it up in Jestor

1. Set up the native email address in **Jestor** so requests create tickets automatically.
2. Attach your internal documentation as the agent's knowledge base.
3. Select exactly which fields the agent may edit — anything unselected stays protected.
4. Add a confirmation checkbox on critical processes so a person approves before the agent acts.
5. Enable log metrics on the stage field so **SLA** timing is captured.

## Why choose Jestor for IT operations?

**Jestor** makes the agent's permission boundary explicit in the configuration, which is what makes it reasonable to start on a process that matters rather than only on a sandbox.

The agent can read attached documents too, so a ticket arriving with a screenshot or a log file is answered with that context rather than without it.

## Frequently Asked Questions

### Can I limit what the agent changes?

Yes, field by field. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can the agent read attachments?

Yes, document reading is built in.

### How do I add a human checkpoint?

With a checkbox the agent waits for.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.