Blog Posts

Software End of Support: What Can Your Customer Notice Promise?

Software End of Support: What Can Your Customer Notice Promise?
Çağla Güvelioğlu
Çağla Güvelioğlu
Contents

Start with the customer's next decision

A software support notice should explain what changes, who is affected and what the customer needs to do next. A product name and an end date rarely answer those questions. The person reading the notice may manage a budget, use the software or hold the account password. Each needs a different part of the same plan.

For a communications team, the first decision is which promises the product team can support with evidence. Can customers still sign in? Will security fixes stop? Can they move their records elsewhere before access closes?

Keep those questions separate while preparing the notice. End of support is a label; its practical meaning depends on the product, service and terms involved. Do not let the label replace the explanation. A reassuring headline is useful only when the instructions beneath it hold up.

The steps below are a suggested communication process for software businesses. They do not set a standard notice period or replace product terms. Use the actual service plan and the checks made by the people responsible for delivering it.

An international brand communication plan should establish who owns messages across markets. For a support notice, appoint one owner for shared facts and local reviewers for language and contact details. Keep the same product scope and deadlines in each local version.

Define exactly what will end

Describe each service that will stop and each service that will remain available, using the product's actual scope. Technical support means help with using or fixing the product. Security patches are software updates that address security flaws. Neither phrase tells a customer, by itself, whether their installed software will keep running.

Cloud shutdown is another event: it concerns a service that depends on the provider's systems. A local application might open while an online feature no longer works. A customer could also lose account access before completing a move. Establish the facts for this product rather than treating these possibilities as its confirmed outcome.

Microsoft's Modern Lifecycle Policy shows why the conditions matter. It links support to servicing and system requirements, licensing and Microsoft continuing to offer support. Those conditions belong to that policy. Check the applicable product terms before using its promises in a customer notice.

Ask the product owner to review a short list of changes. Use exact product names, versions and plans, with a way for customers to identify theirs. Include any known differences between regions or account types. A broad statement about “all users” needs equally broad evidence.

  • Which versions or service plans are affected, and which remain supported?
  • When will help from the support team end, and what help remains?
  • Which updates or security fixes will stop?
  • Will sign-in, online features or the whole hosted service close?
  • What happens to stored records and the tools used to export them?

Write separate answers even when several changes share one date. This makes the notice easier to check and allows a precise correction later. If a team has not confirmed an answer, record that gap before approving the claim. Avoid turning “still being assessed” into “no impact”.

Put customer actions on the timeline

Build the timeline around the actions customers must complete, with a clear date and time zone for each deadline. The last day of support may differ from the last day to export records. A migration offer may also close earlier. Migration means moving work, settings or records to another system.

Atlassian's Server end-of-support page records a February 2024 support and bug-fix cutoff for products including Jira Software Server and Confluence Server. It separately discusses Fisheye and Crucible. These are distinct product schedules. Use the applicable entry rather than treating the page title as one rule for all products.

Start with the final outcome and work backwards. If access will close, identify what must happen while an account is still active. Check who can perform each task and how that person gets permission. A notice sent to the billing contact may never reach the administrator who can export data.

Give the customer a short sequence: check the affected account, choose an option, complete the required steps and confirm the result. Make each step lead to a current guide or contact route. Explain whether the guide covers every supported version. A single generic link can hide a critical difference.

Check the cost of each proposed option before calling it free or included. A new licence, setup work or outside help may need a separate decision. State what the provider covers and what the customer must arrange. Sales copy should not promise a service the support team cannot book.

Across countries, show the same event in a form each audience can use. Check date formats, local contact hours and the wording of deadlines. FL's discussion of planning communications for international markets provides a wider view of local audience needs. Here, that means keeping the underlying deadline consistent while making the required action clear.

Test the route out before you recommend it

Check the export or move process with the relevant product team before telling customers it will preserve their work. An export is a copy taken out of the service. A downloaded file alone does not show that another system can use it. Define the checks that support the promise you intend to make.

Use a suitable test account and record the version, plan and steps checked. Ask whether the export includes files, attachments, settings and the records customers expect. Identify anything left behind. Keep the result separate from assumptions about every other account.

A support specialist checks a software transition plan beside two laptops and an external storage drive.
A clear transition plan connects the customer notice with the work needed to move and check records.

Then check the destination. Can the intended user open the files and understand their structure? Are dates, file names and links still useful? If the move requires manual work, describe that work before the customer commits.

  • Name the format and the content included in the export.
  • State which account role can start or download it.
  • Explain any known limits and where customers can get help.
  • Distinguish downloading records from checking a successful move.
  • Give the confirmed access and deletion dates separately, where they apply.

A backup, meaning a separate copy kept for recovery, is another part of the plan. Do not imply that an export button proves a recoverable backup exists. Ask the technical owner what has been checked and what the customer must verify. Use the tested scope in the notice.

If an essential step remains unclear, change the instructions before sending them. Customers should know where the route ends and who handles a problem at that point. Avoid promising a smooth or loss-free move simply because a replacement product exists.

Check the help pages alongside the tested steps. The link between public communication and consistent online information applies to those instructions too. A clear notice can be undermined by an older guide that still describes an unavailable feature.

Give every promise an owner and a limit

Attach each material promise to a named internal owner, a supporting record and any limit that affects the customer. The owner should be able to confirm the statement and organise a correction. This is an internal approval role. The public notice still needs a usable team contact, not a list of staff names.

Review phrases such as “nothing changes”, “your data is safe” and “we will move everything”. Each can cover far more than the team has checked. Replace them with the specific service, period or tested result. Clear limits help the customer plan without guessing.

FL's public relations management process describes the role of shared preparation and approvals. Apply that principle by agreeing one factual brief across product, support, sales and communications. Record open questions alongside approved answers. Do not quietly remove a difficult question from the brief.

Separate a confirmed promise from a proposed option. For example, a team may be checking whether a paid extension is feasible. Until it is approved, the notice should not present that extension as available. If the option changes, update everyone working from the original brief.

Choose a contact route that matches the question. Billing teams may handle renewal terms, while support handles export steps. Explain how an unresolved case moves between them. Avoid sending customers around several inboxes with no one responsible for the next answer.

Maintain one current notice after the announcement

Keep one dated notice as the current public record and link other messages back to it. Email, account alerts and support replies should agree on scope, dates and actions. They can vary in length for the audience. They should not create competing versions of the plan.

Prepare support answers before the announcement goes out. Give account teams the same links and explain how to report a missing answer. Media enquiries may ask why the change is happening and how affected customers are being helped. FL's media relations preparation and source checks are relevant to that part of the work.

Make the notice easy to find through the help centre and product pages customers already use. Update pages that still promote an expired offer. Keep a clear route from those pages to the current plan.

Track practical questions after sending, such as failed exports or uncertainty about affected versions. Use them to improve the guide and route individual cases to the right team. Keep a visible change note when a date or instruction changes. The announcement is complete only when customers can act on the information it contains.

Frequently Asked Questions

A useful end-of-support notice explains service changes, deadlines and the actions needed to protect access to work.

Does end of support mean the software stops working?

The label alone does not answer that. Check whether the change concerns technical help, updates, sign-in or the service itself, and explain each affected function.

Can one deadline cover every customer action?

Only if the underlying dates really match. Confirm support, migration, export, account access and deletion dates separately before presenting a single deadline.

Is a successful download enough to confirm a migration?

A download confirms only one step. Check what the file contains and whether the intended destination can use it before describing the move as complete.

What should the notice say when an option is still being assessed?

State that the option is unconfirmed and provide the approved next update or contact route. Keep current customer deadlines clear while the team reaches a decision.