Draft a Feature Deprecation Notice for Your Customers

Get a clear, empathetic customer notice that explains a feature sunset, provides alternative workflows, and outlines migration steps to minimize user friction.

Prompt

Prompt
Act as a Customer Success Manager. Draft an email notice announcing the deprecation of a software feature. First, ask me these 3 questions: 1. What is the name of the feature being removed? 2. What is the final date for access? 3. What is the recommended alternative workflow or tool? Once I answer, write the notice following these rules: Use a supportive, direct tone. Do not apologize excessively. Provide a clear timeline with a sunset date. List exactly two alternative workflows. Include a step-by-step migration guide. Output format: Subject line. Body paragraphs. Sunset Timeline section. Alternative Workflows section. Migration Steps section. This is not legal advice and you should consult your legal team regarding contract obligations.

Example output

Example for: retiring the legacy 'Export to PDF' report tool in a project management platform.

Subject: Update regarding the Export to PDF tool

We are reaching out to let you know that we are retiring the legacy Export to PDF feature. We have shifted our focus toward more robust reporting tools that provide real-time data visualization and interactive sharing capabilities.

Sunset Timeline

  • August 15: Announcement and notice period begins.
  • September 1: Feature becomes read-only.
  • September 30: Feature access is fully removed.

Alternative Workflows

  1. Use the new Live Dashboard Link to share interactive views with stakeholders who need real-time updates.
  2. Use the CSV Export tool for raw data analysis, which can be formatted into custom PDF reports using external tools like Excel or Google Sheets.

Migration Steps

  1. Log in to your project dashboard.
  2. Click the Share button in the top right corner.
  3. Generate a public view link for your recurring reports.
  4. Save your existing PDF exports to your local drive before September 30, as these files will not be migrated automatically.

This is not legal advice and you should consult your legal team regarding contract obligations.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Forces a clear timeline to prevent user confusion.
  • Limits alternatives to exactly two to avoid overwhelming the reader.
  • Uses a professional tone that avoids excessive apologies.

Use this prompt to communicate product changes clearly without causing unnecessary alarm. Ideal for SaaS companies retiring legacy tools. Works well in ChatGPT, Claude, and Gemini.

Common edits

  • Adjust the tone to be more or less formal based on your brand voice.
  • Add a link to a support article if you have complex migration requirements.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Customer Support
Customer Support

Write an honest shipping delay update

Turn frustrating parcel delays into clear, reassuring customer updates that give specific dates and tracking details without corporate jargon.