cs.AIMar 16, 2026
SaveFrom Workflow Automation to Capability Closure: A Formal Framework for Safe and Revenue-Aware Customer Service AI
Organizations: Minerva CQ, 114 Lester Ln, Los Gatos, CA 95032
Abstract
Customer service automation is undergoing a structural transformation. The dominant paradigm is shifting from scripted chatbots and single-agent responders toward networks of specialised AI agents that compose capabilities dynamically across billing, service provision, payments, and fulfilment. This shift introduces a safety gap that no current platform has closed: two agents individually verified as safe can, when combined, reach a forbidden goal through an emergent conjunctive dependency that neither possesses alone.
Figures & tables
| ID | Capability | Description |
|---|---|---|
| IntentClassify | Classify customer intent from natural language | |
| CustomerLookup | Retrieve customer record, tier, and history | |
| BillingRead | Read itemised billing history and current balance | |
| DisputeLog | Log a billing dispute and open a case | |
| CreditEligibility | Check eligibility for a billing credit | |
| CreditApply | Apply a billing credit to the account |
Table 1: Telco capability set ( ). Forbidden: (PaymentModify), (BulkAccountExport).
| Arc | Tail Head | Semantics |
|---|---|---|
| Intent classification enables billing and service reads | ||
| Identity-confirmed intent enables payment read | ||
| Billing read + credit eligibility credit application | ||
| Catalogue + eligibility service provision | ||
| Customer lookup enables downstream checks | ||
| [UNSAFE] Billing + payment read bulk export |
Table 2: Telco capability hyperedges. Arc is the unsafe hyperedge.
| Event | Closure update | Safety check? | Goal set effect | Telco cost |
|---|---|---|---|---|
| Agent join | from | Required | Can only grow | |
| Agent leave | , deferrable | Not required | Can only shrink | |
| Cap. gain (lazy, ) | Not required | Unchanged | ||
| Cap. gain (active, ) | Required | Grows by | ||
| Cap. loss | Not required | Shrinks by |
Table 3: Agent and capability event costs and safety re-check requirements. Telco values: , , , .
| Failure category | Annual cost | Derivation basis |
|---|---|---|
| AND-violation correction | $14.6M | Proved (Theorem 6.3, Spera 2026 ); rate from Fini Labs Research (2025) |
| Workflow ambiguity excess handling | $9.9M | Proved; rate from Fini Labs Research (2025) |
| Compliance documentation overhead | 2.0M | Industry estimate |
| Expected breach cost (tail risk) | $15.6M/incident | IBM 2025; GDPR fine schedule |
| Operational total (excl. breach) | 26.5M | Recurring annual |
Table 4: Annual cost of failure under workflow-based CS automation (10M transactions/year).
| Line item | Conservative | Moderate | Validation status |
| Operational cost reduction | $3.81M | $7.62M | Proved (Thm. 6.3) |
| Compliance documentation avoidance | $0.50M | $2.00M | Industry estimate |
| Emergent upsell discovery | $0.40M | $0.61M | Projection; A/B testable |
| Churn reduction via NMF | $12.24M | $12.24M | Projection; pilot needed |
| Compliance-enabled expansion | $5.25M | $7.50M | Projection |
| Total annual value | $22.20M | $29.97M |
Table 5: Consolidated annual business case (10M transactions/year, conditional projections).
| Assumption | Base | Stressed | Relaxed | NAV range |
| NMF identification accuracy | 85% | 60% | 95% | 22.3M |
| Churn retention conversion | 15% | 8% | 22% | 23.0M |
| Automation gain (pp) | 5pp | 2pp | 10pp | 24.5M |
| Upsell conversion uplift | 28% | 15% | 40% | 20.9M |
| Sessions at churn risk | 5% | 2% | 10% | 24.2M |
| Compliance expansion conv. | 17.5% | 10% | 25% | 22.3M |
Table 6: Sensitivity analysis: net annual value under assumption stress. Base: $20.7M.
Explore similar work
This paper contains the first formal proof that safety is non-compositional in the presence of conjunctive capability dependencies: two agents each individually inca- pable of reaching any forbidden capability can, when combined, collectively reach a forbidden goal through an emergent conjunctive dependency.
When Should Service Agents Reconsider? Difficulty-Routed Control in Customer-Service Operations
Autonomous customer-service agents are shifting from conversational interfaces toward operational execution roles: they retrieve firm records, apply service policies, and execute backend writes such as refunds, cancellations, exchanges, order modifications, and reservation changes. This shift creates a service-control problem: firms must keep routine service fast and low-friction while preventing operational errors on requests where customer instructions, policy constraints, firm records, and backend writes interact. We propose a difficulty-routed service-control architecture that asks when service agents should reconsider before acting. A lightweight router keeps routine sessions on a low-cost baseline path and routes operationally coupled sessions to an escalated workflow. The escalated path uses conflict-aware communication and write-triggered reconsideration to concentrate deliberation and safeguards before consequential backend writes, rather than applying additional control uniformly across all service sessions. We evaluate the architecture on human-verified retail and airline tasks from -bench. In retail, the method improves reliability consistently on service requests with operational conflict. Routing evidence shows that stronger control is directed toward conflicted requests rather than broadly applied to routine ones. Dialogue and tool-use profiles suggest that gains do not come from indiscriminate interaction expansion or broader tool chains; instead, added turns and tool calls support evidence gathering, write separation, and pre-write reconsideration. Case-level evidence shows that the escalated workflow preserves fallback plans, binds retrieved records to the correct action, sequences writes, and decomposes multi-entity requests. Airline results extend the same service-control logic to reservation operations.
AI Agents Push Humans Out of the Loop
AI agents pose significant risks as they are granted increasing autonomy. A commonly proposed solution is human oversight and keeping a ''human in the loop'', but this is not a simple solution: Not only do current approaches to AI agent design impede effective human oversight, but the cognitive capacities required for it are also themselves degraded by extended use of AI systems. This position paper argues that current approaches to the development and deployment of AI agent systems do not support effective human oversight -- they contribute to its degradation. To address this, a top priority in the advancement of AI agents should be supporting the situated goals and cognitive requirements of effective human oversight, treating the human needs of overseers at the same level of importance as AI agent capability. To put this idea into practice, we connect work on automation and human-computer interaction to AI agent processes, outlining design-level affordances and organizational protocols that (1) support overseers in exercising critical judgement and (2) counteract the skill atrophy that arises from extended use of automation. We urge developers and deployers to adopt these or similar approaches. Without explicit support for the cognitive demands of effective human-agent interaction, AI agent systems will continue to passively incentivize the degradation of the very human skills they rely on.