Freshdesk Ticketing System: Setup Guide, SLAs, Routing (2026)

Freshdesk's ticketing system turns every customer email, portal request, web form and Facebook message into a ticket in one shared inbox, then lets you move it through statuses, SLA timers, automation rules and routing until it closes. The part most buyers miss is the plan line. Growth gives you the ticket inbox, one default SLA policy, custom statuses and all three automation types, but tickets are assigned by hand or by rule. Automatic round-robin and load-based assignment, multiple SLA policies, collaborators and parent-child tickets start on Pro. This tutorial walks through the setup in the order a new admin needs it.

How a message becomes a ticket

Standalone Freshdesk is email-first. Support mailboxes, the customer portal, web forms in the lite help widget, Facebook (a Growth-and-up channel for new accounts), phone through Freshcaller or a telephony app, and eBay on Pro by request all land as tickets. Live chat, WhatsApp, Instagram and SMS are not part of standalone Freshdesk for new accounts; they come with Freshdesk Omni, which we cover in our Omni guide. Pick the product before you configure anything, because the channel list decides which queues you will build.

Email has a few rules worth knowing on day one. A message sent to more than 50 To and CC addresses creates no ticket, and neither does one where both From and To are your support addresses. When a support address sits in CC, the thread becomes a ticket by default, and a ticket creation rule can delete it. Outbound emails you start from Freshdesk also become tickets, set to Closed so no SLA timer runs until the customer replies. A built-in spam watcher sends a sender to spam on the 51st email inside 30 minutes. That protects the queue from mail loops.

Freshdesk's pricing page lists Growth at $19 per agent per month billed annually ($228 per agent a year) or $23 per agent per month billed monthly, and Pro at $55 per agent per month billed annually ($660 per agent a year) or $66 per agent per month billed monthly.^[1] Billing is per agent and every agent on the account sits on the same plan; our pricing guide covers add-ons and renewal rules. By our arithmetic, the step up between those two plans costs $432 per agent a year on annual billing, or $2,160 a year for a five-agent team.

Statuses, priorities and SLA timers

Every ticket starts with four default statuses: Open, Pending, Resolved and Closed. Freshdesk also ships Waiting on Customer and Waiting on Third Party, and from Growth you can add custom statuses. Each status either runs the SLA clock or pauses it, so a status such as Waiting on Customer is the honest way to stop the SLA timer while you wait, though reported response time keeps counting there. Priorities run Low, Medium, High and Urgent, and ticket types such as Question, Incident, Problem and Feature Request help you report on volume later.

SLA policies set first response, next response and resolution targets. Growth includes one default SLA policy and one set of business hours. Pro adds multiple policies (up to 1,000), SLA reminders and escalations, SLA per company, and multiple business hours (up to 500) assigned to groups, each with its own time zone and holidays imported by country. Enterprise adds SLA conditions on custom fields. If you support several regions or sell premium contracts, that difference alone decides the plan.

Three timer rules trip up new admins. Only a reply or a public note counts as a response; a private note never stops the first-response clock. Reopening a resolved ticket into a status with the timer on counts against its response and resolution times. Timers follow the helpdesk time zone set under Admin > Account > Helpdesk Settings, not each agent's clock. Check that setting first.

Automation rules: three types, firm limits

Freshdesk has three rule types.^[2] Ticket creation rules run when a ticket arrives, by default stopping at the first matching rule, or running every match if you switch that setting. Ticket update rules run every matching rule from top to bottom whenever something changes, including actions taken by collaborators. Hourly triggers (Growth and up) scan tickets once an hour, look only at tickets updated in the last 30 days, can fire up to about 58 minutes late, cannot call webhooks and cannot use contact or company conditions.

Plan around the limits instead of fighting them. Rules never run retroactively, so a new rule ignores the backlog. One rule cannot trigger another. Automations do not run when the requester is an agent, nor on outbound tickets created with New Email. There is no cap on conditions per rule, which tempts admins to build one giant rule; several small ones are easier to debug.

