LensReading which lens this session carries.

Standard operating procedure · CS10C · Customer Service

Outsourcer Allocation

Analytical procedure owned by Workforce Management in Customer Service. 5 numbered steps, 1 of them a person deciding and 4 of them agent work …

Procedure code

CS10C

Analytical

Rule versions in force

v3.2 · v2.6 · v2.4

3 governing rules stacked over it

In force since

2025-03-01

Earliest effective date across those rules

Last reviewed

2026-07-10

Latest review date across those rules

Rules approved by

1

Director, Workforce Management

Rule health

3/3

0 under review · 0 superseded

There is no document register behind this header. The version, the dates and the approver names are read off the governing rules this procedure runs inside, which is the closest thing the estate holds to a document control record. Nobody wrote these procedures. There is no document library behind this page and no Word file anywhere in the estate. Every procedure below is generated from rows this platform already holds: the line and its ordered stations, the owning team and the person accountable for it, the policy items bound to that team, and the governance gates seeded against the function. The steps, the owners, the gates, the approvers, the dwell times and the volumes are read straight off those rows. The sentences that join them together are generated. Read a procedure as the estate describing itself, not as a document somebody signed.

Purpose and scope

What this procedure is for and where it stops

To run outsourcer allocation to one repeatable standard inside Workforce Management, part of Customer Service.

Entry condition

Runs analytical. Starts when a leader asks the question.

Exit condition

The unit clears issue.

In scope

  • Every unit of outsourcer allocation raised inside Workforce Management, from the trigger below through to the final step.
  • 4 of the 5 steps, which run without a person present.
  • 1 decision that stops the line until a named person releases it.

Out of scope

  • Anything outside the envelope set by the owning team. It leaves the line at a gate and becomes the named approver's decision.
  • Work that belongs to another function. This line hands off to procurement and does not follow the unit there.
  • Shared-spine work. This line has none; every step is done inside the function.

Who owns it

Runs the line

Workforce Management Orchestrator

Accountable person

Director, Workforce Management

The end of the escalation path. Above them sits Customer Service Chief of Staff for the function.

That team’s remit

Owns roster work end to end inside Customer Service.

That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.

Autonomy

82% now · ceiling 84%

Forecasting and intraday rebalancing are agentic.

The procedure, step by step

5 numbered steps · 1 of them stop for a person

A step is one station on the line.

No.StepWho does itWhat happensSystem of recordTime on the stepIn flight
01

Model demand

Agentworkflow

Volume Forecast Agent

Volume Forecast Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Customer Relationship Management13.6 hrsstandard 16.5 hrs43
02

Score partners

Agentworkflow

Capacity Model Agent

Capacity Model Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Contact Center Platform11.0 hrsstandard 17.8 hrs8
03

Draft allocation

Agentworkflow

Shift Scheduling Agent

Shift Scheduling Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.IT Service Management2.7 hrsstandard 5.0 hrs32
04

Approve

HumanpolicyDecision

Director, Workforce Management

Releases: Director, Workforce Management

Work stops. Director, Workforce Management reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: Held for a named human when the unit exceeds the roster decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Customer Relationship Management37.8 hrsstandard 2.4 days7
05

Issue

Agentworkflow

Shrinkage Agent

Shrinkage Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Hands off to procurementWorkforce Management10.0 hrsstandard 12.3 hrs22

The swimlane

The same steps, laid out by who is holding the work

Three lanes: a person deciding, an agent working, and the shared services spine.

Person1 station and 50% of the dwellAgent4 stations and 50% of the dwellShared spine0 stations and 0% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Contact Center Platform
IT Service Management
Customer Relationship Management
Workforce Management
Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Run the procedure

One unit walked along that swimlane on the happy viable agentified path

Press run and a single unit enters at station 01. Each station takes exactly the dwell this platform records for it and is held by whoever the estate says holds it.

speed
worked clock
00:00
allowance clock
00:00
stations cleared
0/5
the happy path, worked time0 min of 3.1 days
the same run against its allowance0 min of 4.6 days
Human
decides · 1
Agent
does the work · 4
GBS
shared spine · 0
run log

Nothing has happened yet.

where the worked time goes3.1 days a unit
Person38 hrs · 50%Agent37 hrs · 50%2 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 5 stations stop for a person and every one of them still does on this run.
  • Every one of the 1 decision is still taken by the person who holds it. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 84% autonomy ceiling and this run sits at 50% unattended, inside it.
  • 4 systems are attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.
what would have to change

One decision, held by Director, Workforce Management.

stays with a person
  • 04 Approve — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
what this run is, and what it is not

This is a run, not a forecast.

Happy means nothing goes wrong: no station raises an exception, no gate sends the unit back, no rework loop fires and nothing sits in a queue between stations.

The second clock is the allowance.

A decision may be handed to the agent lane only if two things hold …

The run reads the station rows only.

What this run does not model: arrival patterns, contention between procedures for the same person, shift patterns, weekends, learning curves, and the cost of anything.

Run it again, going wrong

The same unit, the same stations, broken the way the estate already records breaking

This is the same unit on the same stations, breaking.

No break below was chosen.

One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.

As written

5 stations, nothing waiting, nothing sent back

0 min of 3.1 days

now Model demand · Volume Forecast Agent · 14 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 3.2 days

