An item your team relies on is being discontinued and you need precise dates and supported options.
The useful bits
- Exact affected item or version
- Official notice reference
- The reply should identify exact affected versions, confirmed dates and documented transition options.
Before you write
Use this example when an item your team relies on is being discontinued and you need precise dates and supported options. Gather the details below so the recipient can act without asking you to reconstruct the situation.
- Exact affected item or version
- Official notice reference
- Technical and purchasing review owners
An email you can adapt
The subject “Clarification of [item] discontinuation notice” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.
Subject: Clarification of [item] discontinuation notice Hi [name], Please clarify how notice [reference] affects [exact item or version]. We need the confirmed dates for [relevant stages] and the official options available to existing users. Please distinguish a suggested replacement from one verified as compatible with our use. [Owners] will assess the operational and purchasing implications before deciding on a transition. We are not authorizing a replacement purchase through this information request. Best, [sender]
Check the boundary
Avoid converting a supplier’s suggested successor into a promise that migration is automatic or risk-free.
What a useful reply should settle
The reply should identify exact affected versions, confirmed dates and documented transition options.
Plan a proportionate compatibility review and obtain the required approval before making a consequential change.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction