Kaseya is discontinuing Help Desk as a Service (HDaaS) on 14 April 2027. MSPs that use it do not need to change their PSA, RMM or documentation tools to replace it. A white label helpdesk works inside the tools an MSP already runs, such as Autotask, Datto RMM and IT Glue, and under the MSP's own brand. The only thing that changes is who picks up the ticket.
That's the short answer if you're looking for a Kaseya Help Desk alternative. The longer one matters because of what the partner email left out.
If your clients' tickets have been going to Kaseya's desk, the notice probably reached you around the middle of October. Since then, a stream of providers has told you what to do next: build an offshore team of your own, buy AI software that answers tickets, or move to a different PSA. Every one of those is a bigger change than the one Kaseya has forced on you.
My view is simpler. Kaseya is closing the desk, not the stack. Keep the stack and replace the desk.
What is Kaseya actually shutting down?
Kaseya Help Desk as a Service is a white-labelled, remote support desk that answered end-user tickets on behalf of MSPs. Kaseya launched it in November 2023 and has told partners it will end on 14 April 2027. Kaseya has not published a reason. The software MSPs use alongside it, including Autotask, Kaseya BMS, Datto RMM, VSA and IT Glue, is not part of the shutdown.
Kaseya announced the service on 2 November 2023 at DattoCon in Miami. The 14 April 2027 date comes from Kaseya's email to partners, reported independently by several providers. There's no public statement from Kaseya, and nobody outside the company knows the reason or what happens to contracts that run past April. If yours does, ask your account manager in writing.
Under Kaseya's Help Desk Services Terms of Use, the service had clear edges:
- It covered end-user devices and common applications. Shared servers and networks stayed with you.
- It only worked if you ran a Kaseya RMM, meaning Datto RMM or VSA.
- 24/7 cover was an option on the order. Out-of-hours work without it was billed at time and materials.
- Per-ticket pricing needed 400 or more devices, and on those plans Kaseya could hand a ticket back to you after 60 minutes.
One more clause is worth reading before you do anything hasty: a three-year non-solicitation clause with damages of the greater of $150,000 or 1.5 times salary and benefits. Thinking of hiring the engineer who has been answering your clients' calls? Talk to a lawyer first.
Your Autotask, Datto RMM and IT Glue aren't going anywhere
What goes away on 14 April 2027 is people: the engineers answering L1 and L2 end-user tickets under your brand, the phone line they answered, any 24/7 cover you bought as an add-on, and the monthly reporting.
What stays is everything else. Your PSA and its ticket history. Your RMM and its agents. Your IT Glue documentation, your client contracts, your SLAs and your brand.
You've also done the hard part already: RMM agents on every eligible device, authorised-user and device lists in your PSA, service documentation in IT Glue. That groundwork transfers to a new desk as it is.
So I'd push back on anyone telling you this is the moment to change your PSA. You might want to one day. Doing it in 21 weeks, with Christmas in the middle, while also replacing the people who answer your phones, is how service slips and clients notice.
How does a white label helpdesk work inside Autotask and Datto RMM?
A white label helpdesk is a support team that works inside an MSP's own tools and under its brand, so the MSP's clients see only the MSP. Engineers log in to the MSP's PSA as named users, work tickets in the MSP's queues, and record notes and time there. The MSP keeps the ticket history, the client relationship and the tools.
The mechanism is access, not migration. In a Kaseya stack it looks like this:
| Tool | What the desk needs it for | How access is set up |
|---|---|---|
| Autotask PSA | Working tickets, logging time, escalating | Each engineer is a named resource with a restricted security level, copied from a system level such as Service Desk User. Connected tooling uses a separate API-only user with its own security level. |
| Kaseya BMS | The same job, for VSA-centred MSPs | Named users with scoped roles. |
| Datto RMM or VSA | Remote access and alert triage | Engineer accounts scoped to the right sites, with remote control rights. |
| IT Glue | Client documentation, passwords and runbooks | Read access for engineers. IT Glue documents and passwords can also appear inside the Autotask ticket through Kaseya's own integration. |
One detail tells you a lot about a provider. Autotask's default API User security level can see all your data, including internal costs. A careful provider asks for a restricted copy. A careful MSP insists on it.
The ticket trail stays in your PSA: notes, time entries, escalations. Nothing lives in a second system you can't see. To fence the outside desk to particular clients, Autotask has a Co-managed Help Desk licence type for external users limited to named organisations. One honest cost: extra named users in your PSA or RMM may carry a licence fee.
What if you run ConnectWise or HaloPSA instead?
The same model applies, which is the point. In ConnectWise PSA, engineers work your service boards, such as Help Desk, After Hours or Emergency, as named members, with a separate API member for tooling. In HaloPSA, tooling connects through an API-only agent and an API application using OAuth 2.0, with limited permissions instead of an admin role.
Kaseya's desk could never serve those MSPs, because it needed a Kaseya RMM. A desk that follows your tools also survives your next tools decision: move from Autotask to HaloPSA in 2028 and you keep the same people. That's the opposite of what has just happened.
On VSA 9? There's a second date. Kaseya's VSA 9 end-of-life notice says VSA 9 stops working on 31 August 2027, and customers must move to Datto RMM or VSA 10 before then. A new desk that has to learn a new RMM four months after it starts is a risk worth naming now.
How do you choose a Kaseya Help Desk alternative?
The least disruptive Kaseya Help Desk alternative is a white label helpdesk that works inside your existing Kaseya tools, because nothing has to be migrated. Whoever you talk to, ask these before you sign:
- Which PSA, RMM and documentation tools do your engineers work in today, for live clients?
- Is 24/7 cover included, or priced on top?
- What's out of scope: servers, networks, line-of-business apps?
- When can a ticket be handed back to us, and how?
- What permission level will you ask for in our PSA, and why?
- Where are your engineers based, and how are they vetted?
- What are the exit terms, and is there a non-solicitation clause?
After this autumn, every MSP should know how it would leave a provider before it joins one.
How long does it take to replace Kaseya's help desk?
From 18 November 2026 there are 21 weeks until Kaseya Help Desk as a Service ends on 14 April 2027, and the Christmas fortnight sits inside them. Working back from the deadline, an MSP should choose a provider by the end of January 2027 and run both desks side by side in March. Here is a plan that leaves two weeks of buffer:
- Now to mid-December 2026: confirm your contract end date with Kaseya in writing, pull 90 days of ticket data by client and category, and draw up a shortlist.
- January 2027: choose a provider, agree scope and SLAs, and sign.
- February 2027: grant tool access, share documentation, and have the new engineers shadow live tickets.
- March 2027: run both desks in parallel on a few clients, then widen it.
- By 31 March 2027: full cut-over.
The set-up itself is quick. Our target is five days from sign-off to a desk taking tickets. The parallel run is the part not to rush, because that's where you find the runbook nobody wrote down.
Where Supportwave fits
I don't think a vendor's product decision should be able to remove an MSP's support capacity with one email. Capacity should be a decision, not a gamble.
Supportwave White Label Helpdesk is 24/7 user and application support delivered under your brand, inside your tools. Our engineers already work in Autotask, Datto RMM and IT Glue, and in more than 100 other platforms, so a Kaseya stack needs nothing new. The desk starts through email and PSA workflows, or through native integrations with HaloPSA, ConnectWise, Autotask and ServiceNow, on a fixed monthly subscription from 100 tickets a month. We're a channel-only IT services provider: we sell no hardware, software licences or cloud, and we never compete for your clients. When a ticket needs someone on site, Smart Hands covers it. When volume grows, dedicated engineers can join your team.
For one client, an iGaming business with a complex multi-region set-up, we put a dedicated 24/7/365 helpdesk of four engineers live in eight days.
If your clients' tickets go to Kaseya's desk today, send us 90 days of ticket data. We'll come back with a scoped plan and a fixed monthly price before the January rush. For the wider picture, our guides to the white label helpdesk and 24/7 support for MSPs cover the rest.
FAQ
When is Kaseya Help Desk as a Service being discontinued?
Kaseya has told partners that Help Desk as a Service (HDaaS) will end on 14 April 2027. The notice went to partners by email around mid-October 2026, and several providers have reported the same date independently. Kaseya has not published a public statement or a reason, so MSPs should confirm their own contract end date with Kaseya in writing.
Do MSPs have to leave Autotask or Datto RMM when Kaseya's help desk closes?
No. Kaseya is ending the help desk service on 14 April 2027, not the software. An MSP can keep Autotask or Kaseya BMS, Datto RMM or VSA, and IT Glue, and give a replacement helpdesk team access to them through named user accounts with restricted permissions. Tickets, documentation and client history stay where they are.
What is a white label helpdesk?
A white label helpdesk is a support team that works inside an MSP's own tools and under its brand, so the MSP's clients see only the MSP. Engineers log in to the MSP's PSA as named users, work tickets in the MSP's queues, and record notes and time there. The MSP keeps the ticket history, the client relationship and the tools.
How long does it take to replace Kaseya's help desk?
Working back from 14 April 2027, an MSP should choose a provider by the end of January 2027, give the new desk tool access and documentation in February, and run both desks in parallel during March. That leaves two weeks of buffer. Setting up a white label helpdesk takes days once access is granted; the parallel run is what needs time.
Talk to Supportwave →



