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"
1---2name: customer-billing-ops3description: >4 Operate customer billing workflows — subscriptions, refunds, churn triage, billing-portal5 recovery, plan analysis — through connected billing tools like Stripe. Use for "refund a customer",6 "cancel a subscription", "customer can't access billing portal", "churn triage",7 "check subscription state", "duplicate charge".8origin: ECC9metadata:10 source: https://skillmd.com/skills/dabhiram13/customer-billing-ops11---1213# Customer Billing Ops1415Use this skill for real customer operations, not generic payment API design.1617The 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?1819## When to Use2021- Customer says billing is broken, they want a refund, or they cannot cancel22- Investigating duplicate subscriptions, accidental charges, failed renewals, or churn risk23- Reviewing plan mix, active subscriptions, yearly vs monthly conversion, or team-seat confusion24- Creating or validating a billing portal flow25- Auditing support complaints that touch subscriptions, invoices, refunds, or payment methods2627## Preferred Tool Surface2829- Use connected billing tools such as Stripe first30- Use email, GitHub, or issue trackers only as supporting evidence31- Prefer hosted billing/customer portals over custom account-management code when the platform already provides the needed controls3233## Guardrails3435- Never expose secret keys, full card details, or unnecessary customer PII in the response36- Do not refund blindly; first classify the issue37- Distinguish among:38 - accidental duplicate purchase39 - deliberate multi-seat or team purchase40 - broken product / unmet value41 - failed or incomplete checkout42 - cancellation due to missing self-serve controls43- For annual plans, team plans, and prorated states, verify the contract shape before taking action4445## Workflow4647### 1. Identify the customer cleanly4849Start from the strongest identifier available:5051- customer email52- Stripe customer ID53- subscription ID54- invoice ID55- GitHub username or support email if it is known to map back to billing5657Return a concise identity summary:5859- customer60- active subscriptions61- canceled subscriptions62- invoices63- obvious anomalies such as duplicate active subscriptions6465### 2. Classify the issue6667Put the case into one bucket before acting:6869| Case | Typical action |70|------|----------------|71| Duplicate personal subscription | cancel extras, consider refund |72| Real multi-seat/team intent | preserve seats, clarify billing model |73| Failed payment / incomplete checkout | recover via portal or update payment method |74| Missing self-serve controls | provide portal, cancellation path, or invoice access |75| Product failure or trust break | refund, apologize, log product issue |7677### 3. Take the safest reversible action first7879Preferred order:80811. restore self-serve management822. fix duplicate or broken billing state833. refund only the affected charge or duplicate844. document the reason855. send a short customer follow-up8687If the fix requires product work, separate:8889- customer remediation now90- product bug / workflow gap for backlog9192### 4. Check operator-side product gaps9394If the customer pain comes from a missing operator surface, call it out explicitly. Common examples:9596- no billing portal97- no usage/rate-limit visibility98- no plan/seat explanation99- no cancellation flow100- no duplicate-subscription guard101102Treat those as ECC or website follow-up items, not just support incidents.103104### 5. Produce the operator handoff105106End with:107108- customer state summary109- action taken110- revenue impact111- follow-up text to send112- product or backlog issue to create113114## Output Format115116Use this structure:117118```text119CUSTOMER120- name / email121- relevant account identifiers122123BILLING STATE124- active subscriptions125- invoice or renewal state126- anomalies127128DECISION129- issue classification130- why this action is correct131132ACTION TAKEN133- refund / cancel / portal / no-op134135FOLLOW-UP136- short customer message137138PRODUCT GAP139- what should be fixed in the product or website140```141142## Examples of Good Recommendations143144- "The right fix is a billing portal, not a custom dashboard yet"145- "This looks like duplicate personal checkout, not a real team-seat purchase"146- "Refund one duplicate charge, keep the remaining active subscription, then convert the customer to org billing later if needed"