Freshservice Ticket Assignment: Automatic Ticket Assignment, Assignment Policies, and Round Robin
Freshservice has two different ways to assign tickets automatically, built years apart, and most teams only find the second one after the first stops behaving. Here is what each actually does, where it lives in the admin, which plan unlocks it, and the setup steps that quietly have to be true before anything rotates at all.
In short
Freshservice ticket assignment runs through two separate systems, and knowing which one you are in explains most of the confusion. The older method is group-level round robin: you set an agent group to Automatic under Admin, User Management, Agent Groups, and tickets rotate to agents in that group in circular order. Each agent also has to switch on Auto-assign tickets on their own profile, observers are never assigned, and round robin covers tickets but not tasks. The newer method is Ticket Assignment Policies, under Admin, Service Management, which ranks available agents by their current workload and can filter by work schedule so a ticket does not land on someone minutes from the end of a shift. Load-based and availability routing reached general availability in mid-November 2025 on the Pro and Enterprise plans. Skills-based routing is announced but was still pre-GA at our last check, with the private beta limited to Enterprise and closed to new requests. Something also has to put the ticket into the group first, usually the Workflow Automator or your support email setup, or nothing rotates. Assigner runs round robin, weighted round robin, load-balanced, skill-based, and availability rules as one engine beside the Freshservice you already run, from $12/user/mo, and names the rule behind every assignment. The AI assists your triage, the rules stay yours, and the demo data shown is illustrative, not a live integration.
Why it fits
IT and service desk teams on Freshservice that want fair, skill and workload aware ticket assignment without moving up a plan tier or waiting on a pre-GA feature, and teams that also route sales leads or ops tasks and want one fairness engine across all three.
Skill routing without waiting for GA
Freshservice skills-based routing was announced but still pre-GA at our last check, with the beta capped at Enterprise and closed to new requests. Assigner routes by skill and proficiency today, beside the Freshservice you already run.
One rotation across every queue
Freshservice rotates inside a single agent group and has no view of the leads in your CRM or the tasks on your ops board. Assigner applies one set of fairness rules across tickets, leads, and ops work, so fair means the same thing everywhere.
Every assignment shows its reason
When a ticket lands on the wrong agent you are reading group settings and automator rules to work out why. Assigner names the rule that placed each item, so a triage dispute takes seconds instead of an afternoon.
Side by side
Freshservice ticket assignment methods compared
| Method | What it does | Where you configure it | Plan required | Main limitation |
|---|---|---|---|---|
| Round robin auto-assign | Rotates tickets to agents in a group in circular order | Admin > User Management > Agent Groups, set the group to Automatic | Available wherever agent groups are | Only agents who are online and have Auto-assign tickets enabled. Tickets only, not tasks. |
| Load-based routing | Ranks available agents by current workload and assigns to the least loaded | Admin > Service Management > Ticket Assignment Policies | Pro or Enterprise | Agent load values are configured by an admin rather than measured from real effort. |
| Availability routing | Filters to agents actually on shift and avoids end-of-shift assignments | Same Ticket Assignment Policies screen | Pro or Enterprise | Only as good as the work schedules you keep updated per agent. |
| Skills-based routing | Prioritizes agents whose skills match, ranked by proficiency | Ticket Assignment Policies | Enterprise, and pre-GA at our last check | Private beta closed to new requests. No published GA date. |
| Workflow Automator | Rule-based: sets a group or agent when a ticket is created or updated | Admin > Workflow Automator | Paid plans | Static matching. No rotation, workload, or availability logic of its own. |
Verified against Freshservice support documentation in August 2026. Plan gating and GA status change often, so confirm with Freshworks before you buy a tier for a feature.
In detail
Freshservice ticket assignment, setting by setting
How to enable automatic ticket assignment in Freshservice
Three things have to be true, and teams usually have two of them. First, the agent group has to be set to Automatic: go to Admin, then User Management, then Agent Groups, open the group, and pick the Automatic radio button. On a multi-workspace account the path runs through Admin, Global Settings, User Management, Agent Groups, or through the workspace settings for a single workspace. Second, each agent has to have auto-assign switched on for themselves, from their profile icon, Enable Auto-assign tickets. An agent who never touched that setting sits out the rotation silently. Third, something has to put the ticket into the group in the first place. Freshservice rotates within a group, it does not decide which group a ticket belongs to, so you need a Workflow Automator rule or your support email configuration to do that hand-off. Miss that last step and the rotation looks broken when it is simply never being invoked.
Freshservice ticket assignment policies: load and availability routing
The newer framework lives at Admin, then your workspace, then Service Management, then Ticket Assignment Policies, and it is a real improvement over plain rotation. Instead of counting turns, it ranks the agents who are available by how much work they are currently holding and gives the ticket to the least loaded one. It can also treat availability as a filter, reading real work schedules so a ticket does not get handed to someone in the last few minutes of their shift, which is the single most common source of overnight tickets nobody touched. Load-based and availability routing became generally available in mid-November 2025 and require the Pro or Enterprise plan. One honest caveat: agent load is a capacity number an admin sets, not a measurement of effort, so ten password resets and ten escalations still look identical to the policy. That gap is exactly what workload balancing and availability routing are built to close.
Freshservice round robin ticket assignment and where it stops
Round robin is the honest default when tickets are genuinely interchangeable, and Freshservice does it cleanly at the group level. The limits are worth knowing before you build a process on it. Observer agents can view a ticket but can never be assigned one, so they do not enter the rotation. Round robin applies to tickets and not to tasks, which surprises teams who split work into subtasks and expect those to distribute too. Agents in one workspace cannot be assigned tickets from another workspace, so a shared team spanning workspaces will not rotate the way an org chart suggests. And rotation has no opinion about skill: a network incident reaches whoever is next rather than whoever can close it, which usually means a reassignment and a longer resolution. The general shape of this tradeoff is covered on our round robin ticket assignment page, which compares how eight help desks handle it.
Freshservice vs Freshdesk ticket assignment
They are separate products from the same vendor and they do not share an assignment model, which trips up teams running both. Freshdesk calls the feature Automatic Ticket Assignment, configures it under Admin, Team, Groups, and offers round robin plus a load-balanced mode where you cap how many tickets an agent can hold at once. It is gated to the Pro and Enterprise tiers, and skill-based assignment is Enterprise only. Freshservice, being the ITSM product, went a different route with the Ticket Assignment Policies framework and its workload and work-schedule ranking. If you run Freshdesk for customer support and Freshservice for internal IT, you are maintaining two unrelated sets of rules with no shared view of who is actually busy across both. Our Freshdesk ticket assignment page covers that side in the same detail.
When Freshservice ticket assignment is not enough
The native tools are fine for a single service desk with one queue and interchangeable tickets. Three situations reliably outgrow them. The first is skill: if closing a ticket depends on who picks it up, rotation and load ranking both give you the wrong person quickly and fairly. Freshservice skills-based routing is coming but was still pre-GA at our last check and beta access was Enterprise only and closed. The second is scope: routing rules that only see Freshservice cannot balance an agent who is also working sales leads or ops requests, so the person who looks free in one tool is buried in another. The third is explainability, which matters more than teams expect. When an assignment is questioned, you want the rule named rather than a reconstruction from group settings and automator conditions. Assigner sits beside Freshservice rather than replacing it, routes support tickets, leads, and ops tasks through one engine with skills-based routing available now, and is published at $12 per user per month. It is a companion, not a live two-way sync, and it is designed to help rather than to guarantee an outcome.
Questions buyers ask
Frequently asked questions
What is ticket assignment in Freshservice?
Ticket assignment in Freshservice is how an incoming ticket gets an owner without someone picking it by hand. There are two systems: group-level round robin, which rotates tickets to agents in an agent group in circular order, and Ticket Assignment Policies, a newer framework that ranks available agents by current workload and can filter by work schedule. They are configured in different places and gated differently.
How do I enable automatic ticket assignment in Freshservice?
Go to Admin, then User Management, then Agent Groups, open the group, and select the Automatic option. Then have each agent turn on Auto-assign tickets from their own profile icon, because the group setting alone does nothing for an agent who has it switched off. Finally, make sure a Workflow Automator rule or your support email setup actually assigns tickets to that group, since Freshservice rotates within a group but does not choose the group.
Does Freshservice have round robin ticket assignment?
Yes. Freshservice distributes tickets to agents in a group in round robin order once the group is set to Automatic and the individual agents have auto-assign enabled. It only considers agents who are online, it applies to tickets rather than tasks, and observer agents are never assigned. There is no native weighting, so every agent takes an equal turn regardless of what they are already holding.
What are Freshservice ticket assignment policies?
Ticket Assignment Policies are the newer assignment framework at Admin, Service Management, Ticket Assignment Policies. Rather than counting turns, they rank available agents by current workload and assign to the least loaded, and they can use agent work schedules as a filter so tickets are not handed out at the end of a shift. Load-based and availability routing became generally available in mid-November 2025.
Which Freshservice plan do I need for automatic ticket assignment?
Group-level round robin is available wherever you can create agent groups. The newer Ticket Assignment Policies framework is different: load-based routing and availability routing require the Pro or Enterprise plan. Skills-based routing was limited to an Enterprise private beta at our last check. Plan gating changes, so confirm current tiers with Freshworks before upgrading purely to unlock assignment.
Does Freshservice have skill based ticket assignment?
Not generally available at our last check. Freshservice has announced skills-based routing inside the Ticket Assignment Policies framework, which would prioritize agents whose skills match the ticket and rank them by proficiency, but it was still pre-GA and the private beta was restricted to Enterprise and closed to new requests. Teams that need skill routing now typically add a routing layer beside Freshservice.
Why are tickets not being auto assigned in Freshservice?
Usually one of three things. The agent group is not set to Automatic, so nothing rotates. Or the group is set correctly but individual agents have not enabled Auto-assign tickets on their own profile, which quietly removes them from the rotation. Or nothing is putting tickets into the group in the first place, because Freshservice rotates within a group but relies on the Workflow Automator or your email setup to choose it.
What is the difference between Freshservice and Freshdesk ticket assignment?
They are separate products with separate assignment models. Freshdesk uses Automatic Ticket Assignment under Admin, Team, Groups, with round robin and a load-balanced mode where you cap tickets per agent, gated to Pro and Enterprise, and skill-based assignment on Enterprise only. Freshservice uses group round robin plus the Ticket Assignment Policies framework for workload and work-schedule ranking. Rules do not carry across.
Keep reading
More on assigning help desk tickets fairly once group rotation stops being enough.
- Round robin ticket assignment across eight help desks - Which tools include rotation, which gate it, and what each one cannot do.
- Freshdesk ticket assignment - The same setup on the customer support side of the Freshworks suite.
- Support ticket routing - Triage by skill, priority, and live workload rather than by turn order.
- How to balance support team workload - Why ticket counts hide the imbalance that actually burns agents out.
More use cases
Related features
Stop hand-sorting your incoming work
Let Assigner route it to the right available person by skill, workload, and availability, using rules you control. Nothing sits unassigned and no one gets cherry-picked. Every assignment shows why.