refund-and-exception-brief

$npx mdskill add Significant-Gravitas/skills-catalog/refund-and-exception-brief

Use this whenever a customer asks for money back, a credit, or a rule to be bent.

SKILL.md

.github/skills/refund-and-exception-briefView on GitHub ↗
---
name: "refund-and-exception-brief"
description: "Prepare a refund or policy-exception request for the named approver, with facts, policy text, and options."
triggers: ["refund request", "policy exception", "goodwill credit", "billing dispute", "approve refund"]
version: "1"
---

# Refund and exception brief

Use this whenever a customer asks for money back, a credit, or a rule to be
bent.

## State the facts

Give the customer, plan, billing dates, amounts charged, what they asked for
in their own words, and the ticket id. Add what the account record shows:
usage, outages or bugs that touched them, and past credits. Mark any fact you
could not verify.

## Compare with policy

Quote the refund or exception policy that applies, with its source and date.
Say plainly whether the request falls inside or outside it and why. If no
written policy covers the case, say so rather than guessing one.

## Options for the approver

Lay out two or three options, for example:

- follow the policy as written;
- a partial refund or credit, with the amount;
- the full request.

For each give the cost, the precedent it sets, and any chargeback or legal
deadline. Name the approver and the date a decision is needed.

Never promise a refund, credit, or exception to the customer before the
approver decides. Do not issue money or change billing yourself; draft only.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.