Shane Ian Murphy on Limitless Mobile and the Last Useful Service Message

By Shane Ian Murphy, former CBDO and cofounder of Limitless Mobile.

When I write about service design, I think the final communication deserves as much attention as the first invitation to join. My recollections of Limitless Mobile concern the relationship between a simple customer proposition and the organisations needed to support it. That perspective shapes my opinion here: retiring a service is a design problem, and the customer needs a usable route through it.

An announcement can be factually correct and still be practically poor. “This service is being discontinued” tells somebody that a decision has been made. It does not tell them whether they need to act today, whether an alternative fits their situation, or whether a task they started can still be completed. I would begin with those questions before choosing the headline or approving the tone.

Consider a hypothetical communications service that is being withdrawn. Some customers might use it every day, while others might depend on it only occasionally. A message based solely on recent activity could miss the second group. I would want the communication plan to consider dependency as well as frequency. An infrequent user can still face a significant interruption if the notice arrives too late to make another arrangement.

The first message should separate the decision from the required action. I would explain what is ending, what remains available during the transition, and what the customer should do next. If different customer groups face different steps, the notice should make that distinction visible. Asking everybody to interpret one broad statement shifts too much of the work onto the reader.

Dates matter, but a sequence matters too. Customers may need to choose an alternative before they can make a transfer, and finish that transfer before they can close an old arrangement. A calendar full of deadlines does not explain that order. I would prefer a short path that shows what can happen now, what depends on another step, and where help is available if progress stops.

I also think the replacement deserves an honest description. “Move to our new solution” can sound effortless even when the experience differs. In the hypothetical example, a replacement might lack a feature that some customers use. The communication should explain the relevant difference early enough to inform a choice. A migration is not successful merely because a person has been moved somewhere else.

The support team needs more than a copy of the public announcement. I would want them to know which questions have settled answers, which circumstances need individual review, and who can resolve an exception. Otherwise, customers discover that the announcement sounds definite while the organisation remains unsure how to handle ordinary variations. Preparation should include the awkward cases, not only the most convenient route.

Repeated messages should reflect progress. A person who has completed the necessary steps does not need another urgent warning that assumes nothing has happened. Someone who has begun but become stuck needs a different prompt from someone who has never opened the notice. I favour communication that follows the customer's position, with appropriate limits on how much information is collected to do that.

Accessibility belongs in the plan from the beginning. A prominent banner is useful only to somebody who can access the service and understand the wording. I would check whether the essential instructions are available through the channels customers already use, whether the language is plain, and whether a person can obtain help without passing through the feature that is being removed.

The final message should close the practical loop. It should explain what has finished and where a customer can still raise a relevant question. I would also review recurring points of confusion after the transition, because they reveal assumptions the organisation failed to explain. The end of one service can teach a business how to introduce the next more responsibly. For me, a thoughtful retirement is part of delivering the original promise: helping people manage a service they have chosen to rely on.