Settingsbeginner

What are Teams?

Teams group your agents into functional units — by skill, language, channel, region. Used by routing automations, SLA assignment matrix, opening hours rules, and analytics. Users can belong to multiple teams; no team hierarchy today.

4 min read

What are Teams?

Teams organize your agents into functional groups — by skill, language, department, region, or whatever structure fits your operation. Teams are a core building block that connects to routing, SLAs, opening hours, and reporting.

What a team is

  • Name — The label (e.g., Phone Support, Norwegian Email, Tier 2 Escalation)
  • Description — Optional context for what the team handles
  • Members — Users who belong to this team
  • Opening hours rule — Optional opening hours rule tied to the team
  • Default outbound email — Optional default email channel used as the From address when starting new email conversations from this team
  • Replies follow this team — Optional switch, off by default. When on, replies in the team’s conversations leave from the team’s default outbound email. Requires a default outbound email

Beyond grouping users, the team becomes a target for routing decisions across the rest of the product.

Teams and email channels

Teams can be connected to email in two different ways:

  • An email channel can belong to a team for inbound ownership and routing. This decides which team owns incoming email for that channel.
  • A team can have a default outbound email. It is the From address when agents start a new email conversation from the team. It is also the fallback sender for replies when a conversation has no usable email channel of its own (for example, one that started on phone or web chat). If Replies follow this team is on, replies in the team’s conversations go out from the team’s default outbound email first, ahead of the conversation’s own inbox, and the conversation moves to that inbox.

Replies follow this team is off by default. It needs a default outbound email to be set, and it turns off automatically if the default outbound email is cleared.

Changing a team’s default outbound email does not change where inbound email is routed. Inbound ownership comes from the email channel’s team link; outbound defaults come from the team’s default email setting.

What other features use teams

  • Automations — Assign conversation to team X is a common action; team is X is a common condition
  • SLA policies — SLA assignment matrix scopes policies to teams (Premium policy → Premium team)
  • Opening Hours — Rules can be scoped to specific teams
  • Monitor — Filter views by team for supervision
  • Analytics — Group every dashboard by team for performance comparison
  • Voice queues — Inbound calls route to teams via TaskRouter

A clean team taxonomy pays dividends across all of these. A messy taxonomy creates routing headaches everywhere.

Multi-team membership

Users can belong to multiple teams. A bilingual agent who handles both Norwegian and English email might be in Norwegian Email and English Email simultaneously. Routing automations and SLA assignments can target any team they’re a member of.

There’s no concept of a “primary team” — all memberships are equal. If you need primary-team semantics (e.g., for reporting), pair team membership with a custom field like primary_team on the user.

What’s NOT supported today

  • Team hierarchy / sub-teams — teams are flat. You can’t nest “Returns” under “Customer Support” with inheritance. If you need this, model it with naming conventions (CS — Returns, CS — Refunds) and use those individual teams in routing.
  • Team-level role overrides — a user’s role applies tenant-wide, not per-team. A user is Agent or Team Lead across all their teams, not differently per team.
  • Team-direct SLA link — the team config has an opening hours rule field but not a direct SLA link. SLA scoping happens through the SLA policy’s team-assignment matrix, not through the team config. (This is a vault-doc misconception; the actual data flow is policy → assigned-to-team, not team → linked-to-policy.)

Team naming patterns that scale

Once you have 8+ teams, naming consistency matters. Some patterns:

  • <Channel> <Skill> — Phone Support, Email Returns — Channel-specialized teams
  • <Region> <Function> — EU Support, APAC Sales — Geographic teams
  • <Tier> <Department> — Tier 1 General, Tier 2 Technical — Escalation tiers
  • <Language> <Channel> — Norwegian Email, English Chat — Language-divided teams

Avoid generic names like Team A, Misc, or General — six months later, no one remembers the distinction.

Where to start

Tags

Getting StartedConcept