By Enhancesoft

osTicket

What it does

osTicket turns support requests from email, web forms or an API into tickets that a team can route, answer and track in a web help desk. Agents work from queues, and customers can follow their own ticket through a portal. Enhancesoft offers a free downloadable edition alongside a separately hosted SupportSystem service.

Category
Help Desk
Last updated
Oct 18, 2026
osTicket · Editorial illustration
Conceptual editorial illustration of incoming email and web requests becoming support tickets routed to team trays and a customer response for osTicket.

Work at osTicket?

Help customers find accurate information about your software.

Manage this listing →

Find your fit

Who it is for

The free edition suits a team willing to install and operate its own help desk. Its software is free to download, but an administrator still needs to configure incoming and outgoing email, help topics, departments and staff permissions, then maintain the installation.

A team that wants hosted infrastructure, upgrades and vendor support can compare the separate SupportSystem cloud offer. Buyers should decide which party will operate mail delivery, backups, upgrades and user access before comparing the subscription display with self-hosting.

Back to sections

The work it supports

Core capabilities

Email requests can become tickets through piping or POP3/IMAP polling, but email fetching starts disabled and needs configuration. Set up the outbound path as well; osTicket recommends SMTP rather than relying on the default PHP Mail route.

For web intake, create help topics and forms that collect the details each type of request needs. A help topic can route the submission to the right department without asking a customer to understand the organization’s internal structure.

Ticket filters can automate routing to an agent or department using form and user information. Agents can then reassign a ticket to a person or team or transfer it to another department, with handoff details kept in the ticket thread.

The agent workspace separates Open, Answered, My Tickets, Overdue and Closed views. These are working views rather than a single linear funnel: a ticket can be answered and overdue at once, and a closed ticket may reopen when the customer replies.

Agents can reply to the customer, add internal notes and change ticket status according to their role. Customer-visible replies and internal notes are separate, so test the view from a fictional customer account before using notes for sensitive internal coordination.

A configurable ticket lock can keep another agent from replying during the first agent’s work period. Department-specific roles control who may assign, reply, close or transfer a ticket; review both controls when several teams share a queue.

Customers can check a ticket using its number and their email address, or register to see associated tickets together. Agent search can save criteria and export ticket results as CSV, which helps with backlog review and a later migration.

SLA plans can set due-date expectations and overdue notices by help topic, department or filter. Decide which request types need a response target and review what the Overdue queue contains before using it to judge support performance.

Back to sections

Understand the offer

Pricing and getting started

The open-source edition is listed as free to download with community support. It does not include the managed upgrades and ongoing email/phone support shown for the cloud service, so include hosting, operations and support labour in a self-host comparison.

Cloud-hosted SupportSystem is displayed as starting at $12 per agent per month and advertises a 30-day trial. The retained pricing text uses a dollar sign without a currency code and does not establish the final seat count, billing term or tax; confirm those in the actual quote. The hosted service includes managed infrastructure and upgrades.

A virtual appliance is also offered, but its price is quote-led. Keep it separate from both the free download and the standard cloud-hosted display when asking Enhancesoft about deployment and support responsibility.

Back to sections

Look a little closer

Before you choose

Pilot a fictional request through each intended intake route: support email, a web form and any API integration. Check ticket creation, routing, an agent reply and the customer portal view. Incoming mail fetching is not enabled by default, and outbound SMTP needs its own test.

Define who can see, assign and transfer tickets across departments. Test the same fictional case with two agent roles and a customer identity so internal notes, customer replies and the ticket lock behave as expected.

Review status and retention procedures before rollout. Answered and Overdue can overlap, a closed ticket may reopen, and the agent guide describes deletion as unrecoverable. Export a sample result set and agree on a backup and recovery approach for the chosen edition.

For self-hosting, verify the download’s server, PHP and database requirements against the exact version selected. The retained documentation pages are labeled 1.17.7 while the download page lists newer core versions, so check version-specific installation and permission details during a pilot.

Back to sections

10 distinct sources behind this profile. Research observed Oct 18, 2026. Features and offers can change.
View sources and research →

Help keep this profile useful

Spotted an outdated detail? Send the correction with a supporting source. A verified account is needed to submit.

Suggest a correction ↗