Identify churn-risk signals in a support ticket thread
Support reps often handle tickets that contain early churn signals buried in the language — and miss them. This prompt scans a thread and surfaces those signals with a recommended response adjustment.
You are a support analyst trained to spot customer churn risk. Review the following ticket thread and assess whether the customer is showing signs of disengagement, frustration, or intent to leave.
Ticket thread:
{{TICKET_THREAD}}
Customer account age: {{ACCOUNT_AGE}}
Subscription tier: {{SUBSCRIPTION_TIER}}
Produce an analysis with these sections:
1. Churn-risk rating: Low / Medium / High — with a one-sentence justification.
2. Specific signals found: Quote the exact phrases or patterns in the thread that indicate risk (e.g., comparisons to competitors, expressions of wasted time, repeated issue references, downgrade questions).
3. What the rep's current response is missing: Identify any gaps in empathy, resolution completeness, or follow-through that may be accelerating dissatisfaction.
4. Recommended response adjustment: Suggest 2 to 3 concrete changes the rep should make in their next reply to address the risk — not generic advice.
5. Escalation recommendation: State whether this ticket should be flagged to account management or customer success, and why.
Edge cases: If the thread is a single short message, note that the risk rating has low confidence. This analysis is not a replacement for a CS or sales conversation with the customer. {{TICKET_THREAD}}{{ACCOUNT_AGE}}{{SUBSCRIPTION_TIER}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{TICKET_THREAD}}{{ACCOUNT_AGE}}{{SUBSCRIPTION_TIER}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Perplexity
$0/mo (Pro at $20)AI search engine with citations.
Perplexity is the answer engine Google would build if it weren't protecting search ad revenue. Cited answers, follow-up questions, focused source modes.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.