Creating Groups for Routing

Groups help you organize the human side of support. They give Applied a clear way to route work to the right team based on skill, ownership, or operating structure.

What a group is

A group is a set of teammates who should receive a certain kind of work.

Groups are often used for:

Billing support
Technical support
VIP or enterprise support
Regional coverage
Specialized operational teams

When to create a group

Create a group when a category of work should consistently go to the same team or queue.

Good reasons to create a group:

The work needs a specific skill set.
The work belongs to a specific business function.
The team works in a different time zone or region.
The team has different service expectations or response targets.

Do not create a new group for every small variation in work. Too many groups make routing harder to maintain.

How groups affect routing

Groups are a core part of how escalated work gets assigned.

Routing can use groups to:

Send a conversation to the right team automatically.
Keep specialist work away from general queues.
Apply different assignment logic based on the issue type.

This matters most when the AI hands a case off. A strong routing design means the work arrives with the right people the first time.

How groups affect workload

Groups also shape how your team handles capacity.

They help Applied distribute work more sensibly by making it clearer:

Which teammates are eligible for which issues
Which teams should absorb which kinds of volume
Where bottlenecks are likely to form

If one queue consistently struggles, the solution is often a better group design or routing rule, not simply more escalation.

Common group design patterns

Functional groups

Examples: Billing, Shipping, Technical Support, Retention.

Skill-based groups

Examples: Tier 1, Tier 2, specialist review.

Regional groups

Examples: North America, Europe, APAC.

Priority groups

Examples: VIP customers, high-value accounts, strategic partners.

How groups work with escalations

Escalation rules become much more useful when they know where the case should go next.

For example:

Billing issues escalate to the Billing group.
Technical troubleshooting escalates to Technical Support.
High-value customer issues route to a dedicated team.

How groups work with SLAs

Different groups often need different response expectations.

Grouping work correctly makes it easier to:

Measure the right team against the right targets
Keep specialist queues from being treated like general queues
Surface the most urgent work clearly

Best practices

Start with a small number of high-signal groups.
Design groups around real ownership, not idealized org charts.
Keep fallback routing simple when no rule matches.
Review queue health after rollout and adjust gradually.

Common mistakes

Too many groups

This makes rules harder to understand and increases the chance of routing work to the wrong place.

Overlapping groups

If multiple groups seem equally correct for the same issue, the routing logic usually needs simplification.

No clear fallback path

Every routing design should make it obvious where work goes when a case does not match a specialist rule.