Function cockpit
Customer Service
Agents resolve the routine. Humans hold the difficult conversations.
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
Gates, kill switches, and the decision ledger
Governance
Autonomy is only defensible if the brakes are documented
Every gate below names a threshold, an approver, and a clock. Everything the function has decided recently sits in the ledger underneath, whether a person or an agent made the call.
Active gates
0
Pending decisions
0
Approved this cycle
0
Contained or reversed
0
Gate register
The conditions under which an agent must stop and ask.
| Gate | Trigger threshold | Approver | SLA | Waivable |
|---|---|---|---|---|
Refund or remedy above $500 Approval gate | Any single remedy exceeding $500 in customer value | Service manager | 4 business hours | Hard stop |
Vulnerability or hardship indicator Escalation | Any signal of hardship, bereavement, distress or safety risk | Trained human specialist | Immediate | Hard stop |
Legal complaint or regulatory reference Escalation | Any legal threat, regulator mention or formal complaint | Legal and service leadership | 2 hours | Hard stop |
Departure from published remedy Approval gate | Any resolution outside the published remedy catalog | Service manager | 1 business day | Hard stop |
Decision ledger
Immutable record of what was decided, by whom, and how long it took.
- Escalation
Hardship case transferred within 40 seconds
ContainedHighVulnerability Agent detected bereavement language, stopped all automation on the case and warm-transferred the customer to a trained specialist with context preserved.
Vulnerability Agent · 9d 6h ago
- Approval gate
Goodwill remedy above policy band pending
PendingMediumResolution Agent assembled a $1,240 remedy for a repeated fulfillment failure. Held for service-manager decision with cost-to-serve and relationship history attached.
Service manager · 9d 7h ago
Requester can escalate only at this materiality - Escalation
Systemic defect cluster raised to Engineering
PendingHighProactive Service Agent correlated 214 contacts to one firmware release and packaged the evidence for Engineering, Legal disclosure review and Communications.
Customer Service Chief of Staff · 9d 8h ago
Requester can escalate only at this materiality - Oversight
Response path suspended on grounding failure
ContainedMediumQuality Agent detected an answer without a valid source citation in a warranty topic. The response path was suspended and the knowledge gap routed to the content owner.
Quality Agent · 9d 10h ago
Kill switches
Named, tested, and reachable in one click by the accountable human.
- Identity verification failure in a served interaction
- Harmful or unsafe advice detected in an agent response
- Repeated unresolved loop without human offer
- Sentiment escalation without a routing to a person
- Abnormal remedy or refund volume in a short window
Human accountability
Cannot be delegated to an agent at any autonomy level.
- Hardship, bereavement and vulnerable customers
- Safety issues and legal threats
- Large refunds and fraud ambiguity
- Retention exceptions outside published remedies
- Reputational incidents and relationship recovery
Signs for this function
Chief Customer Officer