Logo
ScienceStack
Table of Contents
Fetching ...
Sign In

From Workflow Automation to Capability Closure: A Formal Framework for Safe and Revenue-Aware Customer Service AI

Cosimo Spera, Garima Agrawal, Riccardo De Maria

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.

From Workflow Automation to Capability Closure: A Formal Framework for Safe and Revenue-Aware Customer Service AI

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.
Paper Structure (74 sections, 6 theorems, 9 equations, 8 tables)

This paper contains 74 sections, 6 theorems, 9 equations, 8 tables.

Table of Contents

  1. Introduction
  2. The State of Customer Service Automation in 2026
  3. The Formal Gap
  4. Scope and Contributions of This Paper
  5. Related Work
  6. AI safety guardrails and LLM alignment.
  7. Agentic AI orchestration safety.
  8. Workflow-based CS automation.
  9. Business value of CS automation.
  10. Compositional verification and formal methods.
  11. The Capability Hypergraph Framework: A CS Primer
  12. Capabilities as the Unit of CS Analysis
  13. Conjunctive Dependencies in CS Workflows
  14. Closure, Planning, and the Safety Boundary
  15. The Telco Case Study
  16. ...and 59 more sections

Key Result

Proposition 5.1

Let $A_{\mathrm{billing}}$ be the Telco billing agent configuration and $A_{\mathrm{service}}$ the service agent configuration, as defined in §4. From the joint session state $A = A_{\mathrm{billing}} \cup A_{\mathrm{service}}$:

Theorems & Definitions (15)

  • Definition 3.1: CS Capability Set
  • Definition 3.2: CS Closure and Safe Region
  • Proposition 5.1: CS Upsell Discovery
  • proof
  • Proposition 7.1: Safety-Value Duality
  • proof
  • Proposition 7.2: Domain Transfer
  • proof
  • Definition 8.1: Agent-Level Events
  • Proposition 8.2: Agent Join Safety and Closure
  • ...and 5 more