The choice of an IT service model directly affects your costs, the pace of work, and the company's resilience to outages. In this article we explain IT helpdesk — how to set it up in your company without jargon — so the board, the CFO and the owner have concrete arguments in hand to make a decision.
Build or buy a helpdesk that really supports your people.
Support tiers (L1–L3)
This section frames the topic "Support tiers (L1–L3)" in the context of IT helpdesk — how to set it up in your company. We approach it from the business side — what concrete value or risk it brings to the company.
What you gain
- Predictable monthly cost instead of irregular spend on hardware, people and training.
- Access to a team of specialists (network, cloud, security) under a single contract.
- Faster response to incidents thanks to defined processes and ticketing tools.
Most common mistakes
- A contract without a precisely defined SLA (response time ≠ resolution time).
- No clauses on knowledge and password transfer at the end of the engagement.
- "All-in" pricing without an hour cap — extra fees for every larger project later.
Ticketing tools
Choosing a tool is usually choosing an ecosystem. Evaluate not only feature-table checkboxes but also the vendor's longevity, the quality of support in Poland, and the cost of integrating with what you already have.
- Ask about the product roadmap and update cadence.
- Check whether support is available in your language and time zone.
- Verify a 3-year TCO (licences + rollout + operations).
- Ask for references from companies of a similar profile and size.
In many cases it is better to pick the second-best tool that you will actually finish rolling out than the best one that stalls in pilot.
KPIs and metrics
SLA (Service Level Agreement) is not marketing — it is a specific contract clause saying: "we will respond within this time" and "we will resolve within this time". These two parameters are response time and resolution time — they are different and you must see both in the contract.
- Response time — from ticket to work starting. Market standard: 15 minutes to 2 hours in business hours.
- Resolution time — from work starting to solution. Depends on incident priority (P1–P4).
- Availability — 99.5% monthly means about 3.5 hours of acceptable downtime.
- Contract penalties — without them, an SLA is a declaration, not a commitment.
How to verify the SLA
Require monthly reports from the provider's ticketing system. If they cannot show you in a table how many tickets, in what times and with what priority they closed — the SLA exists only on paper.
Key takeaways
- Predictable monthly cost instead of irregular spend on hardware, people and training.
- A contract without a precisely defined SLA (response time ≠ resolution time).
- Treat the topic of "IT helpdesk — how to set it up in your company" as a project, not a one-off purchase — the best results come from a step-by-step approach.
Frequently asked questions
Considering IT outsourcing for your company?
Book a free 30-minute consultation. We will walk through your current IT service model, point out the weak spots and show what working with MAD System would look like — with no commitment.