---
id: daily-customer-billing-ops
name: "customer-billing-ops"
url: https://skills.yangsir.net/skill/daily-customer-billing-ops
author: affaan-m
domain: finance
tags: ["finance", "automation", "customer-support"]
install_count: 2700
rating: 4.40 (9 reviews)
github: https://github.com/affaan-m/everything-claude-code
---

# customer-billing-ops

> 快速诊断客户账单问题，自动分析计费历史和交易记录，生成安全修复方案和跟进消息

**Stats**: 2,700 installs · 4.4/5 (9 reviews)

## Before / After 对比

### 账单问题排查

**Before**:

手动查询多个系统和数据库，拼接客户计费历史和交易记录，分析问题根因需要切换多个工具，一个复杂账单纠纷需要45分钟定位原因

**After**:

输入客户标识后自动聚合所有相关账单数据，智能分析异常交易和计费逻辑，5分钟生成问题诊断报告和修复建议

| Metric | Before | After | Change |
|---|---|---|---|
| 诊断时间 | 45分钟 | 5分钟 | -89% |

## Readme

# customer-billing-ops

# Customer Billing Ops

Use this skill for real customer operations, not generic payment API design.

The goal is to help the operator answer: who is this customer, what happened, what is the safest fix, and what follow-up should we send?

## When to Use

- Customer says billing is broken, they want a refund, or they cannot cancel

- Investigating duplicate subscriptions, accidental charges, failed renewals, or churn risk

- Reviewing plan mix, active subscriptions, yearly vs monthly conversion, or team-seat confusion

- Creating or validating a billing portal flow

- Auditing support complaints that touch subscriptions, invoices, refunds, or payment methods

## Preferred Tool Surface

- Use connected billing tools such as Stripe first

- Use email, GitHub, or issue trackers only as supporting evidence

- Prefer hosted billing/customer portals over custom account-management code when the platform already provides the needed controls

## Guardrails

- Never expose secret keys, full card details, or unnecessary customer PII in the response

- Do not refund blindly; first classify the issue

- Distinguish among:

accidental duplicate purchase

- deliberate multi-seat or team purchase

- broken product / unmet value

- failed or incomplete checkout

- cancellation due to missing self-serve controls

- For annual plans, team plans, and prorated states, verify the contract shape before taking action

## Workflow

### 1. Identify the customer cleanly

Start from the strongest identifier available:

- customer email

- Stripe customer ID

- subscription ID

- invoice ID

- GitHub username or support email if it is known to map back to billing

Return a concise identity summary:

- customer

- active subscriptions

- canceled subscriptions

- invoices

- obvious anomalies such as duplicate active subscriptions

### 2. Classify the issue

Put the case into one bucket before acting:

Case
Typical action

Duplicate personal subscription
cancel extras, consider refund

Real multi-seat/team intent
preserve seats, clarify billing model

Failed payment / incomplete checkout
recover via portal or update payment method

Missing self-serve controls
provide portal, cancellation path, or invoice access

Product failure or trust break
refund, apologize, log product issue

### 3. Take the safest reversible action first

Preferred order:

- restore self-serve management

- fix duplicate or broken billing state

- refund only the affected charge or duplicate

- document the reason

- send a short customer follow-up

If the fix requires product work, separate:

- customer remediation now

- product bug / workflow gap for backlog

### 4. Check operator-side product gaps

If the customer pain comes from a missing operator surface, call it out explicitly. Common examples:

- no billing portal

- no usage/rate-limit visibility

- no plan/seat explanation

- no cancellation flow

- no duplicate-subscription guard

Treat those as ECC or website follow-up items, not just support incidents.

### 5. Produce the operator handoff

End with:

- customer state summary

- action taken

- revenue impact

- follow-up text to send

- product or backlog issue to create

## Output Format

Use this structure:

```
CUSTOMER
- name / email
- relevant account identifiers

BILLING STATE
- active subscriptions
- invoice or renewal state
- anomalies

DECISION
- issue classification
- why this action is correct

ACTION TAKEN
- refund / cancel / portal / no-op

FOLLOW-UP
- short customer message

PRODUCT GAP
- what should be fixed in the product or website

```

## Examples of Good Recommendations

- "The right fix is a billing portal, not a custom dashboard yet"

- "This looks like duplicate personal checkout, not a real team-seat purchase"

- "Refund one duplicate charge, keep the remaining active subscription, then convert the customer to org billing later if needed"

Weekly Installs551Repository[affaan-m/everyt…ude-code](https://github.com/affaan-m/everything-claude-code)GitHub Stars152.8KFirst Seen12 days agoSecurity Audits[Gen Agent Trust HubPass](/affaan-m/everything-claude-code/customer-billing-ops/security/agent-trust-hub)[SocketPass](/affaan-m/everything-claude-code/customer-billing-ops/security/socket)[SnykWarn](/affaan-m/everything-claude-code/customer-billing-ops/security/snyk)Installed oncodex513opencode489gemini-cli484antigravity484cursor484cline483

---
*Source: https://skills.yangsir.net/skill/daily-customer-billing-ops*
*Markdown mirror: https://skills.yangsir.net/api/skill/daily-customer-billing-ops/markdown*