Choosing a ticketing system for a small IT team
A small IT team should choose ticketing software by the problems it has today: lost requests, no deadlines, requesters who can't see what is happening to their ticket. Use the checklist below to compare any tools on the same terms, and leave out the enterprise features you would pay for and never switch on.
Start with your own list
Before you open a single product page, write down three things: how requests reach you now, how many people work them, and the one thing that goes wrong most often. A team of five that loses requests in a shared inbox needs ownership, priorities and deadlines. It does not need asset discovery or a change advisory board. Rank every feature below against that list.
The checklist
1. Channels
Which channels do requests come through? Email and a web portal cover most small teams. Some tools add other channels as well. If you do not need them, do not pay for them, because every extra channel is one more place to answer on time.
2. Ownership and queues
Look for one owner per request, an unassigned view, teams, internal notes and some way to stop two people answering the same message. These are the basics that fix a shared inbox. See from a shared inbox to ticketing.
3. Priorities and SLAs
Can you set first response and resolution targets by priority? Can the clock follow business hours and holidays, and pause while you wait for the requester? Is there a warning before a breach? If you serve different groups, can each have its own targets? The IT SLA guide explains what to look for.
4. A self-service portal
A portal lets people submit structured requests and see progress without emailing again. Look at the sign-in options, forms that ask different questions for different request types, and a portal that can carry your logo and wording.
5. Roles and permissions
Decide who can see what. Even a small team usually needs administrators who change settings, technicians who work tickets, and requesters who see only their own. Custom roles and an audit log of changes are worth asking about.
6. Light ITSM, if you need it
Many teams need incidents, requests, approvals and a way to link problems and changes, and nothing more. What matters is starting light, not being forced into a full process model. See ITSM lite for what a lighter approach looks like.
7. Automation and the API
Look for rules that act on events, such as a new ticket or an SLA warning, and an API with webhooks so you can connect other systems. Ask if webhooks are signed, how failures are retried and if the API is included in the plan or sold separately.
8. AI assist
If you want AI, ask what it does, when it runs, what data leaves the system, whether the vendor trains models on your tickets, and if a person reviews its output. The AI guide has a checklist.
9. Pricing and trial
Work out the monthly cost for your real agent count, including add-ons, and ask if requesters count as paid seats. A trial without a card, run on real requests, tells you more than a demo. The help desk cost calculator shows what a ticket costs your team in agent time, which puts a monthly price in context.
10. Getting in and out
Ask how you bring contacts and history in, how you take your data out, where it is stored and what the terms say about deletion.
What to skip
- Asset management and a configuration database, unless you will keep them current.
- A long list of integrations, if the API covers the two you need.
- Elaborate workflow designers before you have ten real tickets to design against.
Where ActiveQ fits
We built ActiveQ to cover most of this list for IT teams and MSPs: a client portal, SLAs with business hours, light ITSM, AI assist that a person controls, and an API with signed webhooks. It has two channels, the portal and email. It costs $79.99 a month for 1 to 3 agents, $149.99 for 4 to 8 and $19.99 for each agent above 8, with a 14-day trial and no card required. Sign-up and billing are for businesses in the United States. See internal IT, MSPs and pricing.