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

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

Phased Timeline Table
Phase / Days to SunsetAudience SegmentPrimary ChannelsCore MessageRequired Customer Action
Phase 1: 90 Days OutAll Account AdminsEmail, Help Center docs, Admin dashboardEarly notice of feature retirement with rationale and replacement optionsReview current account usage data in settings
Phase 2: 60 Days OutActive Feature UsersIn-app notification banner, Dedicated webinarDetailed walkthrough of the successor tool and migration pathsRegister for live training or view video guide
Phase 3: 30 Days OutHigh-Volume Users & Inactive MigrationsDirect CS email, Urgent in-app modalAction required: legacy feature will enter read-only mode in 30 daysComplete data export or switch to new workflow
Phase 4: Day of SunsetAll UsersSystem status page, In-app redirectFeature officially deprecated; redirecting to the replacement workflowUse new interface; contact support for migration assistance
Escalation Protocol
  • Flag accounts generating over $50k ARR that have zero migration activity at 45 days out for immediate executive sponsor outreach.
  • Offer dedicated 30-minute technical office hours hosted by product engineering for accounts reporting custom API dependencies.
  • Grant a maximum 14-day read-only extension only upon formal request from customer success leadership.
Sunset Day Checklist
  1. Confirm database backup and archive legacy feature tables.
  2. Flip feature flag to disabled and enable 301 redirects to replacement module.
  3. Publish final status update on the public status page and knowledge base.
  4. Monitor customer support queue tag 'deprecation-legacy' for the first 48 hours.
Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Product Management
Product Management

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.

Product Management

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.