Service desk

Your Kaseya Help Desk Is Going Away. What Should Your MSP Build Next?

Kaseya Help Desk as a Service is being discontinued. Use the transition to build a service desk around your MSP, your customers and the way you want to deliver support, not just to swap suppliers.

Which service desk model fits your MSP?

Two questions, answered from the model comparison in this guide.

147days until Kaseya Help Desk as a Service is discontinued on 14 April 2027

Who should set your service desk's day-to-day priorities?

Who should recruit and employ the engineers?

Model C

A dedicated service desk built for your MSP

Your own team works exclusively for your MSP inside your PSA, RMM and processes. You select the people and set priorities; your partner handles recruitment and employment.

  • You select candidates
  • Your MSP sets priorities
  • Partner handles employment

A quick steer to start the conversation, not a verdict.

Compare the models ↓
3Service desk models to compare before you choose
5Operating disciplines that make a service desk improve
7Performance areas to baseline and track
5Phases to plan your transition before the deadline
The short version
  • Kaseya Help Desk as a Service is scheduled to end on 14 April 2027. Treat that date as a delivery deadline, not the starting point for recruitment.
  • Use the transition to review the model, not just the supplier: control, consistency, visibility, accountability and improvement.
  • You have three broad options: another shared help desk, an internal service desk, or a dedicated team that works inside your PSA, RMM and processes.
  • Start with the work, not the team size: ticket demand, the L1 and L2 split, coverage and skills.
  • Set a performance baseline, then balance responsiveness, resolution quality, efficiency and customer experience.

Kaseya Help Desk as a Service (HDaaS) is scheduled to be discontinued on 14 April 2027. For MSPs relying on the service, the immediate priority is finding a way to maintain support without disrupting customers or existing service commitments.

Tickets still need to be answered. SLAs still need to be met. And your technical team cannot simply absorb an additional workload while you work out what comes next.

But there’s a bigger decision to make.

Do you find another outsourced help desk to take over the existing workload or use this transition to build a service desk around your MSP, your customers and the way you want to deliver support?

Replacing a service is relatively straightforward. Building a better operating model requires a little more thought.

Don’t carry yesterday’s service desk into tomorrow

Finding another provider might seem like the safest option. You already know what your existing arrangement delivers, so finding something comparable appears to minimise disruption.

But this approach carries a risk: you could reproduce the same limitations with a different supplier.

Before moving your tickets elsewhere, consider what your existing arrangement actually delivers.

How does your current arrangement measure up?

Answer for the help desk you rely on today. Nothing you select is stored or sent anywhere.

0of 5 delivered
  • ControlHow much influence do you have over the people handling your customers’ requests?
  • ConsistencyDo support personnel develop lasting knowledge of your clients, their environments and recurring issues?
  • VisibilityCan you see how work is being prioritised, handled and escalated?
  • AccountabilityWho owns the customer experience when a ticket moves between different people?
  • ImprovementDoes your support arrangement help you identify recurring problems and improve the underlying processes?

Answer all five to see where your next service desk needs to do better.

Ticket closure and service quality aren’t the same thing. A provider might meet an agreed support scope without giving your MSP the visibility, continuity or operational ownership it needs.

The transition is your opportunity to review the model, not just the supplier.

Decide what you want to build

MSPs don’t all need the same service desk structure. A business supporting 300 users across a relatively standard Microsoft 365 environment will have different requirements from one managing complex infrastructure, networking and security environments.

Your next service desk should reflect your actual workload, not an arbitrary team size or a generic support package.

There are three broad models worth considering.

Model A: Another shared outsourced help desk

You purchase access to an external support function. Tickets are handled within the provider’s service framework, according to an agreed scope and service arrangement.

This can be useful when you need an external function to absorb support demand without directly recruiting and managing individual engineers.

The provider typically manages staffing and service delivery, while visibility, customer familiarity, integration, and operational control depend on its model and your agreement.

Model B: An entirely internal service desk

