How to Add, Deactivate & Manage Agents in Freshdesk

The two things that decide what an agent costs

Before you add anyone, it helps to know the two levers that move the invoice. The first is agent type. A full-time agent is a core team member who logs in daily and requires a paid user license, billed per agent per month. An occasional agent — think a CEO, a manager who dips in a few times a month, or seasonal field staff — doesn't take a permanent seat. Instead they consume a day pass each time they log into the portal.

The second lever is support agent vs collaborator, but for the add-agent flow you'll almost always be creating a support agent: someone who works tickets directly. Per Freshworks' Understanding Full-time vs Occasional Agents documentation, the day-pass model is what makes occasional agents cheap: a pass is valid until the end of the day (23:59) and does not roll over to the next calendar date. Every Freshdesk plan comes with 3 free day passes to start, and — this is the part people miss — a day pass is not consumed when an occasional agent simply replies to a ticket notification from their email inbox. It's only spent when they actually log into the portal.

Step 1: Add and invite a new agent

Adding an agent sends them an invitation by email; nothing is live until they accept and set a password.

1. Click New Agent in the top bar, or go to Admin → Team → Agents and choose New agent. Freshworks documents the full flow in Add, edit, or delete support agents.
2. Under Agent type, select Support agent, then choose Full time or Occasional.
3. Enter the agent's email address — this is where the invite goes. Optionally set their time zone, language, signature, and photo.
4. Assign a Role (covered in Step 2), a Scope, and any Groups.
5. Save. The agent receives an activation email and appears in your agent list once they accept.

Step 2: Set role, scope, and group

Adding the person is the easy part. What they can see and do comes down to three settings, and they interact in ways that trip people up.

Role controls the permissions — what actions an agent can take. Freshdesk ships default roles like Agent, Supervisor, and Administrator, and on higher plans you can build custom roles with granular privileges. (We break the defaults down in Freshdesk agent roles and scopes explained.)

Scope controls the visibility — which tickets an agent can access at all. You get three levels:

• All tickets — the agent can access every ticket in the help desk.
• Tickets in a group — the agent only sees tickets assigned to the groups they belong to.
• Assigned tickets — the agent only sees tickets assigned directly to them.

Groups control membership and routing — which team an agent belongs to for assignment and reporting. If you're using the "Tickets in a group" scope, group membership is what actually grants an agent access to that queue. Groups are worth setting up deliberately; we cover the model in Freshdesk groups explained.

The common mistake is treating these as one dial. A "Supervisor" role with an "Assigned tickets" scope still can't see the team's backlog — the role gives them power, but the scope hides the tickets. Set both intentionally.

Step 3: Deactivate — don't delete — when someone leaves

This is the single most important distinction in agent management, and it's a billing trap. Per Freshworks' Deactivate or Delete Support Agents guide, the two options do very different things.

To do either, go to Admin → Team → Agents, click the More icon next to the agent, and choose Deactivate or Delete.

Deactivate removes the agent from your system while retaining their tickets, articles, and other contributions. The agent moves to a Deactivated Agents list and can be reactivated later. Critically, an agent license is freed up for a new full-time agent. Their open and pending tickets move to the unassigned queue; resolved and closed tickets stay attached to their name until reopened. This is what you want in almost every case — the seat comes back, but your reporting history stays intact.

Delete goes further: it wipes their assignment from tickets, articles, and other contributions permanently. The person is retained only as a contact record. Use this rarely — you lose the audit trail.

There's a billing consequence worth flagging in bold: before you downgrade your plan, you must deactivate or delete enough agents to match your reduced license count, or Freshdesk may reject the downgrade and keep charging you for the extra seats at the next cycle. The seat doesn't free itself; you have to free it.

Full-time vs occasional: which seat to use

Here's a quick decision table for the seat choice, since it's the one that drives cost.

To buy more day passes, go to Admin → Account → Day Passes, where you can also review usage history for the last 90 days. To add full-time seats or change plans, that's Admin → Account → Plans and Billing. (The Free plan includes 2 agent seats to start.)

The honest limits — and where an AI layer fits

Freshdesk's agent management is clean and does exactly what it promises: it provisions humans, scopes their access, and reconciles seats against your bill. But it's worth being clear about what it isn't solving. Every one of these controls is about which human handles a ticket — none of them reduce the number of tickets a human has to handle. If your queue is growing, the native answer is to add seats, and seats cost money linearly.

A few specific edges are also plan-gated and worth naming honestly. Custom roles with granular permissions aren't available on the lowest tiers — you're stuck with the default role set until you upgrade. Agent shifts and availability management, useful for occasional and part-time staff, is a higher-plan feature too, as we cover in Freshdesk agent shifts and availability explained. And occasional agents, while cheaper, still can't be scheduled around the day pass in any granular way — a pass is spent the moment they log in, regardless of how much work they do that day.

This is the seam where an AI agent layer changes the math. The broader category of AI agents for customer service exists to absorb the repetitive, high-volume tickets before they ever need a human seat — which is a different question from "who do I assign this to," and one worth weighing against the build-versus-buy tradeoff before you commit. Macha is one such layer: it runs on top of the Freshdesk you already use as a native connector — it does not replace Freshdesk, your agents, or your seat management. You connect Macha to Freshdesk with your subdomain and API key, and it reads and writes the same tickets your human agents work: drafting or posting grounded replies, triaging by intent, and looking up order or account status through a custom tool that turns a REST API into something the agent can call. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. And credits are consumed per AI action, not per resolution — see the pricing breakdown.)

The clean division of labour: keep Freshdesk as the system of record for who your human agents are and what they can access, and let an AI layer handle the ticket volume that would otherwise force you to keep buying seats.

FAQ

How do I add an agent in Freshdesk? Click New Agent in the top bar (or go to Admin → Team → Agents → New agent), choose the agent type, enter their email address, assign a role, scope, and group, then save. The agent receives an activation email and becomes active once they accept and set a password.

What's the difference between a full-time and an occasional agent? A full-time agent logs in daily and requires a paid license, billed per agent per month. An occasional agent logs in only a few days a month and consumes a day pass each time they access the portal — a pass valid until 23:59 that doesn't carry over. Every plan includes 3 free day passes, and no pass is spent if the occasional agent only replies via email notification.

Should I deactivate or delete an agent when they leave? Deactivate in almost every case. Deactivating retains their tickets, articles, and contributions, moves them to a Deactivated Agents list you can reactivate later, and frees up a license. Deleting permanently wipes their assignments from tickets and articles — use it only when you don't need the history.

Does deactivating an agent free up a seat for billing? Yes — deactivating frees the full-time license so it can go to a new agent. But note: before you can downgrade your plan, you must deactivate or delete enough agents to match the lower license count, or Freshdesk may reject the downgrade and charge you for the extra seats.

Can I add AI to Freshdesk without adding more agent seats? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and works the same tickets your human agents do — drafting grounded replies and triaging by intent — so it can absorb repetitive volume without you provisioning another full-time seat. It runs on top of Freshdesk; it doesn't replace it.

Ready to handle more tickets without buying more seats? Start a free trial of Macha and connect it to your Freshdesk in minutes.