Destiny Resource Manager vs HelpSpot

Destiny Resource Manager

Follett's district resource-tracking system, part of the Destiny suite, used to manage technology devices alongside textbooks, curriculum materials, and other non-library resources, with bidirectional MDM sync and an optional help desk.

Where Destiny Resource Manager is strong

• ● The strongest permission model in the K-12 asset field: roughly 69 discrete Resource Manager permissions spanning search, resource management, circulation, fines, fees, and administration, with add, edit, delete, and duplicate as separate grants.
• ● Two-tier district and site administration — access levels definable by the district administrator, a site administrator, or both, with district settings pushed out and enforced district-wide or selectively.
• ● Resource Groups provide a second, orthogonal scoping axis, so access is bounded both by permission and by branch of the district's shared resource tree.
• ● Offline-capable mobile scanning through the Destiny Back Office app on iOS and Android, plus Follett's own VersaScan handheld and PocketScan Bluetooth scanner. Both inventory and circulation work offline, with SSO and multi-site switching without re-authenticating — the only offline-capable option in this comparison.
• ● Genuine bidirectional MDM sync across Google Workspace, Intune, and Jamf Pro, with rule-driven write-back that can change device state or organizational unit based on actions taken in Destiny.
• ● Digital Signature Agreements that hard-block checkout when unsigned, map agreements to resource type, patron persona, and site, can require a signature on every checkout, and ship Block Overrides and Needs Signature compliance reports.

What to check before you buy

• No warranty field is documented. The Add/Edit Item field list runs from Status and Condition through Purchase Price, Purchase Order, Funding Source, and Projected Life without a warranty field anywhere in it; Date Acquired plus Projected Life models asset life and depreciation, not warranty end.

  Basis: the complete documented item field list in Follett's own help docs

• Purchase order support is a plain text field on the item record — the docs describe it as the PO number used for the items. There is no approval routing, no line items, and no vendor records. The separate Resource Orders module is internal district-warehouse fulfillment with pick lists and shipments, not external procurement.

  Basis: Follett help documentation for item fields and the Resource Orders module

• No native OneRoster, Clever, or ClassLink rostering is documented. Rostering is a nightly patron import via CSV with XSLT transform files. ClassLink and Okta appear only as SSO providers for Destiny Help Desk, never as roster sources.

  Basis: Follett patron import documentation; absence of any documented rostering connector in public docs

• No parts inventory and no repair-cost tracking in native help tickets — tickets carry priority, status, expected completion date, notes, assignment, and reopen, and nothing about the money or materials a repair consumed.

  Basis: Follett help desk ticket documentation

• No insurance or protection-plan object. Insurance is modeled as a generic fee, with no coverage terms, claims workflow, deductibles, per-incident tracking, or renewals.

  Basis: Follett documents insurance as an intended use of the generic fee type

• Digital Signature Agreements is described by Follett as a hosted cloud app requiring an external internet connection, and Destiny AI is available only to hosted customers. A district running Destiny on-premises or air-gapped cannot have either at any price.

  Basis: Follett product documentation stating the hosted-cloud requirement

• Destiny Help Desk is a paid subscription add-on that additionally requires Resource Manager 22.5 or later with Unified Navigation enabled, so older on-premises installs cannot adopt it without upgrading first.

  Basis: Follett add-on packaging and stated version floor

• The native fee 'Pay' permission records a payment rather than processing one. Actual online collection requires Destiny Fee Manager, a separate Stripe-powered product whose best parent-portal experience additionally depends on Follett's own Aspen SIS.

  Basis: Follett Fee Manager product documentation

How Chalk compares with Destiny Resource Manager →

HelpSpot

A long-running shared-inbox help desk that takes self-hosting seriously — same price and same features on your own server as in their cloud — but it is licensed proprietary software with no asset, roster, or identity side at all.

Where HelpSpot is strong

• ● Self-hosting is a first-class deployment, not a legacy tier: the vendor states the price and the feature set are identical to cloud, which is unusual and worth crediting.
• ● Genuine data sovereignty language backed by the product — you run the database, you own the backups, you get direct SQL access, and the install can sit behind a firewall without phoning home.
• ● You control when updates are applied, so a self-hosted install can be tested in staging before production rather than being upgraded underneath you.
• ● One all-inclusive price per band: unlimited tickets, unlimited mailboxes, and the AI drafting, summarization, and categorization features included rather than sold as a per-agent add-on.
• ● Strong shared-inbox fundamentals — multi-mailbox and multi-brand portals at real scale, collision detection, triggers and mail rules, smart responses with placeholders, time tracking, and a knowledge base.
• ● A REST API and webhooks, plus live lookup that pulls customer data from an external system into the ticket view — a reasonable seam if your student or device truth lives elsewhere.

What to check before you buy

• Self-hosted does not mean open source. HelpSpot is proprietary licensed software you download and run — there is no public source repository and no open-source license, so you can host the code but you cannot fork it, audit it freely, or continue it if the vendor stops.

  Basis: The vendor publishes a licensed self-hosted download and no source repository or OSI license anywhere on its site.

• Pricing scales with agent count, which is the wrong axis for K-12: a district has few technicians and enormous fleets, and the fleet is not something HelpSpot prices because it is not something HelpSpot tracks.

  Basis: Published bands are defined purely by number of agents, from 3 up to 2,000.

• No asset or inventory management of any kind. There is no device record, so a ticket cannot tell you which machine the person is holding.

  Basis: Absent from the vendor's published feature list, which covers shared inbox, ticketing, automation, reporting, knowledge base, and AI.

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

  Basis: No asset or custody concepts exist in the product to build these on.

• No SIS or rostering integration — no OneRoster, Clever, ClassLink, PowerSchool, Infinite Campus, or Skyward — and no student, guardian, or enrollment concepts. The data model is customers and mailboxes.

  Basis: None appear on the vendor's features, pricing, or solutions pages; the product is positioned for support teams generally, not K-12.

• No ChromeOS, Google Admin, Intune, or Jamf ingest, so nothing reconciles your ticket queue against what the fleet actually reports.

  Basis: No MDM connector is published anywhere on the vendor site.

• No repair records, no parts inventory, no student fee assessment, no purchase orders, no warranty tracking, and no funding-source reporting.

  Basis: All absent from the published feature list.

• SSO and SAML are not named in the published feature list, and there is no native mobile app — worth confirming directly with the vendor if either is a requirement.

  Basis: Neither appears in the vendor's feature documentation; we would rather flag the gap than assert a capability we could not verify.

How Chalk compares with HelpSpot →

The third option: Chalk

If you are weighing Destiny Resource Manager against HelpSpot, 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.