You recruit, employ and manage your own engineers locally.

This gives you direct control over recruitment, team structure, responsibilities and daily operations. It can also create a strong foundation for internal knowledge and customer relationships.

The trade-off is the cost and management responsibility of recruiting, retaining and supporting technical staff.

Model C: A dedicated service desk built for your MSP

You build a dedicated team of embedded engineers who work exclusively for your MSP.

They operate within your PSA, RMM, documentation and service processes. You select candidates and manage operational priorities, while your staffing partner handles recruitment, employment, infrastructure and ongoing people support.

This lets you combine operational ownership with the added capacity, capability and predictable performance of a dedicated team.

Highlight a model to compare

What you’re evaluatingShared outsourced help deskInternal service deskDedicated embedded team
Staffing arrangementProvider-managed functionDirect employeesDedicated team members through a staffing partner
Day-to-day prioritiesGoverned by service arrangementYour MSPYour MSP
RecruitmentProviderYour MSPYou select candidates, partner manages recruitment
Customer knowledgeDepends on provider modelBuilds internallyBuilds within your dedicated team
Systems and processesDepends on provider integrationYour MSP’sYour MSP’s
Employment administrationProviderYour MSPStaffing partner
Operational ownershipDefined by service agreementYour MSPYour MSP

Model C: you keep operational ownership and choose your team, while your partner handles recruitment and employment.

The important thing is to understand what each arrangement gives you, what it leaves you responsible for and whether it supports the kind of MSP you want to become.

For a closer look at the trade-offs, read our comparison of a dedicated team and an outsourced help desk.

Design your service desk around demand

A common mistake when building a service desk is starting with the number of people you think you need.

Start with the work instead.

Your ticket volume, issue complexity, customer expectations and escalation patterns should determine your team structure.

Begin with four areas of analysis.

A

Understand your ticket demand

Start by reviewing 60 to 90 days of historical ticket data, where available. Extend the review period if seasonal demand or unusual peaks could affect the picture.

Look at:

  • Average and peak daily ticket volumes
  • Tickets by customer, category and priority
  • Common recurring issues
  • Average handling and resolution times
  • Tickets reopened or transferred between engineers
  • Backlogs and periods of high demand

This helps establish how much support capacity you need and where that capacity should sit.

B

Separate L1 and L2 responsibilities

Your service desk should have a clear distinction between initial support, more advanced troubleshooting and escalation to senior specialists.

  1. L1
    First-line supportTypical responsibilities

    Initial diagnosis, routine troubleshooting, password and access requests, basic Microsoft 365 support, ticket logging and prioritisation

    What to establish

    Which issues can be resolved at first contact?

  2. L2
    Second-line supportTypical responsibilities

    Advanced troubleshooting, systems and network issues, Microsoft 365 administration, complex incidents and escalations

    What to establish

    Which issues require deeper technical expertise?

    See what an L2 Engineer covers →
  3. Senior
    Senior engineeringTypical responsibilities

    Complex infrastructure issues, architectural decisions, specialist troubleshooting and high-risk incidents

    What to establish

    What should remain with your senior technical team?

Your MSP's support scope, technical environment, access permissions and escalation policies should determine the final division of work. Resolve issues at the right level without unnecessary escalations or exposing customers to inexperienced support.

C

Establish coverage requirements

Your service desk needs to reflect when your customers expect support, not simply when your engineers are available.

Assess:

  • Contractual support hours and SLA commitments
  • Time-sensitive and high-priority incidents
  • Peak support periods
  • Leave coverage and staff availability
  • After-hours and weekend requirements

This will help you determine whether you need standard business-hours coverage, extended coverage or a more structured shift arrangement.

D

Identify the skills your environment requires

Build your recruitment requirements around your technology stack and customer base.

Consider your requirements across:

  • Microsoft 365 and cloud administration
  • Windows and server environments
  • Networking and infrastructure
  • Endpoint management and remote monitoring
  • Security tools and access management
  • PSA and RMM platforms
  • Documentation and knowledge management

