Find your fit
Who it is for
RT suits a team that wants ticket handling with configurable queues, roles, search and reporting, and can either operate the software itself or evaluate Best Practical managed hosting. It supports help desk use but can also track operational tasks.
Self-hosting needs an administrator for the server, database, email routing, upgrades and access rules. Evaluate the free software separately from commercial hosting or support, and confirm what service level and capacity the chosen managed plan actually provides.
The work it supports
Core capabilities
Staff can open a ticket in a chosen queue from the web interface, adding a subject, message, custom fields and attachments. An administrator can configure an inbound address so permitted senders create tickets by email, and later mail can add to an existing ticket. Test the address, sender rights and message threading in the real environment.
A queue groups tickets for a team or workflow. Each ticket has a single owner, while requester, Cc and AdminCc roles describe others connected to it. Custom roles can record more specific relationships and apply to selected queues. Review role rights before exposing customer or internal context.
Staff can reply to a requester or add an internal comment that is not sent to the requester. Configured correspondence rules and ticket watchers can generate additional email, so verify recipients before using RT with real requests.
Statuses depend on a queue lifecycle. Administrators can add custom statuses and transitions for a process such as new, active and resolved work. Check how tickets move if queues use different lifecycles, especially when transferring requests between teams.
The Ticket Query Builder searches by ticket properties and can support saved views and reports. Dashboards assemble ticket lists and charts for a role or team and can be shared or sent on a schedule. A pilot should check that search and dashboard access follow the intended permissions.
Articles provide reusable answers that an agent can search and insert while editing a response. Tickets also contain time fields, and a configured SLA can calculate due dates and track response or resolution targets. These tools can help recurring support work once the team defines its own answer, time and target rules.
For a self-hosted system, the vendor recommends SSL access and protection of configuration and database credentials. Make access, email handling and backups part of the rollout plan, then use fictional tickets to verify who can see a request and which messages leave the system.
Understand the offer
Pricing and getting started
RT software is free to use under GNU GPL version 2. That licensing does not supply a hosted server, database, email service, maintenance or backup operation. A self-hosted installation needs a supported Perl, SQL and web-server stack.
Best Practical offers managed hosting and commercial support, training and other services. The captured documentation confirms those offerings but does not establish current Cloud RT prices, user minimums or ticket limits; verify the purchase page and contract for the specific deployment before budgeting.
Look a little closer
Before you choose
Run a small fictional-ticket trial: create a web request, submit one through the configured mailbox, assign an owner, add an internal comment, send a requester reply, and move it through the chosen statuses. Check threading, watcher emails and who can access each queue.
Decide whether the team can maintain a self-hosted RT server or needs managed hosting. Test restore and upgrade ownership, define role access and data handling, and confirm paid hosting or support terms. Evaluate RTIR separately only if incident-response workflows are actually required.
12 distinct sources behind this profile. Research observed Oct 20, 2026. Features and offers can change.
View sources and research →
