customer-billing-ops

Topics in the source

• Customer Billing Ops
• When to Use
• Preferred Tool Surface
• Guardrails
• Workflow
• 1. Identify the customer cleanly
• 2. Classify the issue
• 3. Take the safest reversible action first

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? 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 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 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 pl

This is an excerpt. Refer to the complete source and its current requirements.