A candidate who looks impressive on paper isn’t necessarily the right candidate for your service desk.

Technical capability, communication, problem-solving and the ability to work within your customers’ environments are all essential.

Build a service desk that improves as it operates

A service desk shouldn’t be designed around ticket throughput alone.

Every support request provides information about your customers, their environments and the quality of your internal processes.

If the same problem appears repeatedly, closing each ticket without addressing the underlying cause simply creates more work.

Your next service desk should be designed to capture and use that information.

Five operational disciplines deserve attention.

  1. 1

    Knowledge management

    Maintain accurate customer documentation, technical notes, troubleshooting procedures and knowledge base articles. Make it easier for engineers to resolve recurring issues without starting from scratch.

  2. 2

    Escalation management

    Establish clear escalation criteria, ownership and handover procedures. Complex tickets should reach the right technical resource with sufficient context, rather than bouncing between teams.

  3. 3

    Problem management

    Identify recurring incidents and investigate their underlying causes. Focus on finding permanent solutions that prevent the same problems from continuing to surface.

  4. 4

    Automation and workflow improvement

    Identify repetitive tasks that could be automated, standardised or simplified. Ticket routing, routine administration and recurring support processes can all offer opportunities for improvement.

  5. 5

    Performance management

    Monitor service quality. Review first-call resolution, SLA performance, backlog, reopened tickets, customer satisfaction and escalation patterns together.

These disciplines help turn a service desk from a reactive ticket-processing function into a source of operational intelligence.

Understand what good service desk performance looks like

A new staffing arrangement won’t improve your service desk on its own. You need a way to establish whether it’s delivering the outcomes your MSP expects.

Start by creating a baseline using your current performance data. Then establish targets around the outcomes you want to improve.

Performance areaWhat to measureWhat it tells you
  • ResponsivenessFirst response time

    Shows how quickly customers receive an initial acknowledgement

  • ResolutionFirst-call resolution rate

    Indicates how effectively issues are resolved without further escalation

  • Service commitmentsSLA attainment

    Measures performance against agreed customer commitments

  • WorkloadTicket backlog and ageing

    Highlights capacity constraints and unresolved demand

  • QualityReopened tickets and repeat incidents

    Helps identify incomplete fixes and recurring problems

  • Customer experienceCustomer satisfaction and feedback

    Shows how customers perceive the support they receive

  • Team efficiencyTicket distribution and utilisation

    Helps identify workload imbalances and resource constraints

Don’t optimise one metric at the expense of everything else. For example, pushing engineers to close more tickets can lead to rushed troubleshooting, incomplete documentation and repeat incidents.

Responsiveness
Resolution quality
Efficiency
Customer experience

A good service desk balances responsiveness, resolution quality, efficiency and customer experience.

What does this look like in practice?

Future IT Services, an Australian MSP based in Far North Queensland, faced growing operational demands as its business expanded.

One of its priorities was to reduce the administrative burden on its technical team, improve first-call resolution and maintain service quality while creating capacity for growth.

Dijital Team helped Future IT recruit and integrate two dedicated Sri Lankan service desk team members.

The team was trained on Future IT’s tools and processes and took on first-level support responsibilities, including ticket handling and routine support work. This helped free existing technical resources to focus more time on complex issues.

Future IT Services

First-call resolution

Before
70%
After
Nearly 87%

First-call resolution rate after two dedicated service desk team members took on first-level support.

Up to 250additional users of support capacity, without overburdening the existing technical team
150 usersadded by Future IT within six months

The reported results:

  • First-call resolution: Improved from 70% to nearly 87%
  • Service quality: Client satisfaction increased, with faster response times and better adherence to service-level agreements
  • Additional capacity: The dedicated team created capacity to support up to 250 additional users without overburdening the existing technical team
  • Business growth: Within six months, Future IT expanded by 150 users, capitalising on new business opportunities while maintaining high service standards

