HappyFox Help Desk vs Sortly

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 →

Sortly

The friendliest inventory app in this comparison and the easiest to actually start using — built for supply closets and job sites, priced by how many items you have, which is exactly the wrong meter for a 1:1 fleet.

Where Sortly is strong

• ● Every price is on the page, including a genuinely free tier, with no demo gate anywhere in the funnel.
• ● The lowest adoption cost in this comparison by a distance: folders, tags, photos and custom fields, usable by a building secretary in an afternoon without an IT project behind it.
• ● Strong mobile — iOS and Android with offline access, barcode and QR scanning, and label generation from inside the same app, so counting is a phone job rather than a scanner-hardware purchase.
• ● Alerting that fits consumables well: low stock alerts for reordering and date-based alerts for maintenance and repair schedules, with in-app and email notification.
• ● More reporting than the price suggests — activity history, inventory summaries, user activity, low stock and item-flow reports, saved custom reports, and report subscriptions delivered on a schedule.
• ● Real integration surface for a product this simple: webhooks, an API, QuickBooks Online, and Slack and Microsoft Teams notifications, plus purchase orders, pick lists, and check-in and check-out.

What to check before you buy

• Pricing meters unique items, and a 1:1 district's item count is its student count. At 5,000 items the published tier is $299 per month, and anything past 10,000 items is Enterprise quote-only — a mid-sized district is off the published ladder on device count alone.

  Basis: Vendor pricing page item limits: 100 free, 500 Advanced, 2,000 Ultra, 5,000 Premium, 10,000+ Enterprise.

• User licenses are metered too, and tightly: 1 user free, 2 on Advanced, 5 on Ultra, 8 on Premium. A technician team plus building staff crosses into Enterprise quickly.

  Basis: Vendor pricing page user-license limits per tier.

• No help desk or ticketing of any kind. A district running Sortly still buys a service desk somewhere else, and the two never see each other.

  Basis: Absent from the vendor's published feature list, which covers inventory, alerts, reporting and integrations.

• No MDM or device integrations at all. The published integration list is QuickBooks Online, Slack, Microsoft Teams, webhooks and an API — so ChromeOS, Intune and Jamf data is typed or imported, and serials go stale between imports.

  Basis: Vendor features page lists no device-management or directory connectors.

• No SIS or rostering integration and no student, guardian or enrollment concepts — nothing notices a transfer, a withdrawal or grade rollover.

  Basis: Absent from the vendor's feature list and from its industry positioning, which addresses inventory rather than student records.

• Check-in and check-out is item custody, not a school-year loan: no due dates on a student device agreement, no e-signature, no damage fee, no family balance and no loaner pool workflow.

  Basis: Vendor documents check-in/check-out alongside pick lists and stock tracking, with no agreement or fee concepts published.

• It is an inventory product rather than an IT asset lifecycle product — warranty expiry, depreciation, ChromeOS auto-update expiration and refresh planning are not in the published feature set, though generic date-based alerts can approximate some of it.

  Basis: Vendor features page covers custom fields, alerts and reports; no warranty, depreciation or lifecycle module is published.

• Hosted SaaS only, with no self-hosted option, and no SSO or SAML in the published feature list — so it sits outside your single sign-on estate in both directions.

  Basis: No self-host or source distribution is offered on the vendor site, and SSO does not appear on the features or pricing pages.

How Chalk compares with Sortly →

The third option: Chalk

If you are weighing HappyFox Help Desk against Sortly, 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.