HappyFox Help Desk vs Lansweeper

HappyFox Help Desk

A polished multi-channel help desk sold per agent, with a genuine education landing page and Google Endpoint and Jamf integrations — but the vendor says plainly it is the service layer, not an SIS or an MDM.

Where HappyFox Help Desk is strong

• ● A mature, well-designed ticketing product with the full table stakes done properly: email-to-ticket, self-service portal, knowledge base, SLAs, canned responses, automation rules, and reporting.
• ● Real multi-department structure — IT, Facilities, HR, and Student Services can hold separate queues with routing by campus and issue type while leadership keeps one view across them.
• ● Integrations with Google Endpoint Management and Jamf that attach device data to a ticket, so a technician sees the machine alongside the request.
• ● An unlimited-agent pricing model as an alternative to per-seat, which is unusual and genuinely useful for a district where lots of people touch tickets occasionally.
• ● Named K-12 and higher-ed deployments on the vendor's education page, including a district handling 25,000+ tickets a year — this is not a corporate tool with an education stock photo bolted on.
• ● Asset management exists in the HappyFox product family, tracking assets across IT, facilities, and HR from procurement to retirement.

What to check before you buy

• Hosted SaaS only. There is no self-hosted or on-premises edition, so the software cannot be run on district infrastructure or inspected independently.

  Basis: HappyFox publishes only cloud plans; no self-host or source distribution appears anywhere on the vendor site.

• Asset management is documented as a HappyFox Service Desk feature, and on the help desk side asset tracking lands on the higher-priced tier rather than the entry plan — so the districts most likely to be price-sensitive are the ones who do not get it.

  Basis: HappyFox's asset management feature page is published under Service Desk; the vendor's pricing announcement puts the top per-agent tier at $99 per agent.

• Per-agent pricing is the wrong axis for a district. A K-12 IT shop has a handful of technicians and tens of thousands of devices, so the bill is set by the number you have least of while the number you have most of goes untracked.

  Basis: Vendor pricing is stated as a monthly price per support agent actively managing tickets.

• The vendor states directly that HappyFox is the service layer and not an SIS or MDM replacement. Device and roster truth has to live somewhere else, and you maintain the seam between the two systems.

  Basis: Stated in those terms on HappyFox's education solutions page.

• No SIS or rostering integration — no OneRoster, Clever, ClassLink, PowerSchool, Infinite Campus, or Skyward. Users arrive from a directory, not from the system of record, so a mid-year transfer or withdrawal is invisible.

  Basis: None appear on HappyFox's education page, integrations listing, or pricing page.

• No 1:1 device circulation: no check-out to a student with a due date, no overdue workflow, no parent-signed agreement, no loaner pool, and no lost or stolen lifecycle.

  Basis: Absent from the published asset management feature page, which is framed around lifecycle from procurement to retirement rather than custody.

• No student fee assessment, no family balances, no purchase orders, no repair records consuming parts stock, and no funding-source tracking for ESSER, Title, or E-Rate money.

  Basis: None of these concepts appear in HappyFox's published product documentation.

• It consumes SSO but is not an identity provider — it cannot issue SAML or OIDC to your other vendors, and it cannot give students a portal identity.

  Basis: SSO is described as sign-in into HappyFox; no IdP capability is published.

How Chalk compares with HappyFox Help Desk →

Lansweeper

The strongest network discovery engine in this comparison — it will find every device on your wire, including the ones nobody told it about, and it will not know that any of them belongs to a seventh grader.

Where Lansweeper is strong

