ipIterPrompt

Cancellation Request Reply — Consumer Subscription App

Process a cancellation gracefully while leaving the door open. Purpose-built for consumer subscription app contexts.

iterpromptUpdated 2026-06-12933 copies

A structured customer support prompt for ticket responses: process a cancellation gracefully while leaving the door open, tailored to a consumer subscription app with trials, renewals, and cancellations. It walks the model through a proven process with an explicit quality bar, and delivers a reply that confirms the cancellation cleanly, states what happens to their data/billing, and offers one genuine alternative without guilt-tripping.

The prompt

Variables to fill in: {{customer_message}}{{situation_facts}}{{brand_voice}}

You are a support lead who writes replies that resolve issues on the first touch and leave customers feeling respected. I need your help in the context of a consumer subscription app with trials, renewals, and cancellations.

TASK: Process a cancellation gracefully while leaving the door open.

DELIVERABLE: Produce a reply that confirms the cancellation cleanly, states what happens to their data/billing, and offers one genuine alternative without guilt-tripping.

PROCESS:
1. Review the inputs below. If anything critical is missing or ambiguous, ask me up to three clarifying questions before producing the deliverable.
2. Read the customer's message from the inputs twice: identify the practical problem, the emotional state, and anything they asked that's easy to miss.
3. Resolve or advance every question in one reply — no partial answers that force another round trip.
4. Match the tone to the situation and the brand voice; be human first, procedural second.
5. Produce the deliverable in a clean, skimmable format I can use directly.

QUALITY BAR:
- Acknowledges the customer's actual words, never a generic 'sorry for the inconvenience'.
- Gives the direct answer early, then the explanation — customers skim.
- States exactly what happens next and when, with no vague promises.

INPUTS:
- The customer's message, pasted verbatim: {{customer_message}}
- What you know: account status, relevant policy, what's possible: {{situation_facts}}
- Tone guidance: e.g. warm and casual, or professional and precise: {{brand_voice}}

Run this prompt on a real model without leaving the page. Every run is saved to your history for this prompt.

Fill in the variables

How to use

  1. 1Fill in the {{customer_message}}, {{situation_facts}}, {{brand_voice}} variables with your real details — specifics in, specifics out.
  2. 2Paste the prompt into ChatGPT, Claude, Gemini, or any capable model.
  3. 3Answer the clarifying questions it asks; that step is what makes the output fit your situation.
  4. 4Iterate on the deliverable: ask for alternatives, tighter versions, or a different angle on any section.

Pro tips

  • If the output feels generic, add more concrete detail to the inputs — names, numbers, and constraints sharpen everything.
  • Works well in a thread: keep the conversation going to refine a reply that confirms the cancellation cleanly, states what happens to their data/billing, and offers one genuine alternative without guilt-tripping.

Related

Repeat-Issue Apology — Fintech & Banking

Apologize to a customer hit by the same problem more than once. Purpose-built for fintech & banking contexts.

4,319 copiesOpen ↗

Negative Public Review Response — B2B SaaS

Respond publicly to a harsh review that other customers will read. Purpose-built for b2b saas contexts.

4,316 copiesOpen ↗

Repeat-Issue Apology — Enterprise Accounts

Apologize to a customer hit by the same problem more than once. Purpose-built for enterprise accounts contexts.

2,916 copiesOpen ↗

Negative Public Review Response — Fintech & Banking

Respond publicly to a harsh review that other customers will read. Purpose-built for fintech & banking contexts.

4,165 copiesOpen ↗