We are closing a service. What must still work for existing customers?
Plan the end of an offer while keeping the right information, materials and contact routes available to customers whose work continues.
Article language: English

In this article
The service disappears from the menu on Friday. On Monday, an existing customer opens an old link to check how to prepare for the final stage of their project. It takes them to a homepage announcing new possibilities. The company has closed sales and, along the way, closed the customer's route to information. The menu is tidier. For the person with a deadline in their calendar, the change looks rather different.
Retiring a service involves several separate decisions. When will new enquiries stop? What happens to work already under way? Where will existing customers find help, documentation and a way to get in touch? Which traces of the old offer still lead people to the company? Removing a service card does not answer all of these questions.
Here we look at the operational and editorial side of the change. Decisions about contracts, customers' rights and the timing of obligations need a proper basis and an accountable person. The website should communicate confirmed decisions clearly, not make them on its own. First establish what will remain available; then choose how to announce the closure.
What is ending, for whom and when?
Imagine a fictional company retiring its seasonal display design service. It is no longer accepting new projects under the old scope, but some commissioned work is still in progress. Existing customers need materials, confirmations and a clear way to reach the team. New visitors, meanwhile, need to understand quickly that they can no longer order the service.
Consider these groups separately. Someone considering a purchase needs a different answer from a customer waiting for an agreed project stage. Someone returning a year later may be looking for an old instruction or information about an alternative. A single sentence saying "the service has ended" does not give all of them a useful next step.
The UK Service Manual's guidance on retiring a service starts with the user's continuing needs and information about their changed journey. This is a design reference, not a timetable of duties for a Polish company. In our example, it prompts the question of how a customer will complete a remaining task once new sales close.
For each group, write down one task they should still be able to complete. A new visitor needs to recognise that sales have stopped. A customer with work in progress needs to send materials. A person returning to the documentation needs to find the right version. These statements help a team assess the transition without assuming that a notice alone completes the work.
Keep a simple record of the states: new sales, work in progress, materials for existing customers and ongoing contact. Each state needs an owner and a confirmed date for a change, if a date forms part of the decision. Name the specific stage for each date: the last new enquiry, the end of material submissions or a change in the contact route. Customers should know which action a deadline applies to. If there are several dates, place them next to the relevant tasks rather than trying to fit the whole transition under one "we are closing" heading.
If another service is replacing the old one, explain the difference in scope. "We are replacing it" may suggest the new option meets the same needs on the same terms. Check that against actual customer situations. Sometimes it is more accurate to describe a new direction and state plainly what it no longer covers.
Connect the decision to how the company will maintain that capability (in Polish). A company may close the public offer while still meeting some needs another way. The boundaries must be clear, so an old form does not begin to promise an exception to everyone who finds the retained address.
The old address is still an entrance to the service
Gather the offer page, downloadable materials, messages, profiles and places from which people arrive. The aim is not to find every mention on the internet. Start with routes customers actually use: a saved offer, instructions in a message or a link in a confirmation. Decide what should happen at each one.
Do not automatically redirect everything to the homepage. Google's documentation on site moves cautions against sending many old URLs to one unrelated destination. The problem is just as plain to the visitor: the explanation of what the link concerned and why it no longer leads to the expected material has disappeared.
When moving a site without losing track of its addresses (in Polish), distinguish an actual equivalent from a notice that a service has ended. If a useful replacement page exists, point to it. If it does not, a retained notice at the old address can explain the change and give existing customers an appropriate route.
That page should name the service, its status and the next step. In our fictional example it might say: "We are no longer accepting new display projects in this scope. If your agreed project is still under way, please use your existing project contact." This is an editorial direction to adapt to the real process, not a ready-made promise of support for every company.
Review the buttons. "Order" should not lead to a form that the team no longer handles in the old way. At the same time, removing every action can cut existing customers off from help. Information for new visitors and contact about an ongoing case can be separated, if that reflects how support actually works.
Look at automated messages too. A form confirmation may still promise a proposal while the page announces the end of sales. Test a submission from the old entry point and read the text it actually produces. The person responsible for the change should include such messages in the same plan rather than expecting customers to choose the newer promise themselves.
Check materials downloaded outside the site. An old PDF can continue to circulate inside customers' organisations and still invite them to buy. You cannot change every downloaded copy, but you can look after the place its link leads to. A visitor should find the current service status there and enough context about the older document. If the company maintains a download centre, distinguish an old instruction a customer still needs from an active offer. The guide to download centres (in Polish) discusses organising downloadable materials. Show the document's status before download and make sure its retained address leads to the right context.
The remaining work needs an ordinary, clear route
For projects already started, identify the information still needed to finish them. This may include dates, how to deliver materials and who is handling the work. Do not assume customers remember it from the first conversation. If they used to return to public instructions, removing those instructions changes how they work.

