Free Help Desk Software: What You Actually Get

Free help desk software typically gives a small team the core loop — a request form, a shared queue, assignment, statuses and email or in-app notifications — with caps on agents or users, and holds back SLA timers, automation, advanced reporting, integrations and AI for paid plans. The right free plan is one whose limits you won't hit within six months, that lets you export your data, and whose core workflow doesn't depend on a paid add-on.

What "free" usually means

Vendors use free plans to let small teams start and grow into paying. The limits cluster around a few levers:

Lever	Typical free-plan limit	Why it matters
People	A small number of agents or total users	The first limit most teams hit
Teams / queues	One or a few	Blocks adding HR or finance later
SLA timers	Often paid	Deadlines are the core of a desk
Automation	Few or no rules	Routing and escalation become manual
Reporting	Basic counts	No percentiles, no breach analysis
Integrations	Limited or none	Chat and email intake may be paid
AI features	Small monthly allowance or none	Suggestions stop mid-month
History / retention	Sometimes capped	Old requests or chat disappear
Support	Community only	You're on your own when it breaks

None of these is unreasonable. The question is which ones you'll hit, and when.

LetRelay's own free plan follows the same pattern, and we'd rather say so plainly: the core desk (requests, queue, tasks, rooms and meeting booking) is free for a small team, with a monthly allowance of AI assists; analytics, webhooks, attendance and a few other features are on the Pro plan. Current limits are always on the plan page in the app.

The limits that actually hurt

1. People caps

Most free plans cap agents (people who work requests) or total users. Count both: a 30-person company with 3 IT agents fits an agent cap but not a total-user cap. Also count the teams you'll add in six months — HR and finance usually follow IT within a year.

2. SLA timers behind a paywall

If a free plan has no deadlines, it's a shared inbox with statuses. That can be enough for a start, but you'll lose the most useful thing a desk does: a queue sorted by what's due soonest. Why that matters is in the SLA tracking guide.

3. AI that runs out mid-month

AI suggestions on free plans come with monthly allowances, because model calls cost the vendor money. Check what happens when the allowance runs out: does intake still work normally, with suggestions paused? Or do requests get stuck? The right answer is the first — see AI that degrades gracefully.

4. No data export

The most important question for any free tool: can you get your data out, in a usable format, without paying? Requests, comments, attachments, users. If not, you're locked in the moment you have history worth keeping.

Hidden costs

"Free" can still cost:

• Time spent working around limits — manual routing because automation is paid, spreadsheets because reporting is basic.
• Migration later — moving a year of history when you outgrow the plan. Easier if you checked export first; see moving from a spreadsheet to a request desk for what a migration involves.
• Price changes. Free plans change. Read the vendor's history: have limits tightened suddenly before?
• Per-seat pricing once you upgrade. Model the cost at the size you'll be in a year, not today.

Security questions to ask any help desk

Help desks hold sensitive data: HR questions, access requests, sometimes passwords people shouldn't have pasted. Free or paid, ask:

• Is access enforced on the server? Can a requester see only their own requests, even through the API? The strongest designs enforce this in the database — see row-level security vs app-layer authorization.
• Are private queues possible? HR requests shouldn't be visible to IT agents.
• Is multi-factor authentication available for agents and admins? CISA recommends MFA as one of the most effective account protections.
• Where is data stored, and is it used to train AI models? Especially relevant for AI features.
• What happens when you delete your account? Is your data actually deleted?

What a free plan should never take away

Some limits are fair business; others make the free plan a trap. A free plan worth trusting still lets you:

• Export everything you put in. Your requests are your organization's records.
• Keep working when an allowance runs out. Running out of AI assists should pause suggestions, not intake.
• Downgrade without losing data. If you try the paid plan and step back down, your history should still be there, even if some features become read-only.
• Remove people. Offboarding someone shouldn't require an upgrade.
• Keep security features. Basic permission controls and multi-factor sign-in aren't premium features; they're table stakes.

If a plan fails any of these, weigh that more heavily than any feature on its list.

Build vs buy vs free

Some teams consider building their own. A basic desk is a few weeks of work for a developer familiar with a modern stack — we describe the architecture in building an internal help desk with Next.js and Supabase. The hard parts aren't the forms; they're permissions, SLA logic, notifications, reporting and keeping it all maintained. Unless the desk is your product, a free or inexpensive tool is usually the better use of engineering time.

A checklist before you commit

• Fits your people count — agents and total users — for the next 6–12 months
• Has deadlines/SLA timers, or you've accepted working without them
• Data export of requests, comments and users is available on the free plan
• Intake keeps working when AI allowances run out
• Private queues for sensitive teams
• MFA for agents and admins
• Clear data-handling and AI-training policy
• Upgrade cost at your size in a year is acceptable
• You tried it with real requests for a week, not just a demo

Try it for real

Every help desk looks fine in a demo. Run a one-week pilot with one team and real requests: file ten, work them, run the reports, export the data. The problems that matter — a missing field, a confusing status, a notification nobody sees — show up in the first week of real use, not in the feature list.

FAQ

Is free help desk software good enough for a small business?

Often, yes, for a team with a handful of agents and simple routing. Check the people cap, whether SLA deadlines are included, and whether you can export your data before relying on it.

What features are usually missing from free help desk plans?

SLA timers, automation rules, advanced reporting, integrations, larger AI allowances and priority support are the most common paid features.

What's the biggest risk of a free help desk?

Lock-in without data export. If you can't get your requests and history out, switching later means losing them or paying to leave.

Should I build my own help desk instead?

Only if it's core to your product or you have unusual requirements. Permissions, deadlines, notifications and reporting take far more ongoing work than the forms.

Is there open-source or self-hosted free help desk software?

Yes. Open-source help desk and ITSM projects such as osTicket, Zammad, FreeScout and GLPI can be installed on your own server at no licence cost. The price is your time: you host it, patch it, secure it, back it up and run its email intake, and you carry the risk if nobody on the team does that reliably. They suit a team with someone who already runs servers; for everyone else, a hosted free plan with clear limits is usually less work. Check each project's current features and licence before you commit.

Sources

• Wikipedia — Help desk
• Atlassian — What is ITSM?
• CISA — Require multifactor authentication
• OWASP — Broken Access Control
• osTicket — open source support ticketing
• Zammad — open source helpdesk and ticketing
• FreeScout — open source help desk and shared mailbox
• GLPI — open source ITSM and asset management