Because boosted emails route ahead of Tasks, the breadth of your Priority Boost rules directly affects how quickly Tasks get routed. This article covers common configuration pitfalls, how to detect them, and how to design boosts that prioritize the right Conversations without blocking Task routing.
How boost breadth affects Task routing
Every email that matches at least one Priority Boost rule is considered "boosted." Boosted emails always route ahead of Tasks, regardless of the Task's due date. When most emails in an Inbox match a boost rule, agents almost always have a boosted email to pick up first — and Tasks in that Inbox rarely get a turn to route. The broader your boost conditions, the more emails get boosted, and the fewer opportunities Tasks have to route.
How to tell if your boosts are too broad
You don't need to calculate an exact percentage. The primary symptom is observable: if Tasks in an Inbox are consistently overdue while emails continue routing, your boosts are likely matching too large a share of email traffic in that Inbox. When investigating Task backlog, start by reviewing which Priority Boost rules include the affected Inbox. If a boost's conditions are broad enough that most Conversations in the Inbox would match, that boost is the likely cause.
Anti-pattern: Inbox-only boosts
A boost that uses only an Inbox condition (e.g., "Inbox is US Team") without additional narrowing conditions will match every email in that Inbox. This effectively makes every email in that Inbox "boosted" and prevents Tasks from routing.
What to do instead: Add at least one additional condition that limits which Conversations qualify for the boost. Examples include a wait-time or due-date threshold, a specific Topic, a Channel filter, or a custom attribute condition.
A useful test when creating or reviewing a boost: Ask yourself, does every Conversation in this Inbox match these conditions? If the only condition is the Inbox itself, the answer is yes, and the boost will affect all email traffic. Adding at least one narrowing condition ensures the boost targets a subset rather than everything.
Anti-pattern: Flat boosts (same size applied uniformly)
A boost that applies the same Boost Size (e.g., Small) to the majority of Conversations in an Inbox doesn't change the relative ordering of those Conversations — they all receive the same uplift. Its only practical effect is marking most Conversations as "boosted," which blocks Task routing without providing any routing benefit.
How to detect this: If a boost applies a uniform Boost Size to most traffic in an Inbox without differentiating between Conversations based on urgency, topic, or Customer attributes, it is likely a flat boost.
What to do instead: Either remove the boost (within-Inbox ordering won't change if the Boost Size was the same for everything) or add conditions that differentiate which Conversations genuinely need prioritization.
Strategy: Use wait-time conditions to create Task routing windows
You can add a Wait Time or Due Date condition to a boost so it only fires on Conversations that have been waiting longer than a configured threshold. This creates an "unboosted window" at the beginning of each conversation's lifecycle during which Tasks can compete normally for routing.
How it works: When a new email arrives in a boosted Inbox, it initially enters the queue without a boost. After the configured wait time, the boost kicks in and the email receives its priority uplift. Tasks get routed during the unboosted window before the boost activates.
Trade-off: Conversations that qualify for the boost won't immediately leapfrog other work. They get that priority only once they've been waiting past the threshold. For an agent who handles both specialty and frontline Inboxes, a brand-new specialty Conversation would briefly compete at parity with frontline traffic before the boost takes effect.
How to tune: The right threshold depends on your queue depth, agent count, and how quickly specialty or high-priority work needs to be prioritized. Start with a conservative value, monitor whether Tasks begin draining, and adjust from there. If Tasks still back up, increase the threshold. If Customers or agents notice delayed prioritization on high-priority work, lower it.
Strategy: Trim Inbox lists on broad boosts
If a single boost rule lists many Inboxes, audit the list periodically. Inboxes may have been added over time that don't match the boost's original intent — for example, a "Specialty Boost" that also includes Frontline Inboxes inflates boost breadth beyond its intended scope. Review each Inbox in the rule and confirm it matches the boost's stated purpose. Remove Inboxes where the boost doesn't align with the team's function.
Recommended review approach
Periodically review your boost configuration, especially when:
Tasks in key Inboxes are backing up past their due dates
You've recently added new Inboxes or changed team structures
Agents report that Tasks aren't routing while emails continue to flow
When investigating, check each boost rule's conditions against the affected Inbox and ask whether the conditions are narrow enough to target a subset of traffic or so broad that they match everything.