Scenario automations are the manual counterpart: one click applies a bundle of actions, such as setting a status, adding a tag and sending a reply. They arrive on Growth, can be shown to all agents or to one group, and run from the mobile apps too. Webhooks inside automations also start on Growth, while the Trigger API action, which reads the response, is Pro.

Routing: who gets the ticket

On Growth, assignment is manual or rule-based. An automation that sends a new ticket to a group only notifies that group and leaves the ticket unassigned until someone takes it. Agents pick up their own work. That works for three or four people who share one queue. It breaks once nobody owns the pile. Watchers and day passes do not change this, because only a Pro or Enterprise plan hands tickets out automatically. Plan the upgrade early.

Pro switches on automatic assignment through Omniroute, enabled per group.^[3] Round-robin hands each ticket to the available agent who has gone longest without one, and it ignores business hours: it follows each agent's availability toggle. Load-based routing sends each ticket to the least loaded agent until everyone reaches the capacity you set. Only tickets with an active SLA timer count toward that load, so moving a ticket to Waiting on Customer frees a slot. Tickets you assign by hand can push an agent over the limit and block new automatic assignments. If every eligible agent is offline or full, the ticket waits unassigned.

Enterprise adds skill-based routing with up to 180 skills, matching a ticket's language or product to agents who handle it. The match also weighs each agent's capacity, so a skilled agent who is already full is passed over rather than overloaded. Most teams never need it. For a team that only needs fair distribution across one language and one product, Pro's round-robin is enough.

Working a ticket together

Several collaboration tools exist on every paid plan. Any agent can add watchers, who get email updates; even an occasional agent without a day pass can follow a ticket this way. Private notes stay internal, the Forward option brings in a third party the customer never sees, and discussion threads hold up to 100 threads per ticket. Agent collision detection shows an eye icon when someone else is viewing a ticket and a pen icon when they are typing. There is no hard ticket lock, only these alerts.

Pro adds the heavier tools. Collaborators (up to 5,000) are free seats for colleagues outside support who can view tickets, edit private notes and update status, which costs less than buying full seats for engineers or finance staff. Parent-child ticketing splits one request into up to 50 child tickets, and shared ownership keeps an internal group and the assigned agent working on the same ticket. Shared ownership needs custom statuses mapped to internal groups; the four default statuses cannot be mapped. Admins switch both on under Admin > Support Operations > Advanced Ticketing.

Merging is irreversible. Merge with care. Chat, WhatsApp, Facebook and Instagram tickets cannot be merged at all, the merge note is private by default, and merged tickets drop out of reports while ticket exports still count them separately, so the two totals will not match. Freshdesk's pricing page lists day passes for occasional agents at $2 per pass on Growth and $7 per pass on Pro, and every plan includes three free passes.

Old tickets, spam and the mobile apps

Freshdesk archives tickets that have been closed and inactive for 120 days.^[4] Archived tickets are read-only and cannot be unarchived, so a customer reply opens a new ticket instead. Automation rules skip them, watchers stop getting notifications, and global search leaves them out unless you switch on the option to include archived tickets. A parent with open children waits until those close. Tickets in Spam and Trash are deleted permanently after 30 days and never appear in reports, so review those folders weekly.

The iPhone, iPad and Android apps are for agents only, on every plan; there is no customer-facing app. Agents can reply, bulk assign and close, run scenarios, merge, mark spam and log time with a stopwatch. Color strips show priority at a glance, from red for Urgent to green for Low. Admin settings, automation rules and custom ticket views must be built on the web first; saved views then appear at the top of the mobile ticket list.

The bottom line

Freshdesk's ticketing system is easy to learn and strict about plans. Growth covers a small team that assigns work by hand and lives with one SLA policy; the moment you need tickets handed out automatically, different targets per customer or colleagues working inside tickets without a full seat, the real starting point is Pro. Build the statuses and the SLA clock first, then automation rules, then routing, and use the trial to test the Pro features before you commit to a plan.