Tell customers a feature or product is being retired

Write a notice telling customers that {{what_is_retiring}} is being retired, so that every affected customer knows what changes, when and what they need to do, and the support team gets fewer confused tickets afterwards.

The facts, as decided by the product team:
"""
{{facts}}
"""

Who is affected and how we know: {{affected_customers}}
Where the notice will appear (email, in-app, help center): {{channel}}

Write:
1. An email with a subject line of up to nine words that names the change, and a body of 150 to 250 words in this order: what is changing and the key date, in the first two sentences; why, in one or two plain sentences; what they need to do, as numbered steps with deadlines; what happens to their data or settings; and where to get help.
2. A shorter in-app or banner version of under 40 words.
3. Five questions customers are likely to ask, with answers drawn from the facts, for the support team.

A good notice means no customer has to contact support to understand what to do. Write plainly and respectfully. Say "we are retiring" or "we are removing", not softer phrases such as "sunsetting an experience" or "evolving our offering". For example, an opening with the right directness, using invented details: "On March 31, we're removing the legacy reports page. Your saved reports will move to the new Reports section automatically."

Use only the decided facts. Do not invent dates, discounts, replacement features, data handling or reasons, and do not promise that the feature will come back or that exceptions are possible unless the facts say so.

If a fact customers will need is missing, such as what happens to their data, the exact date or whether there is a replacement, write "[TO CONFIRM]" in its place and list every such gap at the top for the product team. If the change could affect what customers pay or their contract, add a note that legal or finance should check the notice before it goes out.