The Short Answer
Omni-Channel isn't a distribution mechanism; it's a capacity model. At any given moment, it asks one question: how much work can this agent handle right now? If the answer to that question is incorrect—perhaps because chat and email are assigned the same weight—then routing will function exactly as configured but will negatively impact service.
Therefore, the correct workflow is: first, define the capacity model and weights, then skills, then Entitlements and Milestones, and only at the very end, escalation automations.
The Capacity Model: The Determining Factor
Omni-Channel assigns a "work quota" (Capacity) to each agent and a weight to each work item. A contact center that assigns a uniform weight to all channels will experience one of two outcomes: chat agents collapse under heavy load, or agents handling emails appear busy when they are, in fact, available.
A reasonable starting point for calibration:
| Work Type | Characteristic | Recommended Relative Weight |
|---|---|---|
| Phone Call | Fully synchronous | Consumes all capacity |
| Live Chat | Synchronous with short breaks | High, typically 2-3 concurrent at most |
| Email / Form | Asynchronous | Low |
| Case Awaiting Customer | Inactive | Zero - must release capacity |
The last point highlights a common error: a Case awaiting a customer that continues to consume capacity makes agents appear busy when they have no active work.
Skills: Less Is More
Skills-Based Routing sounds like an obvious improvement, but in practice, it's a frequent source of stuck requests. The more skill requirements added, the higher the probability that no available agent meets all of them.
Three rules to prevent this: define skills only when their absence truly prevents handling; define a Fallback level for each requirement that activates after a defined waiting period; and monthly check how many requests were assigned via Fallback – a high percentage indicates the model doesn't match contact center staffing.
Entitlements and Milestones: From Commitment to Mechanism
An SLA that only appears in a report is retrospective reporting. Entitlements and Milestones transform it into an active mechanism:
- Entitlement defines which service level is due to which customer – typically one default and a few contractual exceptions.
- Milestone defines the measured time points: first response, periodic update, resolution.
- Business Hours determine when the clock runs and must be configured for each time zone and channel separately.
- Stopped Time freezes the timer when awaiting the customer – without this, metrics penalize the contact center for customer behavior.
- Milestone Actions generate alerts and escalations before the breach, usually around 75-80% of the time.
The guiding principle: if the first alert arrives after the breach, the mechanism measures but doesn't manage.
Fundamental decisions regarding Case definition and the SLA clock are detailed in Service Cloud Implementation.
How to Tell the Model Isn't Holding Up
Five early signs, before monthly metrics reveal a problem:
- A high percentage of assignments via Fallback – skills don't match staffing.
- Requests in the assignment queue for more than a few minutes – lack of capacity or a missing Overflow rule.
- Agents reporting high load while the capacity report shows availability – incorrect weights.
- An unusual concentration of SLA breaches at a consistent time of day – a staffing issue, not a routing problem.
- A high rate of assigned and immediately abandoned requests – agents refuse work that doesn't suit them.
Ongoing Measurement
| Metric | What It Reveals |
|---|---|
| Time in Assignment Queue | Does the model find an agent in time? |
| Average Capacity Utilization | Are the weights realistic? |
| Breaches by Milestone | Exactly where the SLA is broken |
| Rate of Prevented Escalations | Does the early alert work? |
| Breach Gaps Between Channels | Is a specific channel unfairly treated in routing? |
Implementation Order
Start with one channel, a single Entitlement, and no skills. Calibrate the weights against real-world data for two weeks. Only then, add a second channel and skills. Full deployment on a single day makes it impossible to identify which component caused the overload and usually ends with routing being disabled and a return to manual queues.
Summary
Omni-Channel is a capacity model, not a distribution model, and an SLA is an alert mechanism, not a report. These two principles determine whether the contact center will operate according to the system or find ways to circumvent it – and the difference becomes apparent by the first week of operation.