LensReading which lens this session carries.
Every coverage statement

Function coverage

Customer Service

The platform observes 85.0% of the 42,800 items a week in scope here, reconstructs 10.0%, and estimates that 2,140 happen where it cannot read them.

The method behind this statement

Source system count · owned by Chief Customer Officer · Function head

Observed is the contact center count.

Observed comes straight from what the connected systems return. The remainder is split between what the platform can reconstruct and what it is told exists.

What is happening in the unseen share

Escalations handled by an account manager outside the contact center.

Who has signed for it

Nobody. This figure rests on its method alone.

An attestation would not turn an estimate into a measurement.

Work filed here that the platform could not see

1 item has been filed by somebody who did the work off-platform.

Customer escalation settled by the account managerRecalled · pending
IN-0005 · Wei Lin Tan · Customer Service · escalations

Gaps raised against this function

1 gap in a chain that something must have filled.

Case escalated → Case closedCandidate · moderate

An account manager is handling the escalation outside the contact center.

SP-0005 · 190 instances · median gap 44.0 hours

What this statement is, and what it is not

Coverage can only ever be estimated from the outside.

A coverage statement is disputable by design.

Compare against every other statement