Set up a tiered support team (Tier 1 → Tier 2 → Specialist)

A tiered support model — frontline agents handle the routine stuff, seniors handle harder cases, specialists handle the rest — is a common scaling pattern. Atender doesn’t have a dedicated “escalation” feature; you build the model out of teams, channel defaults, and automation rules. This recipe gives you the concrete setup.

What you’ll end up with

• Tier 1 — General team receives every new conversation by default on all channels
• Tier 2 — Senior team picks up conversations Tier 1 reassigns, or that an automation rule sends directly based on a tag
• Specialists — Billing / Technical teams handle specific topics, routed by content auto-tagging

Three teams, three channel default settings, and three or four automation rules. No new concepts beyond what’s already in the product.

Before you start

• Admin permissions on Teams, Users, and Automations
• Users already invited (at minimum: a few people for each tier)
• A clear idea of who escalates to whom — the recipe assumes a linear T1 → T2 → Specialist flow, but you can adjust

Step 1 — Create the three teams

In Settings → Teams, create:

• Tier 1 — General — Frontline support, all new conversations land here — Most of your support team
• Tier 2 — Senior — Senior agents handling complex cases — A subset — your most experienced 2–4 agents
• Specialists — Billing — Finance-savvy team for invoice / payment issues — 1–2 agents with billing knowledge

If you need more specialist teams (Technical, Returns, Compliance), create them with the same pattern.

Detailed steps: Create a team.

Step 2 — Point all channels at Tier 1

For every active channel, set Tier 1 — General as the default team. New conversations always start with Tier 1.

• Email inboxes — Settings → Email → each inbox → Default team
• Voice numbers — Settings → Voice → each call queue → Team
• Web Chat widget — Settings → Web Chat → widget → Default team
• SMS numbers — Settings → SMS → each number → Default team

See Assign channels to a team for the per-channel detail.

Step 3 — Manual reassignment to Tier 2

Tier 1 agents reassign conversations to Tier 2 using the Assign action in the conversation panel:

1. Open the conversation.
2. Click the team assignee (or the Assign button if unassigned).
3. Type #Tier 2 to filter teams, pick Tier 2 — Senior.
4. Confirm.

This is the human-driven path. No automation needed — Tier 1 decides what gets pushed up. Atender calls this assignment; some teams call it escalation. Both mean the same thing in Atender — moving the conversation to a different team.

Atender doesn’t have a separate “escalate” verb or a dedicated escalation queue. Reassignment between teams is escalation in this model. Train your Tier 1 agents on when to reassign, and the model works.

Step 4 — Automated reassignment to specialists

Create an automation rule per specialist team. The rule fires when a tag is applied — either manually by an agent or automatically by AI auto-tagging.

Recipe — Billing rule

In Settings → Automation Rules → New rule:

• Trigger: Tag Added
• Conditions:
  Tag is billing (or whatever your billing tag slug is)
• Actions:
  Assign team → Specialists — Billing
  (Optional) Add an internal comment: “Auto-routed from tier: billing topic detected”

Save and enable.

Repeat for each specialist team with their respective tag:

• Specialists — Billing — billing
• Specialists — Technical — technical-issue
• Specialists — Returns — return-request

How tags get applied

Either path works:

• Manual — agents tag conversations with billing, etc. Useful when AI auto-tagging isn’t reliable enough.
• AI auto-tag — the Sidekick auto-tag feature applies tags based on conversation content. Set this up in Settings → Tag Management. Best for high-volume teams.

Many teams start with manual tagging, watch which conversations get tagged consistently, and graduate to auto-tagging when they trust the AI’s accuracy.

Step 5 — SLA differentiation (optional but recommended)

Different tiers usually have different response-time expectations. Define separate SLA policies and tie them to teams:

• Tier 1 — General — Standard SLA — 15 minutes
• Tier 2 — Senior — Standard SLA (inherited) — 30 minutes
• Specialists — Billing — Specialist SLA — 1 hour (higher complexity, longer target)

Set this up in Settings → SLA Policies. The policy’s Team Assignment matrix is where you scope each policy to a specific team. See Channel-specific SLAs for the assignment pattern.

Verify it worked

1. Send a test conversation through any channel. It should land in Tier 1 — General.
2. As a Tier 1 agent, reassign to Tier 2 — Senior. Verify it appears in Tier 2’s queue.
3. Add the billing tag to a new test conversation. The Billing automation should auto-reassign within seconds. Check the conversation history — there should be an entry showing the rule fired.
4. Open Analytics → Team Performance and confirm conversations are distributed across the three tiers as expected after a day or two of real traffic.

When this model breaks down

A tiered model assumes most conversations are routine, only some escalate. If your traffic skews the other way — most conversations need specialist knowledge — you’ll be reassigning constantly. Two alternatives in that case:

• Skill-based default routing. Skip the universal Tier 1 default. Use channel-specific defaults: billing-related channels point at Billing Specialists directly. Tier 1 catches whatever’s left.
• Flat team structure. No tiers at all. Just one or two teams that handle everything. Smaller operations often outgrow Tier 1 + Tier 2 complexity.

If you find your Tier 2 team is doing 60%+ of the work, you don’t have a tiered model — you have a misnamed flat model. Rename and simplify.

Variations

Add an after-hours fallback

Wire opening hours so Tier 1 only receives conversations during business hours. After hours, a fallback team (Tier 1 — On-Call, with a smaller member list) takes over.

In Settings → Opening Hours, define Business Hours and After Hours rules. In Settings → Teams, link Tier 1 — General to Business Hours. Create an automation rule: Outside business hours → Assign to Tier 1 — On-Call.

Add an AI Specialist Agent

For high-volume tenants, an AI Specialist Agent can handle Tier 1 directly — answering common questions, gathering context, and only handing off to Tier 1 humans when AI confidence drops or the customer asks for a person.

This isn’t part of the team setup itself — it’s an Agent Stack feature that lives upstream of human assignment. The AI agent handles initial triage; team assignment happens at handover time.

“Specialist Agent” in Atender refers to an AI agent inside an Agent Stack. It’s not the same as a human specialist team. Don’t conflate the two — they’re different layers.

See also

• What are Teams?
• Create a team
• Assign channels to a team
• VIP routing automation recipe — similar pattern, different trigger
• What are Automations?
• What are Specialist Agents? — the AI tier (different concept)