NetPulse Solutions (real case — data altered under NDA) is an IT services company in Porto with 18 employees, providing technical support, infrastructure management and managed services to 45 business clients. With SLA contracts promising response times of 30 minutes to 4 hours depending on severity, the company faced an increasingly serious problem: it could not meet its own promises. Tickets arrived by email, phone and direct messages, with no centralised system. Frustration was growing on both sides — overloaded technicians and dissatisfied clients. This case shows how a helpdesk platform with automated SLA transformed the operation.
Organised Chaos: When Everything Is Urgent, Nothing Is a Priority
NetPulse had grown organically over 8 years. What started as a two-technician company was now an 18-person operation — but the processes had not kept pace with the growth. Support requests arrived through five different channels: general email, direct emails to individual technicians, phone calls, WhatsApp messages and, occasionally, in-person client visits to the office.
There was no centralised ticketing system. Technicians managed requests in their own email inboxes, with post-it notes on their monitors and mental lists of priorities. When a technician was on holiday or off sick, their clients were left without support — nobody knew which requests were pending.
The SLA issue was particularly serious. Client contracts specified response times (30 minutes for critical severity, 2 hours for high, 4 hours for medium, 8 hours for low) and resolution times. But without a tracking system, nobody knew whether these SLAs were being met. When a client complained, the response was always reactive — there was no data to prove or refute the claim.
An internal audit we conducted revealed a concerning picture: in the previous 3 months, 34% of critical-severity tickets had exceeded the contractual response time. For high-severity tickets, the breach rate was 41%. Some tickets had simply "vanished" — lost in overflowing email inboxes.
The Numbers Before Intervention
• Monthly tickets: ~420.
• Entry channels: 5 (dispersed, no centralisation).
• SLA compliance rate (critical severity): 66%.
• SLA compliance rate (high severity): 59%.
• Average first response time: 2h 47min (contractual for critical: 30 min).
• Lost/forgotten tickets per month: 8–12.
• CSAT (client satisfaction): 6.1 out of 10.
• Clients lost in the past year due to dissatisfaction: 4 (annual revenue: ~EUR 48,000).
The Solution: Centralised Helpdesk with Intelligent SLA
Component 1: Centralisation of All Channels
The first step was to funnel all requests into a single platform. We configured the helpdesk to receive tickets from all existing channels: emails sent to the general address created tickets automatically; phone calls were logged by the receptionist in a form that created the ticket in seconds; and we implemented a support portal where clients could raise tickets directly, with structured forms by problem type.
Direct emails to technicians were redirected: any email sent to an individual technician with a subject indicating a support request was automatically converted into a ticket and assigned to that technician, but now visible to the entire team. WhatsApp messages were gradually replaced by the portal — a process that took approximately 6 weeks, with active communication to clients about the benefits of the new system.
Each ticket had a unique number, a visible status (Open → In Progress → Awaiting Client → Resolved → Closed) and a complete record of all interactions. For the first time, NetPulse had full visibility over its support operation.
Component 2: Automated SLA Engine
The heart of the solution was the SLA engine. Each client had their SLA contract configured in the system, with the specific response and resolution times for each severity level. When a ticket was created, the system automatically assigned severity based on pre-defined rules (for example: "server down" = critical; "email not working for one user" = high; "new equipment request" = low).
From that moment, the clock started ticking. The system displayed a visual timer for each ticket — green when within the deadline, yellow when approaching the limit, red when in breach. Alerts were sent in cascade: to the assigned technician when 50% of the time had elapsed; to the team leader when 25% remained; to the technical director when the SLA was breached.
The system also implemented automatic escalation. If a critical-severity ticket had not received a first response within 15 minutes (half the 30-minute SLA), it was automatically escalated to the technician with the fewest open tickets. If no technician responded within 20 minutes, the technical director received an automatic phone call.
Is your IT company missing SLAs due to lack of a system?
We implement helpdesks with automated SLA, intelligent escalation and client dashboards. Free diagnostic of your support operation.
See Automation Solutions →Component 3: Real-Time Client Dashboard
The third piece was a dashboard accessible to each client, where they could see in real time all their open tickets, the history of resolved tickets, SLA compliance and service metrics for the last month, quarter and year.
The dashboard included: number of open and resolved tickets, average response and resolution time, SLA compliance rate by severity, and a trend chart showing the evolution of service quality over time. Each ticket could be tracked in real time — the client saw exactly what stage their request was at and who was handling it.
This level of transparency had a transformative effect on client relationships. "What's the status of my ticket?" calls dropped by 75% in the first month. More importantly: when there was a delay or a problem, the client saw it on the dashboard before needing to phone and complain. Transparency built trust, even when the service was not perfect.
Impact on the Technical Team
The transformation was not only external. Internally, the technicians went from a state of chronic stress — not knowing how many tickets they had, which were priorities and whether they were within SLA — to a clear and controlled view of their workload.
The automatic assignment system distributed tickets based on the technician's speciality and current load, preventing one technician from being overloaded while another was available. Technicians gained personal dashboards showing their open tickets, the next to expire and their performance metrics for the month.
The knowledge base integrated into the helpdesk also significantly reduced repetitive tickets. When a client raised a ticket with a common problem, the system automatically suggested resolution articles. In the first quarter, 15% of tickets were resolved by the client themselves through the knowledge base, without technician intervention.
The Results: Before vs. After
After 6 months with the new system:
• SLA compliance rate (critical): from 66% to 97%.
• SLA compliance rate (high): from 59% to 94%.
• Average first response time: from 2h 47min to 18 minutes.
• Lost tickets/month: from 8–12 to 0.
• CSAT: from 6.1 to 8.7.
• Clients lost due to dissatisfaction: 0 in the following 6 months.
• Tickets resolved via knowledge base: 15% (new).
• Client follow-up calls: −75%.
Lessons for IT Services Companies
1. SLA without tracking is an empty promise. If you do not measure, you do not manage. And if you do not manage, you do not deliver. The first step to meeting SLAs is having a system that measures them automatically.
2. Centralisation is not optional. As long as requests arrive through 5 different channels and sit in each technician's email inbox, there will be lost tickets. Centralising does not mean adding bureaucracy — it means making things visible.
3. Transparency sells more than perfection. Clients do not expect there to never be problems. They expect to know what is happening and when it will be resolved. A real-time dashboard answers both questions with no additional effort.
4. The knowledge base is the most underrated automation. Every ticket resolved by the client is a technician freed for problems that genuinely require human intervention. And the client is satisfied with the immediate resolution.
5. The cost of losing a client always exceeds the cost of a helpdesk. NetPulse lost EUR 48,000 in annual revenue from the 4 clients who left. The helpdesk investment was EUR 6,000. The maths is clear.
Conclusion
NetPulse Solutions did not need to hire more technicians, buy more servers or change its service offering. It simply needed to organise what it was already doing — provide visibility, measure what mattered and automate what was possible. The result was a less stressed team, happier clients and zero clients lost to dissatisfaction in the 6 months following implementation.
If your IT services company recognises this scenario — lost tickets, breached SLAs, frustrated clients — the path is clear: centralise, automate and provide visibility. The technology exists, is affordable and pays for itself in weeks.
