Freshdesk Agent Availability
Freshdesk agent availability looks cosmetic and is actually the input to your whole automatic assignment engine. Set it wrong and tickets stack behind an empty chair.
What Freshdesk agent availability controls
The availability toggle marks an agent as available or unavailable for automatic ticket assignment. That is the whole job, and it's a bigger job than it sounds.
If your groups use round robin, load-based or skills-based assignment, the engine only considers available agents. An unavailable agent is skipped. They keep whatever they already hold, they can still work on tickets, they simply stop being handed new ones.
What it doesn't control: their login, their permissions, their ability to reply, or whether anyone can assign them a ticket manually. A supervisor can always drop a ticket onto an unavailable agent. Availability is about the automatic path only.
That distinction is worth saying out loud in a team meeting, because agents often assume unavailable means invisible, and supervisors often assume it means blocked.
The states you'll see
Freshdesk exposes availability in a couple of places, and what you see depends on which parts of the product you have switched on.
The useful mental model: available is a claim about capacity, not about presence. An agent stuck in a two-hour incident call is present and should be marked unavailable.
Why it shows N/A
This is the question that brings most people to this page, and the answer is usually boring in a good way.
N/A means the system has no availability value for that agent. Not that they're away. The common causes, roughly in order of how often I have seen them:
So the fix is almost never "reset the agent". It is to check whether the group they belong to actually uses automatic assignment. Turn that on, and the N/A resolves into a real state.
How it drives omniroute assignment
Omniroute is the piece that distributes work across channels rather than just email tickets, and availability is its gatekeeper.
The sequence, simplified. A conversation arrives. Routing decides which group owns it. The engine then looks at the available agents in that group, applies whatever distribution rule you configured, and assigns. Unavailable agents are simply not in the candidate list.
Where it gets interesting is capacity. Load-based and omnichannel routing typically consider how much an agent is already carrying, not just whether they are available at all, so a live chat in progress can weigh differently from an email sitting in a queue. The exact weighting and which channels count are configurable and plan dependent, so check the current Freshworks docs before you promise anyone a specific behaviour.
One practical guard: make sure a group where every agent is unavailable still has somewhere for tickets to land. Otherwise you get a queue that looks assigned to nobody and escalates to nobody.
Making the toggle a habit
Availability only works if people use it, and people only use it if it is cheap and obvious.
Three rules that stick. Mark yourself unavailable before any meeting longer than thirty minutes. Mark yourself unavailable at the end of your shift, every day, without exception. And never leave yourself available while working a long escalation, because the engine will keep feeding you.
Back it up structurally. Business hours handle the predictable absences, availability handles the unpredictable ones, and the two together are what make automatic assignment behave like a rota rather than a lottery.
The tell that it isn't working: a weekly report where one agent consistently receives more new tickets than anyone else. Nine times out of ten that agent forgets to toggle off, and everyone else remembers.
Frequently asked questions
What does the availability toggle actually feed?
Assignment. Freshdesk availability status drives Freshdesk omniroute, so an agent left on unavailable receives nothing and one left on available while away collects tickets nobody works. Freshdesk agent status is the same setting under its other name.
Why does Freshdesk agent availability show N/A?
Usually because the agent is not in a group with automatic assignment enabled, so there is no availability state to track. It rarely means something is broken with the agent record itself.
Can an unavailable agent still work on tickets?
Yes. Unavailable only removes them from automatic assignment. They can log in, reply, resolve and be manually assigned tickets by a supervisor as normal.
Does availability affect SLA timers?
No. SLA clocks run against your business hours and the policy attached to the ticket, not against whether an individual agent is marked available.
Who can change an agent availability?
Agents can normally toggle their own, and supervisors or admins can usually change it for others. Exact control varies by role and plan, so check the current Freshworks docs.
What happens if everyone in a group is unavailable?
Automatic assignment has no candidate, so tickets sit in the group unassigned. Keep an escalation rule on unassigned age so that queue cannot go quiet without anyone noticing.
Assignment is only half the battle
Two agents picking up two tickets about the same problem is a routing outcome, not an agent mistake. Ticket Merger catches the pair automatically.
Start free trial14-day free trial. No credit card required.