How channel-to-team routing works

Every inbound conversation is first assigned to its channel’s default team; automation rules can then reassign it, and the team’s routing strategy decides which agent actually gets it. This article explains those three layers and the common ways to arrange them.

One default team per channel

Each channel has one default team. The relationship is one-to-one from the channel’s perspective:

• An email inbox routes new email conversations to one team.
• A voice number routes inbound calls to one team’s queue.
• A web chat widget routes new chats to one team.
• An SMS number routes inbound texts to one team.

A team can be the default for many channels (a “General Support” team can own three email inboxes, two voice numbers, and a chat widget). But each individual channel points at exactly one default team.

Inbound routing vs. outbound email

The channel → default team relationship controls where inbound conversations land. It is separate from a team’s default outbound email setting, which controls which From address is suggested when an agent starts a new email conversation from that team. Configure inbound routing on the channel in Settings → Channels; configure a team’s default outbound email in Settings → Teams.

The three routing layers

When a new conversation arrives:

1. Channel default team is applied first. The conversation is assigned to that team.
2. Automation rules run. Any rule with a matching condition can reassign the conversation to a different team — common reasons: VIP tagging, content-based routing (auto-tagged “billing” → assign to billing specialists), language detection.
3. Agent assignment within the team is then handled by the team’s routing strategy — round-robin, most-available, or manual claim from a queue.

The default-team setting on the channel is the floor. Everything else stacks on top. See What are Automations? for the rules layer.

Common patterns

• One team handles all channels — Same team set as default on every channel. Simplest setup; works for small teams.
• Channel-specialized teams — “Email Support” gets email channels, “Phone Support” gets voice numbers, “Chat Support” gets web chat widgets.
• Region-divided teams — EU number → EU team, US number → US team, APAC number → APAC team. Common for follow-the-sun coverage.
• Tier 1 default + Tier 2 escalation — All channels default to Tier 1. Automation rules escalate to Tier 2 based on tag, sentiment, or customer tier. See Tiered support recipe.

Changing the default team

You can change a channel’s default team at any time. The change applies to new conversations only — already-assigned conversations stay with their current team unless you reassign them manually or via automation.

If you’re consolidating teams (merging “Email — US” and “Email — EU” into a single “Email Support”), reassign in-flight conversations before retiring the old team.

See also

• Assign channels to a team — the per-channel setup steps
• Troubleshooting channel-to-team routing
• What are Teams?