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

Watch one unit run any procedure on the happy viable agentified path

Process simulation

Run any Customer Service procedure on the happy viable agentified path

Pick a procedure and press run.

The written procedures

Procedures you can run

33

Stations across them

191

every one of them a step in some run

Decision points

19

stations that stop for a named person

Stop for nobody

14

19 of the 33 still have a person on them

Units a week

85,201

the recorded volume across all of them

33 procedures. Pick one and it runs.
now running
CS4ACase LifecycleCase Management · Transactional · 5,193 a week
speed
worked clock
00:00
allowance clock
00:00
stations cleared
0/7
the happy path, worked time0 min of 13 hrs
the same run against its allowance0 min of 28 hrs
Human
decides · 0
Agent
does the work · 1
GBS
shared spine · 6
run log

Nothing has happened yet.

where the worked time goes13 hrs a unit
Agent1.8 hrs · 14%Shared spine11 hrs · 86%2 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 0 of the 7 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 92% autonomy ceiling and this run sits at 100% unattended, inside it.
  • 1 system is 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.