Service level (SL)

What it is

Service level turns “we answer quickly” into a checkable promise. It has two parts: a share of contacts and a time threshold. For calls the threshold is usually seconds, for messengers it is minutes. The pair is chosen by the business, not borrowed from someone else, because the right target depends on what clients expect and what the line can afford.

How it is calculated

SL = contacts answered within the threshold / all incoming contacts × 100%.

An illustrative example: in an hour 200 messages arrived, 150 got an answer within 5 minutes. SL = 150 / 200 = 75% at a 5-minute threshold. Agree in advance what to do with contacts the client abandoned before an answer: some teams exclude very short abandons, others count every abandon as a miss. Both are valid if the rule is fixed and the same every month.

Why it matters

SL is the main input for staffing. It connects the number of people on shift with what the client experiences. A daily SL can look fine while certain hours collapse completely, which is why it is read by interval, usually every 15 or 30 minutes. A drop in SL is often the first visible sign of a scheduling gap, a spike in volume or a rise in handle time.

The typical mistake

Chasing SL at the cost of everything else. Agents rush, transfer and close contacts early to free the line, and repeat contacts grow. Another trap is reporting one monthly number that hides the bad hours. Read SL by interval, next to abandon rate and first contact resolution, and treat a miss as a planning question before it becomes a discipline question.