customer-billing-ops

Investigate and resolve customer billing issues using Stripe subscriptions, invoices, and refunds.

Updated May 19, 2026
One-click install
npx skills add https://github.com/azusagasaku/--claude-config --skill customer-billing-ops-azusagasaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: customer-billing-ops
Source: https://github.com/azusagasaku/--claude-config/tree/main/skills/ecc/customer-billing-ops
Command: npx skills add https://github.com/azusagasaku/--claude-config --skill customer-billing-ops-azusagasaku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Support and operations teams often face messy billing cases—duplicate subscriptions, failed renewals, refund requests, and churn risk—without a clear, safe procedure. This Skill provides a structured workflow to identify the customer, classify the issue, take the safest reversible action, and produce a clean operator handoff. ## Core Features & Use Cases - Customer Identification: Resolve identity from email, Stripe customer ID, subscription ID, or invoice ID and summarize active subscriptions, invoices, and anomalies. - Issue Classification: Distinguish duplicate purchases, real multi-seat intent, failed payments, missing self-serve controls, and product failures before acting. - Safe Remediation: Prioritize reversible actions—restore billing portal access, fix duplicate billing state, refund only affected charges—and document revenue impact. - Use Case: A customer reports being charged twice. Use this Skill to confirm duplicate active subscriptions in Stripe, cancel the extra one, refund the duplicate charge, and draft the follow-up message plus a product-gap ticket for a duplicate-subscription guard. ## Quick Start Use the customer-billing-ops skill to investigate this customer's duplicate Stripe charge and recommend the safest fix with a follow-up message.

Frequently Asked Questions about customer-billing-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle a duplicate Stripe subscription for a customer?▼

Duplicate subscription handling starts by confirming two active subscriptions on the same customer, then canceling the extra one and refunding only the duplicate charge. Keep the remaining active subscription and document the reason before sending a follow-up message.

How to classify a customer refund request before issuing it?▼

Refund classification puts the case into one bucket first: accidental duplicate purchase, deliberate multi-seat purchase, broken product, failed checkout, or missing self-serve controls. Refunds are appropriate mainly for duplicates and product failures, not blindly for every complaint.

Can I use Stripe billing portal instead of building custom account management?▼

Stripe's hosted billing portal is preferred over custom account-management code when it already provides the needed controls like cancellation, payment method updates, and invoice access. Custom dashboards should only be built when the portal cannot cover the workflow.

What customer identifiers work for looking up billing state?▼

Billing lookup works best with the strongest identifier available: customer email, Stripe customer ID, subscription ID, or invoice ID. GitHub usernames or support emails can be used only when they are known to map back to billing records.

When should a billing issue become a product backlog item?▼

A billing issue becomes a product gap when the pain comes from a missing operator surface, such as no billing portal, no cancellation flow, or no duplicate-subscription guard. Handle customer remediation immediately and file the product fix separately.