Chalk vs HappyFox Help Desk

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 HappyFox Help Desk

• 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.

Where Chalk pulls ahead

• ✓ Chalk does not charge per agent or per seat. Self-hosting is free forever under AGPL-3.0, as a single binary with every module included, so adding a technician or a building never changes the bill.
• ✓ Chalk syncs your SIS directly — PowerSchool, Infinite Campus, Skyward, and OneRoster 1.1, plus Clever and ClassLink import — so students, staff, schools, and enrollments are in the system before the first ticket is filed. HappyFox says outright that it is not an SIS replacement.
• ✓ The help desk and the device inventory are the same system in Chalk, so a ticket already knows the student, their building, and every device assigned to them — with no per-tier gate on the asset side.
• ✓ ChromeOS write-back, not just ingest: OU moves, disable, deprovision, and annotated fields, all planned as a diff you preview and approve, with typed confirmation on destructive actions. HappyFox reads device data from Google Endpoint and Jamf into a ticket.
• ✓ The whole 1:1 loop is native — due dates and overdues, e-signature at the desk, loaners, lost and stolen with police report, attestation campaigns, and repairs that consume parts out of stock.
• ✓ Purchase orders, warranty tracked on the device, on the ticket, and in the refresh runway, and funding sources as a managed list, so a grant audit is a report rather than spreadsheet archaeology.
• ✓ Chalk is itself a SAML 2.0 and OIDC identity provider with a student portal, QR badges, and outward provisioning to Google, AD, and Entra.

Sources

Claims about HappyFox Help Desk above are drawn from these pages, checked when this comparison was written. If something has changed, tell us and we will correct it.

• HappyFox — pricing model, agent cap on Basic, annual discount, unlimited-agent option
• HappyFox — agent-based pricing page
• HappyFox blog — pricing update announcing Basic $24, Team $49, Pro $99 per agent
• HappyFox — education solutions, 'the service layer, not an SIS or MDM replacement'
• HappyFox Service Desk — asset management feature page