Customer support ticketing and help desk systems for managing, tracking, and resolving support requests efficiently. All available with one-click installation on 365i web hosting.
FreeScout is a free, open-source help desk and customer support platform designed to help businesses...
osTicket is a free, open-source ticketing system designed to help organizations manage customer supp...
Trouble Ticket Express is a free, open-source help desk and ticketing system that simplifies custome...
A self-hosted help desk takes the mailbox your customers already write to and turns it into tracked tickets: an inbound message becomes a numbered conversation, replies thread against it, and nothing falls out of a shared inbox because one person marked it read. That is the whole job. Everything else these applications add, canned replies, saved searches, tags, per-agent assignment, is built on top of that one loop of receive, assign, reply, close.
The commercial market is priced per agent, and that is what pushes people towards open source ticketing software. Zendesk's UK price list puts Suite Team at £45 per agent per month paid yearly, with Suite Professional at £89. Help Scout publishes three tiers at 25, 45 and 75 US dollars per user per month. Freshdesk and Intercom work the same way. For a support team of one or two those numbers are survivable. At five or six agents the annual bill starts to look like a hosting budget for a decade, and self-hosting stops being an ideological choice and starts being arithmetic.
The three applications in this category are not equivalent. FreeScout is a modern Laravel app that deliberately imitates Help Scout's shared-inbox model. osTicket is the older, more formal ticketing system, with departments, SLA plans and help topics. Trouble Ticket Express is a Perl CGI script from a different era of the web and should be treated as a historical listing rather than a candidate.
Situations we see often. If one of these sounds like you, this category is worth a look.
Five engineers on a mid-tier SaaS help desk is comfortably four figures a year before any add-ons, and the tooling is mostly unused: no telephony, no chatbot, no workforce scheduling. Moving the same five inboxes onto a self-hosted install puts the recurring cost into a hosting plan and leaves the ticket history on a server the firm controls.
Three part-time staff answering members from a single address, where the failure mode is two people replying to the same person and a third message going unanswered for a fortnight. Ticket assignment and a visible open queue fix that at a cost the charity can actually justify, and the member correspondence stays on UK infrastructure.
Low ticket volume, but each thread runs for months and references version numbers, log extracts and prior conversations going back years. Per-agent SaaS pricing punishes the small team while the archive, which is the actually valuable asset, sits in somebody else's database under an export policy that can change.
Account managers currently keep client threads in Outlook, so when somebody leaves the history goes with them and handover is a forwarded chain. A shared help desk on the agency's own domain makes the correspondence an asset of the business, and it can sit alongside the agency site on the same hosting package.
To take advantage of modern email authentication methods, the Oauth2 Plugin is required. This release supports PHP versions 8.2 through 8.4.
Two things a buyer should read into that. Mailbox access now means OAuth 2.0 rather than a username and password, so the plugin is not optional if your support address lives on Microsoft 365 or Google Workspace. And the supported PHP range has a ceiling as well as a floor, which is why the PHP version selector matters more here than on most applications.
Background fetching fetches only unread emails.
This is the single most common cause of a "lost ticket" report, and it is not a bug. If anything else touches that mailbox, a phone client, a webmail tab left open, a forwarding rule, the message is marked read and the help desk never sees it. Dedicate the mailbox to the help desk and nothing else.
Helpdesk and ticketing apps live or die on cron reliability and IMAP throughput. Email-to-ticket pipelines silently degrade when shared hosts throttle background fetches, and the resulting "lost tickets" feel like an application bug but are nearly always a hosting one. We run cron every minute on every plan, monitor IMAP latency, and set up outbound SMTP with proper DKIM and DMARC during install so ticket replies land in inboxes rather than spam folders.
Inbound email is the part that breaks. On a dedicated server you can pipe mail into a script at delivery time. On shared hosting the realistic route is IMAP polling: a cron job runs every minute or two, connects to the mailbox, pulls unread messages and creates tickets. Three things have to be true at once, and the failure of any one looks identical from outside: cron running, the php-imap extension enabled on the PHP version the cron job uses rather than the one serving the site, and the mailbox reserved for the help desk, because background fetching only sees unread mail.
Watch the PHP ceiling. osTicket 1.18.4 supports PHP 8.2 to 8.4 and will not run on 8.5, so this is one of the few applications where you deliberately select an older branch. FreeScout is broader, and as a Laravel application it expects the document root pointed at its public directory, not the project root.
Skip Trouble Ticket Express. It is a Perl CGI application with no current release and a public record of remote code execution issues. Listing it is not a recommendation.
Not for you if you need CSAT surveys, contractual SLA reporting, live chat, voice, or shift routing across fifteen agents. That is what the commercial platforms charge for, and rebuilding it in modules costs more than paying for it.
Common questions we hear from people running help desk systems applications on 365i hosting.
FreeScout and osTicket are both alive; Trouble Ticket Express is not. FreeScout releases constantly, with 1.8.235 shipping on 15 August 2026. osTicket moves more slowly and formally, with v1.18.4 released on 17 June 2026 carrying security fixes and PHP 8.3 and 8.4 compatibility work. Trouble Ticket Express is a Perl CGI script with no visible release cadence and known historical remote code execution vulnerabilities, and we would not put a support queue on it.
Agent count decides it, because that is what the commercial platforms bill on. Zendesk lists Suite Team at £45 per agent per month paid yearly on its UK site, and Help Scout lists 25 to 75 US dollars per user per month. Self-hosted, the cost is one hosting plan regardless of how many agents you add. At one or two agents the saving is modest and probably not worth the maintenance. At five or more it becomes the dominant factor in the decision.
Yes, in almost all cases now. Both providers have moved mailbox access away from plain username and password authentication towards OAuth 2.0, and osTicket states plainly that its OAuth2 plugin is required to use modern email authentication. Budget an hour for the app registration on the provider side; it is fiddly the first time and then permanent. If your support address is an ordinary mailbox on your own hosting package instead, this problem does not arise at all.
Silent email failures, in both directions. Inbound, the fetcher stops and nobody notices for two days because a working help desk with no new tickets looks exactly like a quiet Tuesday. Outbound, replies land in customers' spam folders because the domain's SPF, DKIM and DMARC records were never set up for the address the application sends from. Neither is a fault in the software. Both are worth checking deliberately in the first week rather than discovering through a complaint.
Our entry web hosting plan runs FreeScout or osTicket for a small team without complaint, with SSH, unlimited cron jobs, free wildcard SSL and daily backups with 30 days of restore points. Move to a managed cloud server from £9.99/mo when ticket volume makes search slow, when you want the mail fetch running on a tighter interval than a shared cron schedule comfortably allows, or when the attachment archive grows past what a shared plan should be carrying.
Get Help Desk Systems apps up and running in minutes with our fast, reliable web hosting. Every plan includes one-click installation, free SSL, UK, US & Asia data centres, and dedicated expert support.
All prices exclude VAT. No contract, cancel any time.
All 3 help desk systems applications available with one-click installation on our fast UK web hosting.