now Model demand · Volume Forecast Agent · 14 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen.

What the two runs say together

2 counted categories land on this procedure.

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen.

Two clocks run. Worked time is the sum of the time the work is actually being done …

Roles and responsibilities

6 named parties

The responsibility grid is assigned by a rule, not lifted from a chart.

PartyRACIStepsDutyEscalates to

Workforce Management Orchestrator

orchestrator

Runs the line0Sequences this line, holds its timetable and decides what has to surface to a person. Raises to Director, Workforce Management when a unit falls outside the envelope or confidence drops below the floor.

Volume Forecast Agent

agent

A3% autonomy · ceiling A3%

92% clean · 8% overridden

Responsible1Executes the workforce management step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Workforce Management when the unit falls outside the decision envelope or confidence drops below the floor.

Capacity Model Agent

agent

A3% autonomy · ceiling A3%

88% clean · 8% overridden

Responsible1Executes the workforce management step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Workforce Management when the unit falls outside the decision envelope or confidence drops below the floor.

Shift Scheduling Agent

agent

A3% autonomy · ceiling A3%

95% clean · 7% overridden

Responsible1Executes the workforce management step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Workforce Management when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Workforce Management

person

Accountable and responsible1Holds 1 decision on this line. Accountable to Director, Workforce Management for the decisions held here.

Shrinkage Agent

agent

A3% autonomy · ceiling A3%

98% clean · 6% overridden

Responsible1Executes the workforce management step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Workforce Management when the unit falls outside the decision envelope or confidence drops below the floor.

Decision points and escalation

1 places this procedure stops

04 · Approve

37.8 hrs

Held for a named human when the unit exceeds the roster decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

Director, Workforce Management

Handoffs out of this procedure

Step 05 Issue passes the work to procurement.

The rules this procedure runs inside

3 governing rules

Workforce Management Decision Envelope

active

CS10-POL-200 · envelope · vv3.2

Agents in this lane may act without a human when the roster sits inside the stated value, risk and confidence envelope.

Approved by Director, Workforce Management · in force 2026-04-03 · reviewed 2026-06-01

Binds Volume Forecast Agent, Capacity Model Agent, Shift Scheduling Agent, Shrinkage Agent, Skill Coverage Agent, Outsourcer Balance Agent

EU · UK

Workforce Management Evidence Standard

active

CS10-POL-201 · evidence · vv2.6

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path.

Approved by Director, Workforce Management · in force 2026-01-24 · reviewed 2026-07-10

Binds Volume Forecast Agent, Capacity Model Agent, Shift Scheduling Agent, Shrinkage Agent, Skill Coverage Agent, Outsourcer Balance Agent

US · Canada

Workforce Management Escalation Rule

active

CS10-POL-202 · escalation · vv2.4

Escalation is mandatory when confidence falls below the floor, when two options sit inside the confidence band, or when a break condition on a ratified position fires.

Approved by Director, Workforce Management · in force 2025-03-01 · reviewed 2026-06-24

Binds Volume Forecast Agent, Capacity Model Agent, Shift Scheduling Agent, Shrinkage Agent, Skill Coverage Agent, Outsourcer Balance Agent

US · Canada

Systems this procedure touches

4 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Customer Relationship ManagementSalesforce Sales Cloudcrmcritical2modeled
Contact Center PlatformGenesys Cloud CXservicehigh1modeled
IT Service ManagementServiceNow ITSMitsmhigh1modeled
Workforce ManagementNICE WFMservicemedium1modeled

0 of the 4 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 3 of them are marked as taking a write back, which is a property of the system, not a live path from here.

How it performs

End to end

3.1 days

Summed from the time each step sits, standard 4.6 days — running at 68% of the standard.

Touchless

71%

Agent share

80%

A week

74

In flight

112

Effort a week

2,265 human minutes · 2,238 agent minutes

Volume multiplied by the time on each step.

Assurance over this procedure

4 governance gates sit above it

The twenty-four controls and eighteen exception classes in this platform are held at estate level …

GateWhat trips itWho releases itClockWaivable

Refund or remedy above $500

approval

Any single remedy exceeding $500 in customer valueService manager4 business hoursNo

Vulnerability or hardship indicator

escalation

Any signal of hardship, bereavement, distress or safety riskTrained human specialistImmediateNo

Legal complaint or regulatory reference

escalation

Any legal threat, regulator mention or formal complaintLegal and service leadership2 hoursNo

Departure from published remedy

approval

Any resolution outside the published remedy catalogService manager1 business dayNo

What this document is and is not

These procedures describe the modeled estate.

Actions

What is waiting on a person

What one procedure document gives you, and what to check before you treat it as the standard.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

A procedure document prints purpose, scope, entry and exit, the numbered steps with the actor on each, the roles and their RACI position, the swimlane, the decision points and escalation, the handoffs, the governing rules with version and approver, the systems by rule and the timings.

Live observability

What the record shows right now

The whole library, by lane, so a single document can be read against the estate it came from.

Current distribution

2,748 steps

Agent, inside the function1,38951%
Agent, on the shared spine85131%
Person deciding at a gate50818%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Half. The document is complete and every actor on it is measured

Not holding on the record

A procedure here carries a version, an approver, an in-force date and a last-review date.