LensReading which lens this session carries.

Standard operating procedure · CS10B · Customer Service

Intraday Rebalance

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

Procedure code

CS10B

Transactional

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 intraday rebalance to one repeatable standard inside Workforce Management, part of Customer Service.

Entry condition

Runs transactional. Starts when a request lands in the queue.

Exit condition

The unit clears confirm.

In scope

  • Every unit of intraday rebalance raised inside Workforce Management, from the trigger below through to the final step.
  • 5 of the 5 steps, which run without a person present.
  • No decision on this line stops for a person; it runs end to end without one.

Out of scope

  • Anything outside the envelope set by the owning team. With no gate on this line, an out-of-envelope unit is refused rather than held.
  • Work that belongs to another function. This line records no handoff, so nothing leaves it mid-flow.
  • The 1 step carried on the shared AI GBS spine. They are done for this line but not by this 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 · 0 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

Monitor adherence

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 Management1.5 hrsstandard 2.5 hrs5
02

Detect variance

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 Platform1.2 hrsstandard 2.0 hrs44
03

Re-allocate

GBSgbs

Capacity Model Agent

Capacity Model Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, 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 Management58 minstandard 2.3 hrs40
04

Notify

Agentworkflow

Intraday Adherence Agent

Intraday Adherence 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 Management1.6 hrsstandard 3.1 hrs8
05

Confirm

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.Workforce Management1.7 hrsstandard 2.5 hrs2

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.

Person0 stations and 0% of the dwellAgent4 stations and 86% of the dwellShared spine1 station and 14% 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
Customer Relationship Management
IT Service 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 6.9 hrs
the same run against its allowance0 min of 12 hrs
Human
decides · 0
Agent
does the work · 4
GBS
shared spine · 1
run log

Nothing has happened yet.

where the worked time goes6.9 hrs a unit
Agent6.0 hrs · 86%Shared spine58 min · 14%2 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 0 of the 5 stations stop for a person and every one of them still does on this run.
  • There is no decision point on this procedure, so nothing was waived to make the run clean.
  • The owning team is held to a 84% autonomy ceiling and this run sits at 100% 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

This procedure stops for nobody.

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 6.9 hrs

now Monitor adherence · Volume Forecast Agent · 1.5 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 12 hrs

now Monitor adherence · Volume Forecast Agent · 1.5 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

3 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

Responsible2Executes 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.

Intraday Adherence Agent

agent

A3% autonomy · ceiling A3%

91% clean · 13% overridden

Responsible1Watches workforce management continuously. Escalates to Director, Workforce Management when the unit falls outside the decision envelope or confidence drops below the floor.

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.

Director, Workforce Management

person

Accountable0Accountable for this procedure and for the envelope the agents run inside. The end of the escalation path for this line.

Decision points and escalation

0 places this procedure stops

This procedure has no decision point.

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Workforce Management.

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

6.9 hrs

Summed from the time each step sits, standard 12.3 hrs — running at 57% of the standard.

Touchless

84%

Agent share

100%

A week

6,682

In flight

99

Effort a week

0 human minutes · 416 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.