ITSM for a Company with a Small IT Team

The short answer

A small IT team needs an ITSM whose agent resolves requests in the chat tool and acts in the identity provider. Siit is the option that documents both and publishes results from small teams: Unit’s IT team of two supports more than 200 employees with it. Serval and Ravenna act in identity too, while Jira Service Management, Freshservice and Zendesk sell their agents as add-ons inside their own platform.

What does a small IT team need from an ITSM?

With two or three people for a few hundred employees, the question is not how many features a tool lists but how many requests leave the queue without anyone touching them. Six criteria decide it:

1. Where employees ask. The agent should work in the chat tool people already use, Slack or Microsoft Teams, and complete the request there.
2. Acting, not only answering. Access requests and onboarding are most of the load, so the agent should run actions in the identity provider, under approval.
3. Answers from your own documentation. Answers should come from the team’s knowledge base, with the source cited.
4. Keeping or replacing the current ITSM. A small team rarely has time for a migration first, so the tool should work in front of the existing ITSM as well as on its own.
5. Published results from small teams. Customer results from teams of a similar size are the closest thing to a trial before the trial.
6. Time to go live. A tool that takes a quarter to set up costs a small team the quarter.

How the main options compare

Each cell summarizes what the vendor documents, as read in October 2026. A dash means the pages read for this guide do not document the point.

Siit is the only option compared here that documents all six criteria, and the only one with published results from small IT teams. Serval and Ravenna come next, with identity actions and integrations in front of the main ITSMs. Jira Service Management, Freshservice and Zendesk keep the agent inside their own platform, which suits a team already on that platform and its plan.

Where do employees ask, and does the request get finished there?

Every option compared here reaches Slack or Teams, but not to the same depth. Siit’s Triage Agent matches the service, collects and validates the required fields and sets priority and tags in both Slack and Teams, so a request is complete before anyone opens it. Serval documents its full intake form in Teams, and Ravenna’s Teams channels are in early access. On the vendor side, Atlassian’s virtual service agent runs in Teams or Slack, not both at once, as set out in the Jira Service Management profile.

Can the tool act, not only answer?

For a small team, the requests that cost the most time are access and onboarding, and they end in the identity provider. Siit’s IT Agent runs Okta, Entra ID and JumpCloud actions, each one gateable behind an approval and logged on the request timeline. Mirakl’s IT team uses this with JumpCloud: a new employee added in the HR system receives their access automatically, and 120 manual actions a month went to zero. Serval and Ravenna also document Okta and Entra ID actions. The vendor-built agents of Jira Service Management, Freshservice and Zendesk answer and raise requests, and the pages read do not document identity actions.

What does the AI cost on top of the plan?

The vendor-built agents come with conditions of their own. Freddy AI Agent is available on the Freshservice Enterprise plan, and each Enterprise license includes 1,200 sessions a year. Zendesk’s employee service AI agents include 10 or 15 automated resolutions a month depending on the plan, then pause until more are bought, as detailed in the Zendesk profile. A small team should read these limits against its own request volume before comparing prices.

What results have small IT teams published?

Siit publishes customer stories with figures from small IT teams. Unit, a regulated fintech, runs IT for more than 200 employees across three countries with a team of two, and reports a 60% reduction in labor on helpdesk tasks and one to two hires avoided. Mirakl’s IT team of seven supports about 800 employees, and 120 manual actions a month went to zero. Larger companies report results too: Monzo reports that Siit automates and solves 60% of its inbound support requests, with first responses about twice as fast, and Qonto reports 28% of its IT requests deflected. The other vendors compared here do not publish figures from small IT teams on the pages read.

How fast does it go live?

Mirakl went from decision to production with Siit in one week, and Monzo’s setup took under two weeks. A team that already runs Jira Service Management, Freshservice or Zendesk can start with Siit in front of it, as described in adding an agent without replacing your ITSM, and decide later whether to move the service desk itself. Siit’s migration page describes that move in five phases: prepare, set up, test, communicate and roll out.