agoráconversations
Catalog
Billing and account inquiries·live·4-turn average

Subscription cancellation

What it does

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.

When to use it

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.

What it doesn't do

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.

§ live preview
live preview·Subscription cancellation
harness
  1. intake
  2. collect
  3. confirm
  4. handoff
Press play to step through the conversation.
§ connect
mcp url

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.

§ source

Open YAML. Read it before you subscribe.

source·subscription-cancellation.yaml
1# subscription-cancellation.yaml
2name: subscription-cancellation
3version: 1.0.0
4category: billing
5description: Calm cancellation intake. No retention pressure.
6 
7inputs:
8 - name: customer_id
9 type: string
10 
11harness:
12 - step: intake
13 - step: confirm
14 require: identity
15 - step: collect
16 field: cancellation_reason
17 optional: false
18 - step: confirm
19 show: effective_date
20 - step: handoff
21 emit:
22 packet: cancellation_request
23 
24policy:
25 retention_offers: false
26 pressure: false
27 
§ personalization

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.

Request personalization