The team needs to know how to answer questions about new sales and existing work. A clear approach to declining a B2B assignment (in Polish) helps maintain the agreed scope without adding promises. During retirement, it is particularly important to recognise whether the person is asking for a new service or for an existing case to continue.
Prepare several realistic questions and check the answers on the site, in the form and in the team's guidance. "Can you still take on a project?", "Where do I send the final materials?" and "What should I choose instead of the old scope?" should not all receive the same automated text. Consistency means the same service status, not the same paragraph copied into every situation.
If support will remain available for a period, explain its scope using confirmed decisions. Do not simply say "support is available" when it covers only a particular stage or group of customers. A returning visitor should be able to tell whether that route applies to their case before preparing a full request.
Decide how a case will be handed over if its usual contact is unavailable. Does the customer know where to return, and can the person covering find the context? As an offer winds down, the team may already be working on other projects. That makes a simple record of the remaining work more useful than keeping it solely in the account manager's memory.
When archiving company knowledge (in Polish), keep the materials needed to explain past work. Separate the archive from the current offer. An old scope may be useful to the team as a historical record, but it should not accidentally reappear among active services through an import or search.
Aeneia Design
We can organise the page for a retiring offer and the route available to its existing customers. We will separate the end of new sales from the materials, contact options and steps needed to complete an ongoing case.
Design a clear transition after a service ends
With Aeneia Design, the conversation can begin with the old offer page, the confirmed scope of the change and a few customer situations. That grounds the communication design in actual company decisions instead of announcing a closure the organisation is not yet ready to support.
See the change through the eyes of someone who did not know the plan
Test three entry points: the old link, the new services page and a message from an ongoing project. Ask a reviewer to say what is available and what they can do next. Do not show them the retirement schedule first. Customers were not in the meeting where everything seemed obvious either.
Add a delay to one stage of the exercise. The notice has changed, but the customer material has not yet reached its new location. Decide what the visitor will see during that gap and who confirms the next step is ready. It is better to plan the order of dependent changes than to open a route whose final stretch will only be built tomorrow.
Across language versions, check the actual service status. One language may still invite new enquiries even though the form now leads to a closure notice. The team should identify which version needs correcting and who owns its review. Hiding the language switch is not enough if the old address still works and is used in messages.
Check internal search and related materials. An old offer can still look active in a shortened card even when the main page carries the correct notice. The change should cover the promise in places a visitor actually sees before clicking. Correcting the heading on the destination page alone does not finish the work.
If incorrect information about the closure or replacement was published earlier, follow the company's correction process. The guide to correcting published information (in Polish) explains how to prepare a correction. Explain what was corrected and which scope the current notice covers. Do not leave two versions circulating as though both were still authoritative.
Turn off internal mechanisms according to a separate automation closure plan. The guide to automation closure (in Polish) discusses how to prepare that plan. New sales may stop before a form needed for ongoing work is closed. The order should follow dependencies, not the convenience of one master switch.
After the change goes live, collect questions that still reach the old service. Distinguish an unnoticed notice, an unclear scope and a missing route. Each cause calls for a different correction. The number of such contacts alone does not tell you whether to add information, change a link or agree on a missing way to provide support.
Keep a transition record covering several customer cases. For each one, record the old entry point, the information needed, the current next step and the test result. A month later, the team can revisit those same cases instead of checking only that the service is still absent from the menu. If a remaining route stops working, the record helps identify the specific action that has been lost.
Finally, assign an owner for the remaining public traces and a date to review them again. Retirement does not necessarily end when the menu changes. It ends when the agreed route for existing customers works as the company decided it should. The homepage can still talk about new possibilities; it simply need not replace instructions for someone who came to finish an older piece of work.








