Freshdesk Teams and Groups
Groups and Freshdesk teams sound like synonyms and are not. One routes work, the other gets people talking about it, and mixing them up creates a routing model nobody can explain.
Groups and Freshdesk teams, in one paragraph
A group is a queue. It owns tickets, carries assignment settings, attaches to business hours, and appears in your SLA and escalation rules. If you want a ticket to go somewhere, it goes to a group.
A team is a collaboration unit. It's a named set of people you can pull into a conversation, discuss with, and coordinate through, without that set of people owning a queue. Collaboration features and their naming vary across Freshworks products and plans, so check the current Freshworks docs for exactly what your account exposes.
Put crudely: groups are for routing, teams are for talking. When people mix them up you end up with fifteen queues that exist to describe who sits near whom.
Groups and teams at a glance
| Group | Team | |
|---|---|---|
| Owns tickets | ||
| Drives automatic assignment | ||
| Attaches to business hours | ||
| Used in SLA and escalation rules | ||
| Built for discussion | ||
| Good for cross-functional work | ||
| Right answer for "where does this ticket go" |
Team huddles and what they are for
A huddle is a conversation about a ticket that happens alongside the ticket rather than inside the customer thread. Pull in the people you need, work out the answer, keep the customer-facing reply clean.
Why that matters: the alternative is a private note thread that becomes forty entries long, or a Slack conversation that lives outside the helpdesk and vanishes the moment anyone needs to know why a decision was made.
Use huddles for the genuinely collaborative cases. A bug that needs engineering input. A refund that needs a finance decision. An angry escalation where a lead should see the draft before it goes out.
Do not use them as a general chat channel. The value of keeping the discussion attached to the ticket is that the next person can read it. That value disappears the moment the huddle fills with noise.
Assign to a team, not to a person
This is the rule worth arguing for, and it applies whether the container is called a group or a team.
Named routing breaks on the ordinary. Holiday, sickness, a meeting, a change of role, a resignation.
A ticket assigned to a named human who isn't there sits owned and untouched. It doesn't show in the unassigned queue. It does not fire your unowned-ticket escalation. Nobody notices until the customer chases, which is the worst possible way to find out.
Route to the queue on arrival and let a person claim it. Then your unassigned number is real, your escalations have something to fire against, and everyone who can help can see the work.
The one honest exception is a long-running case where continuity beats availability. Even there, add a rule that hands the ticket back to the group if it goes untouched for a day. Continuity is not a reason to lose a ticket.
A structure that scales
Start with the smallest number of groups that makes routing obvious. Under ten agents, two or three. General, billing, and technical if you genuinely have specialists. More detail on that in the guide to groups and agents.
Then layer teams on top for the cross-functional work that doesn't deserve its own queue. Engineering escalations, the fraud review crew, the people who handle enterprise accounts. Those groups of people need to be reachable, not to own a backlog.
The test for whether something should be a group: can you name what lands there, and who is accountable if it backs up? If both answers are clear, make it a group. If it's really "these people should talk to each other", make it a team and leave your routing alone.
Frequently asked questions
How does team assignment differ from group assignment?
Freshdesk team assignment is about collaboration; group assignment is about ownership. A ticket belongs to a group, and a team is who you pull in to help with it.
What is the difference between groups and teams in Freshdesk?
Groups own tickets and drive assignment, business hours and escalation rules. Teams are collaboration units for pulling the right people into a conversation. Routing decisions belong to groups.
What is a team huddle in Freshdesk?
A discussion attached to a ticket that runs alongside the customer conversation, so several people can work out the answer without cluttering the reply thread or moving the debate into Slack.
Should I assign tickets to a team or an individual?
To the queue, every time. An individual assignee who is on holiday produces a ticket that looks owned, does not appear as unassigned, and escapes your escalation rules entirely.
How many groups should a small support team have?
Two or three under ten agents. General support, billing, and technical if you have real specialists. Adding more creates places for tickets to sit unnoticed.
Are teams available on every Freshdesk plan?
Collaboration features and their exact naming differ by plan and by which Freshworks products you use. Check the current Freshworks docs for what your subscription includes.
One request, two queues, two answers
Split routing means the same customer problem can land in two groups. Ticket Merger detects the pair and merges them before anyone replies twice.
Start free trial14-day free trial. No credit card required.