LensReading which lens this session carries.

Function cockpit

Customer Service

Agents resolve the routine. Humans hold the difficult conversations.

Autonomy0% / 82%

Phase: Phase 3 — Functional orchestration

Resolve common issues end to end across knowledge, billing, inventory and scheduling systems, while routing vulnerability, ambiguity and emotion to humans who can genuinely help.

Trust score

0

Touchless

0%

Human review

0%

Override rate

0%

Capacity released

40-60% autonomous resolution initially, progressing only when repeat contact and outcomes stay strong

Accountable human

Chief Customer Officer

CoS agent: Customer Service Chief of Staff

How a unit moves: the conductor, the five desks, the agents, and the people

Flow of work

How work actually moves through Customer Service

Work enters on the left. Customer Service Chief of Staff routes it to one of five desks. A named agent does the work. It leaves as cleared, as evidence posted, or as a hold for a person. Every packet you see below is weighted by the real distribution of 161 live units.

See it as a line map

Live units

161

Moving now

86

in flight at a station

Held for a person

14

50 past SLA

Agents on the floor

110

11 sub-functions

Control gates

19

rules a unit cannot pass

Interchanges

13

handoffs out of the function

Flow of work

Customer Service Chief of Staff and the desks reporting to it

Each packet is a unit of work. Desk weighting and the outcome mix are taken from the 161 units live in this function.

WORK ENTERS5 named triggers · 161 units liveCustomer Service Chief of StaffConductor · arbitrates the queue, sets the route, owns the clock86 in flight · 14 held · 50 past SLAStrategyTakes a position14 agents · 20 stations517 in flight · 0 gatesPolicyWrites the envelope15 agents · 19 stations76 in flight · 19 gatesObserveWatches and warns19 agents · 0 stations0 in flight · 0 gatesWorkflowDoes the work45 agents · 106 stations2423 in flight · 0 gatesAI GBSProcesses at scale17 agents · 46 stations894 in flight · 0 gatesKnowledge DoctrineA2Service Analytics ChalleA2Knowledge Management ChaA2Bias MonitorA2Fraud PatternA2Dispatch PolicyA2Quality ScoringA3Dispatch OrchestratorA3Knowledge OrchestratorA3ShrinkageA3Skills MatchingA4BenchmarkA3Job QualificationA4Warranty ValidationA4Metric AssemblyA3+ 11 more on this desk+ 12 more on this desk+ 16 more on this desk+ 42 more on this desk+ 14 more on this deskCleared in envelopeAgent closed it. Sampled later.0 delivered this runCleared, evidence postedClosed with the proof filed.0 delivered this runHeld for a personAgent stopped. Clock running.0 delivered this runresults return to the conductor
Cleared in envelopeCleared, evidence postedHeld for a person0 units completed a full circuit this run

What starts the work

The triggers that put a unit on a line, ranked by live volume.

  • Runs transactional

    Runs transactional. Starts when a threshold is crossed.

    47

  • Runs transactional

    Runs transactional. Starts when an upstream system posts an event.

    36

  • Runs transactional

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

    32

  • Runs transactional

    Runs transactional. Starts when a scheduled window opens.

    20

  • Runs analytical

    Runs analytical. Starts when a leader asks the question.

    10

Where the work goes next

Shared services that run the transaction, and the functions this one hands to.

The five desks

What Customer Service Chief of Staff is actually conducting

Each desk is a layer of the operating model, not a team. The conductor decides which desk owns a unit, then which agent on that desk picks it up.

Takes a position

Strategy

14 agents

Agents that take positions, argue them, and get held to the outcome.

Receives

A question the function has to answer with money or people behind it.

Emits

A written position with assumptions, alternatives priced, and break conditions.

tasks 24h

1,827

in flight

517

held

0

gates

0

confidence 7700%override 1000.0%
  • Knowledge Doctrine AgentKnowledge ManagementA2
  • Service Analytics Challenger AgentService AnalyticsA2
  • Knowledge Management Challenger AgentKnowledge ManagementA2
  • Warranty & Returns Challenger AgentWarranty & ReturnsA2
  • Case Management Challenger AgentCase ManagementA2
  • Tier-1 Resolution Challenger AgentTier-1 ResolutionA2

+ 8 more on this desk

Writes the envelope

Policy

15 agents

The written rules every other agent is bound by, with version and owner.

Receives

A position that has been accepted, plus every regulator and control change.

Emits

Versioned rules that bind every other desk, with an owner and an effective date.

tasks 24h

1,662

in flight

76

held

4

gates

19

confidence 8400%override 900.0%
  • Bias Monitor AgentQuality & CoachingA2
  • Fraud Pattern AgentWarranty & ReturnsA2
  • Dispatch Policy AgentField Service DispatchA2
  • Returns Policy AgentWarranty & ReturnsA2
  • Feedback Policy AgentVoice of CustomerA2
  • Refund & Credit AgentTier-1 ResolutionA2

