Schedule phased customer communications for feature sunsetting
Create a structured, multi-channel communication timeline to retire a software feature without alarming customers or breaking workflows.
You getPhased Timeline Table, escalation Protocol and sunset Day Checklist
Prompt
Act as a principal product manager planning the deprecation of a software feature.
Create a complete, phased communication schedule to deprecate an existing feature responsibly.
- Cover four distinct milestone phases: Initial Notice (90 days out), Reminder (60 days out), Action Required (30 days out), and Final Cut-Off (day of retirement).
- Detail communication channels for each milestone (in-app banner, email, customer success outreach, documentation updates).
- Provide key messaging objectives and explicit calls-to-action for each phase.
- Include specific migration guidance checkpoints for technical administrators.
Output format:
- Phased Timeline Table (columns: Phase / Days to Sunset, Audience Segment, Primary Channels, Core Message, Required Customer Action)
- Escalation Protocol (3 bullet points for managing impacted enterprise accounts)
- Sunset Day Checklist (4 operational verification steps)Example output
Run this prompt directly in ChatGPT, Claude, or Gemini without any edits to establish your deprecation framework. Afterward, ask the model to draft the exact email copy for the 30-day reminder phase.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Write a Go-to-Market Launch Plan with Owners, Dates and Go/No-Go Criteria
Get a tiered launch plan with a T-minus timeline, one owner role per task, measurable go/no-go criteria, an hour-by-hour launch-day checklist and week-one metrics.
Turn Engineering Changelogs into Customer Release Notes Users Read
Paste a changelog or ticket list and get customer-ready release notes grouped into New, Improved and Fixed, with internal-only changes removed and listed.
Define beta cohorts and launch exit metrics
Build a structured cohort plan and clear release criteria for your upcoming beta launch. Use this to prevent feature creep and ambiguous testing timelines.
Design a customer grandfathering plan for pricing changes
Structure a fair, phased grandfathering framework that updates customer pricing without triggering mass cancellations.
Draft a customer advisory board charter
Create a clear operational charter for a customer advisory board. Use it to align senior executives, define member terms, and prevent sessions from becoming feature wishlists.
Analyze customer feedback using Jobs to Be Done
Extract functional, emotional, and social customer drivers from raw user feedback. Use this to separate true user motivations from reactionary feature requests.
- Decline a stakeholder feature request diplomatically
- Reframe a feature request into a core user problem
- Create a Feature Deprecation and Sunset Migration Plan
- Define Granular Role-Based Access Control for Multi-Tenant Features
- Draft Multi-Tier SaaS Product Packaging and Feature Matrix
- Transform Customer Interview Transcripts into Ranked Pain-Point Matrix