• ● Genuine network discovery, which almost nothing else in this category has: agentless scanning of Windows over WMI, Linux and macOS over SSH, and printers, switches, routers, firewalls and NAS over SNMP, so the inventory includes devices no one ever entered.
• ● A passive traffic sensor that discovers assets from network communications, catching devices that active scanning misses entirely — the closest thing to a real answer for shadow IT and unmanaged OT gear.
• ● An IT Agent for Windows, Linux and macOS endpoints that rarely touch the LAN, and Cloud Discovery across Azure, Intune, Microsoft 365 and Entra ID, AWS and GCP — with a reconciliation engine that merges the same device seen through several sources into one asset record instead of three.
• ● Vulnerability detection built on CPE correlation and VulnCheck, with CVSS severity and patch status against the software and OS actually in your inventory, alongside hardware and software lifecycle tracking for end-of-sale and end-of-support dates.
• ● Deployment packages in Lansweeper Classic — install software, run scripts and make remote changes on Windows machines from the same console that inventoried them.
• ● A full built-in help desk in Classic: tickets from the web console, email, API or import, dispatching rules, SLAs, teams, internal notes and a knowledge base.

What to check before you buy

• Lansweeper is two products with a documented feature gap between them — Lansweeper Platform in the cloud and Lansweeper Classic on-premises — and which capabilities you get depends on which one you deploy.

  Basis: Vendor's own 'Comparing Lansweeper Platform and Lansweeper Classic' documentation page, which lists discovery targets and features per product.

• ChromeOS discovery is a Lansweeper Classic capability. In the newer Lansweeper Platform the vendor's comparison table marks Chrome OS as 'Planned (Cloud Discovery)'. For a district whose fleet is Chromebooks, that is the whole fleet sitting on the older product.

  Basis: Vendor comparison table lists Chrome OS as supported in Classic scanning and Planned for Lansweeper Platform.

• Even in Classic, ChromeOS scanning is work you do yourself: your license must support Chrome OS scanning, and you build a Google Cloud project, enable the Admin SDK, create a service account and grant it scopes before a single Chromebook appears.

  Basis: Vendor's 'Chrome OS scanning requirements' documentation page.

• The help desk is licensed per agent. Unlimited users can file tickets, but exactly one agent license is included, and every additional technician who answers tickets is a paid seat at $120 per year.

  Basis: Vendor's 'Manage helpdesk agents' documentation plus the listed price in Lansweeper's own online store.

• That help desk belongs to Classic. The cloud Platform documentation covers no ticketing module of its own — service management appears as connectors to Jira Service Management, ConnectWise, Zendesk and Freshservice, meaning a second vendor.

  Basis: Lansweeper's documentation index places every help-desk article under Classic, and lists ITSM tools as integrations under Platform.

• The asset meter has teeth: reaching your licensed asset limit can stop scanning of new and existing assets until you delete assets or upgrade.

  Basis: Vendor's 'Manage your licensed asset limit' documentation page.

• No student, guardian or enrollment concepts, and no SIS or rostering connectors — the identity sources documented are Active Directory, Entra ID, Intune and Microsoft 365. Students arrive by CSV, if at all.

  Basis: Absent from Lansweeper's documentation index, which covers directory and cloud identity sources only.

• Nothing models the 1:1 program itself: no device agreement, no parent signature, no fee for a cracked screen, no family balance, and no funding-source dimension for ESSER, Title or E-Rate reporting.

  Basis: Absent from the vendor's documented feature set, which is discovery, inventory, risk and deployment.

How Chalk compares with Lansweeper →

The third option: Chalk

If you are weighing HappyFox Help Desk against Lansweeper, Chalk belongs on the same shortlist. It is the open-source K-12 IT stack: device inventory that fills itself in from Google Admin, Intune, and Jamf against a roster synced from your SIS, a 1:1 circulation desk with agreements and fees, repairs with parts and costs, a help desk that already knows who is asking, and a built-in SAML/OIDC identity provider.

• ✓ Self-host it free forever under AGPL-3.0 — the entire feature set, one binary, your infrastructure — or use the hosted version, priced by fleet size with no per-seat or per-student fees and the price ladder published.
• ✓ Built only for K-12: students, buildings, custody, funding sources, and ChromeOS auto-update expiration are native concepts, not custom fields.
• ✓ Writes back to Google Admin as a reviewed diff — every OU move, disable, and deprovision previewed before it executes — and serves a OneRoster 1.1 API so other district systems can pull the roster from Chalk.
• ✓ Fees are assessed and tracked without touching payment cards, keeping the asset system out of your PCI scope.