Standard operating procedure · CS3C · Customer Service
Recurring Issue Analysis
Analytical procedure owned by Tier-2 Technical in Customer Service. 5 numbered steps, 1 of them a person deciding and 4 of them agent work … more
Procedure code
CS3C
Analytical
Rule versions in force
v5.3 · v5.2
2 governing rules stacked over it
In force since
2024-11-26
Earliest effective date across those rules
Last reviewed
2026-06-26
Latest review date across those rules
Rules approved by
1
Director, Technical Support
Rule health
2/2
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 recurring issue analysis to one repeatable standard inside Tier-2 Technical, part of Customer Service. more
Entry condition
Runs analytical. Starts when the cycle calendar fires.
Exit condition
The unit clears raise problem. more
In scope
- Every unit of recurring issue analysis raised inside Tier-2 Technical, 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 engineering 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
Tier-2 Technical Orchestrator
Accountable person
Director, Technical Support
The end of the escalation path. Above them sits Customer Service Chief of Staff for the function.
That team’s remit
Owns escalated case work end to end inside Customer Service. more
That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.
Autonomy
68% now · ceiling 76%
Diagnosis and workarounds are agentic. more
The procedure, step by step
5 numbered steps · 1 of them stop for a person
A step is one station on the line. more
| No. | Step | Who does it | What happens | System of record | Time on the step | In flight |
|---|---|---|---|---|---|---|
| 01 | Cluster cases Agentworkflow | Diagnostic Agent | Diagnostic 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 Management | 14.9 hrsstandard 28.4 hrs | 25 |
| 02 | Quantify impact Agentworkflow | Log Analysis Agent | Log Analysis 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 Platform | 3.0 hrsstandard 5.0 hrs | 39 |
| 03 | Draft findings Agentworkflow | Reproduction Agent | Reproduction 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 Management | 8.2 hrsstandard 16.6 hrs | 15 |
| 04 | Review HumanpolicyDecision | Director, Technical Support Releases: Director, Technical Support | Work stops. Director, Technical Support 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 escalated case decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Customer Relationship Management | 21.7 hrsstandard 25.3 hrs | 4 |
| 05 | Raise problem Agentworkflow | Workaround Agent | Workaround 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 engineering | Workforce Management | 6.2 hrsstandard 9.9 hrs | 11 |
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. more
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. more
Nothing has happened yet. more
- 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 76% autonomy ceiling and this run sits at 60% 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.
One decision, held by Director, Technical Support. more
- 04 Review — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
This is a run, not a forecast. more
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. more
The second clock is the allowance. more
A decision may be handed to the agent lane only if two things hold … more
The run reads the station rows only. more
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. more
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. more
No break below was chosen. more
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 2.2 days
now Cluster cases · Diagnostic Agent · 15 hrs
As the ledger has it
the same stations, plus 2 categories the estate already counts
0 min of 2.3 days
now Cluster cases · Diagnostic Agent · 15 hrs
What breaks, and where it is counted
No break below was chosen. more
What the two runs say together
2 counted categories land on this procedure. more
What this run cannot claim
These breaks are shown together on one unit so the shape of a bad day fits on one screen. more
Two clocks run. Worked time is the sum of the time the work is actually being done … more
Roles and responsibilities
6 named parties
The responsibility grid is assigned by a rule, not lifted from a chart. more
| Party | RACI | Steps | Duty | Escalates to |
|---|---|---|---|---|
Tier-2 Technical Orchestrator orchestrator | Runs the line | 0 | Sequences this line, holds its timetable and decides what has to surface to a person. more | Raises to Director, Technical Support when a unit falls outside the envelope or confidence drops below the floor. |
Diagnostic Agent agent A3% autonomy · ceiling A3% 95% clean · 5% overridden | Responsible | 1 | Executes the tier-2 technical step it owns, posts its evidence, and hands the unit to the next stage. | Escalates to Director, Technical Support when the unit falls outside the decision envelope or confidence drops below the floor. |
Log Analysis Agent agent A3% autonomy · ceiling A3% 99% clean · 8% overridden | Responsible | 1 | Executes the tier-2 technical step it owns, posts its evidence, and hands the unit to the next stage. | Escalates to Director, Technical Support when the unit falls outside the decision envelope or confidence drops below the floor. |
Reproduction Agent agent A3% autonomy · ceiling A3% 96% clean · 3% overridden | Responsible | 1 | Executes the tier-2 technical step it owns, posts its evidence, and hands the unit to the next stage. | Escalates to Director, Technical Support when the unit falls outside the decision envelope or confidence drops below the floor. |
Director, Technical Support person | Accountable and responsible | 1 | Holds 1 decision on this line. more | Accountable to Director, Technical Support for the decisions held here. |
Workaround Agent agent A3% autonomy · ceiling A3% 96% clean · 8% overridden | Responsible | 1 | Executes the tier-2 technical step it owns, posts its evidence, and hands the unit to the next stage. | Escalates to Director, Technical Support when the unit falls outside the decision envelope or confidence drops below the floor. |
Decision points and escalation
1 places this procedure stops
04 · Review
21.7 hrsHeld for a named human when the unit exceeds the escalated case decision envelope, when confidence falls below the floor, or when a policy clause is engaged.
Director, Technical Support
Handoffs out of this procedure
Step 05 Raise problem passes the work to engineering.
The rules this procedure runs inside
2 governing rules
Tier-2 Technical Decision Envelope
activeCS3-POL-200 · envelope · vv5.3
Agents in this lane may act without a human when the escalated case sits inside the stated value, risk and confidence envelope. more
Approved by Director, Technical Support · in force 2026-06-20 · reviewed 2026-06-21
Binds Diagnostic Agent, Log Analysis Agent, Reproduction Agent, Known-Error Match Agent, Workaround Agent, Engineering Handoff Agent
Global · EU
Tier-2 Technical Evidence Standard
activeCS3-POL-201 · evidence · vv5.2
Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more
Approved by Director, Technical Support · in force 2024-11-26 · reviewed 2026-06-26
Binds Diagnostic Agent, Log Analysis Agent, Reproduction Agent, Known-Error Match Agent, Workaround Agent, Engineering Handoff Agent
APAC
Systems this procedure touches
4 named · 0 connected
System attribution is a rule, not a reading. more
| System | Vendor | Domain | Criticality | Steps | Connection |
|---|---|---|---|---|---|
| Customer Relationship Management | Salesforce Sales Cloud | crm | critical | 2 | modeled |
| Contact Center Platform | Genesys Cloud CX | service | high | 1 | modeled |
| IT Service Management | ServiceNow ITSM | itsm | high | 1 | modeled |
| Workforce Management | NICE WFM | service | medium | 1 | modeled |
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
2.2 days
Summed from the time each step sits, standard 3.6 days — running at 63% of the standard.
Touchless
53%
Agent share
80%
A week
88
In flight
94
Effort a week
1,301 human minutes · 1,937 agent minutes
Volume multiplied by the time on each step. more
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 … more
| Gate | What trips it | Who releases it | Clock | Waivable |
|---|---|---|---|---|
Refund or remedy above $500 approval | Any single remedy exceeding $500 in customer value | Service manager | 4 business hours | No |
Vulnerability or hardship indicator escalation | Any signal of hardship, bereavement, distress or safety risk | Trained human specialist | Immediate | No |
Legal complaint or regulatory reference escalation | Any legal threat, regulator mention or formal complaint | Legal and service leadership | 2 hours | No |
Departure from published remedy approval | Any resolution outside the published remedy catalog | Service manager | 1 business day | No |
Next to it on the same team
Tier-2 Technical
What this document is and is not
These procedures describe the modeled estate. more
Actions
What is waiting on a person
What one procedure document gives you, and what to check before you treat it as the standard.
named approvers appear across the library
Every decision point on every procedure carries a job title, not a queue. more
steps in the library hand their unit to another function
A handoff is where a procedure stops being one team’s problem. more
controls exist in the estate, and they belong to no procedure in particular
Controls and exception classes are held estate-wide. more
Operations
What this desk is allowed to start
A surface that only reports is not operable. more
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. more
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. more
Current distribution
2,748 steps
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 more
Not holding on the record
A procedure here carries a version, an approver, an in-force date and a last-review date. more