+ 9 more on this desk

Watches and warns

Observe

19 agents

Continuous sensing of the outside world and of the agents themselves.

Receives

Outside signals and the behavior of the agents themselves.

Emits

Alerts, drift flags, and the evidence the conductor uses to reroute work.

tasks 24h

2,100

in flight

0

held

0

gates

0

confidence 8300%override 1000.0%
  • Quality Scoring AgentQuality & CoachingA3
  • Dispatch OrchestratorField Service DispatchA3
  • Knowledge OrchestratorKnowledge ManagementA3
  • Reopen Detection AgentCase ManagementA4
  • Warranty & Returns OrchestratorWarranty & ReturnsA3
  • Workforce Management OrchestratorWorkforce ManagementA3

+ 13 more on this desk

Does the work

Workflow

45 agents

Doing the work: lines, stations, and live units moving through them.

Receives

Live units of work entering at the first station of a line.

Emits

Cleared work, posted evidence, and holds when a unit leaves the envelope.

tasks 24h

101,109

in flight

2423

held

7

gates

0

confidence 8200%override 500.0%
  • Shrinkage AgentWorkforce ManagementA3
  • Skills Matching AgentField Service DispatchA4
  • Benchmark AgentService AnalyticsA3
  • Localization AgentKnowledge ManagementA3
  • Article Authoring AgentKnowledge ManagementA3
  • Driver Analysis AgentVoice of CustomerA3

+ 39 more on this desk

Processes at scale

AI GBS

17 agents

Repeatable transaction processing run once for the whole enterprise.

Receives

Repeatable transactions handed off from every function on the same spine.

Emits

Settled transactions, a cost per unit, and exceptions back to the owning desk.

tasks 24h

35,213

in flight

894

held

3

gates

0

confidence 8800%override 400.0%
  • Job Qualification AgentField Service DispatchA4
  • Warranty Validation AgentWarranty & ReturnsA4
  • Metric Assembly AgentService AnalyticsA3
  • Parts Availability AgentField Service DispatchA4
  • Disposition AgentWarranty & ReturnsA4
  • Handoff AgentTier-1 ResolutionA4

+ 11 more on this desk

Human lanes

Where the conductor stops and asks a person

The conductor does not decide everything. Materiality routes a unit to a named human role, and the clock keeps running while it waits.

Function Leader

Critical

Blast radius or value beyond what any agent in this function may commit.

waiting

0

oldest

--

  • Nothing waiting in this lane right now.

Process Owner

High

A policy exception inside the function, or a gate the agent is not rated for.

waiting

1

oldest

199h 24m

Approver

Medium

Routine four-eyes on a commitment the agent has already prepared.

waiting

8

oldest

7h 48m

No person required

Low

Inside the envelope. Cleared by the agent and sampled after the fact.

waiting

43

oldest

9h 44m

Walk one unit

Follow the single piece of work with the most at stake

Diagrams argue. A unit proves. Step through the actual route this unit is taking, station by station, and read the evidence written at each action.

CS8C-1001human-holdhigh materialityline CS8C

Feedback theme at ratify

Clara Tanaka · raised by Yuki Okafor · $4.4m at stake · touches 462 downstream things if it goes wrong.

Full unit record
Station 1 of 6

The route

Frame question

cleared

Feedback Ingestion Agent handled this station and released the unit onward. Design dwell here is 55h 4m against an SLA of 112h 40m.

Owned by

Feedback Ingestion Agent

Layer

strategy

Dwell vs SLA

55h 4m / 112h 40m

Evidence trail recorded so far

5 entries. Written when an action is taken, not when a station is passed.

  1. -11964mTheme Extraction Agent Cleared gather evidenceevidence: Inputs, rule version and output hash written to the evidence log
  2. -9571mDriver Analysis Agent Cleared model optionsevidence: Inputs, rule version and output hash written to the evidence log
  3. -7178mChurn Signal Agent Cleared draft positionevidence: Inputs, rule version and output hash written to the evidence log
  4. -4786mClosed-loop Follow-up Agent Cleared challengeevidence: Inputs, rule version and output hash written to the evidence log
  5. -2393mHead of Customer Experience Holding at ratifyevidence: Inputs, rule version and output hash written to the evidence log

SLA breached by 8h 36m

Trace a different unit

CS6A-1013Field job at evidenceCS2C-1015Case at over envelope approveCS2C-1024Case at over envelope approveCS3B-1020Escalated case at trackCS6C-1030Field job at rescheduleCS4A-1040Case at progress

The walk above always picks the unit in customer service with the most at stake right now.

What this view is and is not

Every count, agent, station, gate and unit on this page is read from the live records for Customer Service. The moving packets in the diagram are a visual weighting of that same distribution, not a live message bus: they show where volume goes, not individual transactions in real time. The human lanes are the routing rule, not a staffing model. Chief Customer Officer remains accountable for this function whatever the conductor clears.