The engagement demonstrates what can happen when dedicated service desk resources are recruited around an MSP’s requirements and integrated into its existing operation.

Take a closer look at how Future IT improved first-call resolution and built capacity for growth.

Plan your Kaseya Help Desk transition before the deadline

The April 2027 discontinuation date should be treated as a delivery deadline, not the starting point for recruitment.

Building a new service desk involves more than finding available engineers. You need to understand the existing workload, define the roles, select the right people, transfer knowledge and establish performance expectations.

For guidance on the decisions and preparation involved, read The MSP’s Kaseya Help Desk Transition Planning Guide.

Use this sequence to organise your transition.

Your transition plan

Tick tasks off as you go. Nothing you tick is stored or sent anywhere.

0of 25 tasks done
  1. Phase 1

    Assess

    0/5
  2. Phase 2

    Design

    0/5
  3. Phase 3

    Recruit and prepare

    0/5
  4. Phase 4

    Integrate and validate

    0/5
  5. Phase 5

    Stabilise and improve

    0/5

Ready to put your transition plan into action? Use the MSP Service Desk Transition Checklist & Worksheets to organise key tasks, document requirements and track progress.

Build a service desk that belongs to your MSP

Kaseya Help Desk as a Service’s discontinuation creates a decision point for every MSP that relies on it.

You can replace the existing arrangement with another outsourced support function. Or you can take a closer look at your ticket demand, technical capacity, customer expectations and long-term operating requirements, then build a service desk designed around them.

A dedicated, embedded team offers a practical way to do that.

With Dijital Team, your MSP selects its dedicated engineers and manages their day-to-day operational priorities. They work within your technology stack, follow your processes and develop knowledge of your customers over time.

Dijital Team supports the employment environment around them, including recruitment, onboarding, HR, payroll, infrastructure and ongoing people management.

  • ISO 27001Certified information security management
  • 120+MSPs and ITSPs supported
  • Your PSA and RMMEngineers work inside your tools and processes

Service desk team members

Dedicated professionals for first-line and second-line support, recruited around your stack.

Explore the roles →

L2 Engineers

Advanced troubleshooting, escalations and Microsoft 365 administration within your processes.

L2 Engineers →

L3 Engineers

Complex infrastructure work and specialist escalations alongside your senior team.

L3 Engineers →

Frequently asked questions

Kaseya has advised customers that Help Desk as a Service will be fully discontinued on 14 April 2027. MSPs relying on the service should plan their replacement arrangements and knowledge transfer well ahead of that date.

MSPs should assess their current ticket volumes, L1 and L2 requirements, customer support hours, SLAs, technology stack, escalation procedures and internal engineering capacity. These requirements should determine the next service desk model rather than simply recreating the existing arrangement.

A shared outsourced help desk provides access to an external support function operating under an agreed service arrangement. A dedicated service desk team works exclusively for one MSP, using its systems and processes and developing familiarity with its customers. The degree of operational control depends on the specific staffing and service model.

Yes. A dedicated team can be recruited around an MSP’s required technical capabilities, including first-line and second-line support. The responsibilities assigned to each engineer should reflect their experience, the MSP's support scope and its escalation policies.

Start with a performance baseline and monitor first response time, first-call resolution, SLA attainment, ticket backlog, reopened incidents, escalation rates and customer satisfaction. Reviewing these measures together provides a more complete picture than relying on ticket closure numbers alone.

Next step

Don’t just replace your Kaseya Help Desk. Build a service desk that’s yours.

See how Dijital Team can build a dedicated service desk around your MSP. Start with a Help Desk Transition Assessment: a focused session with Dijital Team to map your current support model and what your post-Kaseya service desk could look like.

  • You select your team and set priorities
  • Engineers work inside your PSA and RMM
  • ISO 27001 certified
  • Trusted by 120+ MSPs and ITSPs
Book a Help Desk Transition Assessment →