Ticketing software pricing based on the queue you run

A per-agent model charges for people who work tickets. A per-resolution model follows automated outcomes or usage units. Flat pricing stays stable inside the plan limits. Free tiers help with evaluation but may restrict agents, queues, history, automations, or reporting.

Seat pricing is straightforward for a stable service desk. Resolution pricing needs reliable volume forecasts, especially during peaks. Flat pricing can suit a small team with a known channel mix. Use a free tier for testing only when it represents the ownership and SLA workflow you plan to run.

• Stable team: calculate every agent and required role
• Seasonal volume: test resolution or usage overage assumptions
• Small queue: compare flat software cost and separate AI consumption

Most shortlists come from the same pool: Zendesk, Freshdesk or Freshservice, Jira Service Management, ServiceNow, Zoho Desk, HubSpot Service Hub, Intercom, Help Scout, Spiceworks, osTicket, and SamDesk. They do not price the same way, so the honest comparison is strengths, weaknesses, and the unit each one bills on. Treat this as a shape guide and read current numbers on each vendor page before you build a budget.

• Zendesk — strength: depth, apps, enterprise governance. Weakness: capability gates push you up tiers. Billed per agent, per suite tier.
• Freshdesk / Freshservice — strength: broad features at mid-market prices, ITSM sibling. Weakness: the useful automations sit above the entry plan. Billed per agent.
• Jira Service Management — strength: cheap for engineering-adjacent teams already on Atlassian. Weakness: customer-facing support feels like a bolt-on. Billed per agent with a free small-team tier.
• ServiceNow — strength: enterprise ITSM and process rigour. Weakness: implementation cost usually exceeds licence cost. Quoted, not listed.
• Zoho Desk — strength: low entry price inside a large suite. Weakness: value depends on adopting the rest of Zoho. Billed per agent.
• Spiceworks — strength: no licence cost. Weakness: ad-supported and thin on SLA and reporting depth. Free.
• osTicket / FreeScout / Zammad — strength: no per-seat licence. Weakness: you own hosting, upgrades, and security. Self-hosted.
• SamDesk — strength: flat workspace price with bring-your-own-key AI. Weakness: focused on ecommerce support, not general ITSM. Flat subscription.

IT support and customer support look alike on a feature list and diverge sharply in practice. An internal IT desk needs asset and configuration records, change and incident separation, an approval flow, and often a formal service catalogue. A customer support desk needs channel handling, order or account context, and reply speed. Products built for ITSM — Freshservice, Jira Service Management, ServiceNow, GLPI — carry the asset and change model natively, and you pay for it. Customer-facing helpdesks carry channels and customer context instead. If someone on your shortlist is cheap for one job it is usually because it was designed for the other one.

• Internal IT: asset register, change management, approvals, service catalogue
• Customer support: channels, customer and order context, response-time reporting
• Both in one tool: expect to pay for the larger product or run two smaller ones

For a small business the free field splits three ways. Ad-supported hosted products, most notably the Spiceworks Cloud Help Desk, carry no licence cost and no server to run, but you accept in-product advertising and a ceiling on reporting and SLA depth. Self-hosted open source — osTicket, FreeScout, Zammad, GLPI — has no licence cost and no ceiling, but you provide the server, the upgrades, the mail deliverability, the backups, and the security patching. Free tiers from commercial vendors are the third route and are usually capped at a small agent count. The cheapest ticketing system on paper is whichever of these costs nothing; the cheapest one in practice is the one that does not need a half-day of somebody's week to stay alive. Price the maintenance hours at your own internal rate before calling it free.

Almost every vendor has an enterprise tier, and it rarely means more tickets. It means governance: single sign-on and SCIM provisioning, audit logs, granular roles and field-level permissions, data residency, sandbox environments, contractual uptime, and named support. Those items get deliberately placed above the mid tier because they are what larger buyers cannot go without. Check early whether your security or procurement team requires SSO, audit logging, or data residency, because a single one of those requirements can move your whole quote up a tier regardless of team size. Ask the vendor which specific tier carries each requirement rather than accepting a general answer.

Check whether SLA policies, routing, audit history, analytics, integrations, and AI are included. Also account for migration and administration. Compare current documentation or quotes rather than copying a price table that can change before your rollout starts.

SamDesk currently lists a €10 monthly BYOK plan and a €150 one-time lifetime deal for the first 100 customers. The software price does not include managed AI usage. Your organization connects its own provider key and pays provider usage directly.

Record agents, ticket volume, peak months, SLA rules, channels, integrations, automation, and reporting for one representative queue. Apply every vendor model to that same scope. The result is a decision estimate, not a misleading headline price.

Frequently asked questions