Pricing and billing complaints

When to use it

Reach for this when someone says any of these — they are the phrases the skill itself triggers on:

• “customers complaining about price”
• “billing complaint analysis”
• “why do customers dispute their invoice”
• “is our pricing a problem”

How it works

The method, in the order the skill runs it. The full procedure — tables, worked examples and the edge cases — is in the skill itself.

1. Separate the four before counting anything

   Getting the mix wrong sends the finding to the wrong place. A pricing review triggered by what is actually a proration bug wastes a quarter; a billing investigation triggered by a genuine value objection finds nothing and closes.

2. Billing defects need their own path

   Once separated, defects stop being an analysis and become an incident.

3. Surprise is a design problem, and it is measurable

   For each surprise category, find the moment the customer could have known: Was the charge communicated in advance, in a channel they use?, Was the trial end date visible in the product?.

4. Reading the value objection honestly

   This is the only one of the four that is actually about your pricing, and support is a biased place to measure it.

5. Affordability is a duty, not a discount decision

   Where a customer says they cannot afford it — as distinct from will not pay it: Look for vulnerability signals alongside it, and flag them.

Related skills

• Onboarding blockersFind what blocks new customers, before retention shows it
• Refunds and goodwillSet refund limits agents can apply without escalating
• Handing leads to salesGet a revenue signal to the account owner without selling
• Executive escalationsRun an executive escalation through to actually fixed
• Cost of poor qualityPut a number on what poor support costs you
• Support-led growthGrow accounts by removing blockers, not by selling