What problem does it solve? Billing complaints mix customer-specific incidents with broader product-truth questions, and answering from pricing pages or memory produces wrong refunds, wrong policy answers, and missed product defects. This Skill classifies billing incidents, verifies claims against the actual code, and keeps financial actions gated behind explicit permission. ## Core Features & Use Cases - Incident Classification: Sorts billing issues into five categories — duplicate subscriptions, multi-seat vs accidental duplicates, failed checkout, broken self-serve controls, and product defects — each with a distinct fix path. - Code-Verified Entitlement Claims: Traces pricing and entitlement statements (per-seat billing, quota resets, cancel behavior) to the checkout, entitlement, and billing-portal code that actually enforces them. - Permission-Gated Financial Actions: Treats refunds, credits, and cancellations as explicit-permission-required, producing a diagnosis and recommendation rather than executing changes autonomously. - Use Case: A customer reports being charged twice. The Skill confirms whether it is a true duplicate or an intentional second seat, checks what the code actually provisioned, and outputs a structured handoff with customer impact, product truth, and a recommended action awaiting approval. ## Quick Start Ask the assistant to diagnose a customer billing complaint, for example: a customer says they were charged twice — classify the incident, verify what the code enforces, and recommend next steps.
