Freshdesk Groups Explained (Support Groups & Assignment)

Group vs team: is there a difference?

Short answer: not really. People say "team" in conversation and "group" in the product, but Freshdesk itself has no separate "team" object. The organizational unit is the group, and you'll find it under Admin → Team → Groups — the menu is literally called "Team," and the things inside it are groups. Per Freshworks' Organizing Agents into Groups documentation, a group is simply a set of agents you manage together so ticket assignment, shared settings, and reporting all happen at the team level.

One detail that trips people up: an agent can belong to more than one group. Your senior agent can sit in Billing, Tier 2 Escalations, and a VIP group at once, and Freshdesk will show them the tickets from all three. That flexibility is the whole point — groups are a lens, not a wall.

What a group actually controls

A group is small on the surface and load-bearing underneath. Each one holds four things that matter:

• Membership — which agents are in the group (and, on higher plans, an assigned agent group of admins/leads who manage it).
• Business hours — the working calendar the group runs on.
• A ticket-assignment method — manual, or one of the automatic routing options.
• Escalation preferences — what happens to a ticket that sits unassigned too long, and how idle agents are handled.

That short list is why groups quietly touch almost every other configuration in Freshdesk. The next two sections cover the two that surprise people most.

Business hours are group-level — and that changes SLAs

Here is the fact that reorganizes how you think about groups: business hours in Freshdesk are assigned per group, and a business-hours calendar can't apply to a ticket unless that ticket is mapped to a group. Each group can carry its own schedule — a EU group on 9–5 CET, a North America group on 9–5 ET, an Asia group on its own hours — so the clock a ticket runs against depends entirely on which group owns it. Freshworks documents this coupling in What are business hours and calendar hours?, and we go deeper on the mechanics in Freshdesk business hours explained.

Because SLA timers can be calculated on business hours, this has a direct consequence: move a ticket from the Billing group to the Tier 2 group and its SLA clock may start counting against a different working calendar. A first-response target of "2 business hours" means something different at 4pm depending on which group's hours are in force. So groups aren't just an inbox filter — they're an input to your service levels. If your SLAs ever seem to breach or pause at surprising moments, the group-to-business-hours mapping is one of the first places to look.

Group-based SLA policies and automations

Groups also give you a scoping handle for two of Freshdesk's most powerful features.

SLA policies can be scoped to specific groups. On Pro and above, you can create multiple SLA policies and, in a policy's conditions, restrict it to selected agent groups — Freshworks calls this out in Configuring multiple SLA policies. The classic example: your Finance group processes refunds and needs a tighter, different set of targets than the general queue, so you give it its own policy. Remember that policy order matters — the first policy whose conditions match a ticket is the one that applies, so put group-specific policies above the catch-all default.

Automations can route by group. Ticket-assignment rules, dispatchers, and other workflow automations can read a ticket's properties and drop it into the right group — for instance, "if subject contains invoice, set group to Billing." This is how tickets reach the correct team before any human touches them, and it's the foundation you build routing on. We cover the wider workflow story in how to automate Freshdesk with AI.

The routing choice: manual vs automatic

Once a ticket is in a group, how does it reach an individual agent? That's the group's ticket-assignment (routing) method, and it's the decision most teams underthink.

1. Manual — nobody is auto-assigned. A supervisor or the agents themselves pick tickets up. Fine for a small, disciplined team or a tier-2 bench where a human should triage before assigning.
2. Round robin — tickets go to online agents in the group in a circular order, so by the end of the day everyone has handled roughly the same number. Even distribution is the goal. (We walk through the setup in how to set up round robin in Freshdesk.)
3. Load-based (intelligent) — instead of pure rotation, it looks at each agent's current workload and capacity, so faster resolvers pull more and nobody gets buried. It optimizes for quick resolution rather than equal counts.
4. Skill-based — tickets route to agents whose skills (language, product) match the ticket, considering capacity.

Per Freshworks' automatic ticket assignment documentation, the automatic methods (round robin, load-based, and skill-based, delivered through Omniroute) are gated to the Pro and Enterprise plans — on lower tiers you're doing manual assignment or legacy round robin. So the plan you're on genuinely constrains how sophisticated your routing can be. Here's the shape of the decision:

For a fuller tour of how assignment works end to end, see Freshdesk ticket assignment explained.

The honest limits — and where an AI layer picks up

Groups are a genuinely solid piece of infrastructure. They're deterministic, they scope business hours and SLAs cleanly, and Omniroute's routing is fair and configurable. But be clear about what a group does and doesn't do.

A group gets a ticket to the right team; it does not answer the ticket. Round robin can hand an invoice question to an available billing agent in seconds — and then that agent still has to read the ticket, look up the account, and write the reply. The routing is fast; the work behind it is exactly as slow as it ever was.

Routing also depends on correct upstream classification. Automations assign to a group based on keywords and fields, so a mislabeled ticket lands in the wrong group, runs against the wrong business hours, and inherits the wrong SLA — quietly. And the more sophisticated routing (load-based, skill-based) is plan-gated to Pro and Enterprise, so smaller teams are often stuck with manual or legacy round robin, which is honest to acknowledge.

This is the seam where an AI agent layer fits — and it's worth understanding the category of AI agents for customer service before reaching for one. Macha is one such layer: it runs on top of the Freshdesk you already use as a native connector, and it does not replace Freshdesk, your groups, or your routing. You connect Macha to Freshdesk with your subdomain and API key, and it works the same tickets your groups already own — drafting or posting grounded first replies the moment a ticket arrives in a group, triaging by intent so the ticket reaches the correct group in the first place, and looking up an order or account 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 — the pricing page has the breakdown.)

The clean division of labour: keep Freshdesk groups as the source of truth for which team owns a ticket, on which clock, under which SLA, and layer an agent on top for the part groups can't do — reading and answering the ticket fast enough that the routing actually pays off.

FAQ

Where do I manage groups in Freshdesk? Go to Admin → Team → Groups. From there you can create a group, add agents, assign business hours, choose a ticket-assignment (routing) method, and set escalation preferences for unassigned or idle tickets.

What's the difference between a group and a team in Freshdesk? There isn't a formal one. Freshdesk's organizational unit is the group — the admin menu is called "Team," but the objects inside it are groups. People use "team" and "group" interchangeably.

Can an agent be in more than one group? Yes. An agent can belong to multiple groups at once and will see tickets from all of them, which is what makes senior agents easy to place across Billing, Tier 2, and VIP queues simultaneously.

Are business hours set per group? Yes. Business hours are assigned at the group level, and a business-hours calendar can't apply to a ticket unless that ticket is mapped to a group. Each group can run its own schedule (e.g. EU, North America, Asia), which in turn affects how business-hours-based SLAs are calculated.

Which group routing methods are plan-gated? Manual assignment is available on all plans. The automatic methods — round robin, load-based (intelligent), and skill-based routing via Omniroute — require the Pro or Enterprise plan (Freshdesk and Freshdesk Omni). Confirm the exact behaviour against your own plan.

Ready to turn a well-routed queue into answered tickets? Start a free trial of Macha and connect it to your Freshdesk in minutes.