Subscription cancellation
Confirms identity, captures cancellation reason in a structured form, and produces a cancellation request with the effective date your client's system needs to process.
Use when you want a calm, predictable cancellation path that doesn't try to save the customer. The voice in this workflow is deliberately neutral.
It does not run save-offers, does not negotiate, and does not actually cancel. Cancellation is executed by your client's billing system using the structured output.
- intake
- collect
- confirm
- handoff
Provisioning the MCP URL for Subscription cancellation is part of Pro.
Free accounts can read the YAML, run the Live Preview, and provision one starter URL. Pro provisions URLs for the whole catalog.
Open YAML. Read it before you subscribe.
The harness that enforces this YAML is closed and hosted. The YAML is what you can audit, fork, and reason about.
1# subscription-cancellation.yaml2name: subscription-cancellation3version: 1.0.04category: billing5description: Calm cancellation intake. No retention pressure.6 7inputs:8 - name: customer_id9 type: string10 11harness:12 - step: intake13 - step: confirm14 require: identity15 - step: collect16 field: cancellation_reason17 optional: false18 - step: confirm19 show: effective_date20 - step: handoff21 emit:22 packet: cancellation_request23 24policy:25 retention_offers: false26 pressure: false27 Need subscription cancellationtuned to one client’s voice, escalation logic, and required fields? That’s a $99 personalization.
One-shot fee. Turnaround stated up front. The result is yours, with the deterministic harness already wired.
- Refund request intakeCollects structured refund-request information and produces a handoff packet for human review.
- Invoice clarificationWalks the customer through a specific invoice line by line and answers questions grounded in the line items provided.
- Payment failure recoveryWalks customer through updating a failed payment method.