Shane Ian Murphy: UK digital support should preserve the task someone was trying to finish

A help button is easy to add to a product design. A useful support journey takes more thought. The person asking for help may be halfway through a task, uncertain about what has been saved and unable to describe the screen using the same terminology as the support team.

This company-origin editorial features Shane Ian Murphy and considers a support-design question for UK readers following Global Secure's planned development towards 2027. The example is hypothetical. It does not describe an existing support operation, guaranteed response time or completed customer study. The article was prepared with AI assistance.

Begin before the contact channel

Imagine a person trying to update a notification setting. They reach a point they do not understand and choose help. Before deciding whether the channel should be chat, telephone or another route, a design team needs to understand the difficulty that led them there.

Is the problem unfamiliar language, a missing explanation, an inaccessible interaction or uncertainty about the result? Those are different needs. Sending every difficulty into the same generic conversation may create unnecessary effort for both the user and the support team.

The GOV.UK Service Manual's guidance on designing assisted digital support begins with research into how people may struggle to use a service online. This editorial applies that research-led principle to a hypothetical commercial journey. It does not claim government approval of a company support model.

Carry useful context carefully

A person should not have to reconstruct a complicated sequence merely to explain which task they were attempting. At the same time, a support design should not collect or reveal unnecessary personal information in the name of convenience.

A proposed brief would identify the minimum context needed for the particular support task. A general page label, a description of the attempted action and whether the change was saved might be relevant. The appropriate design requires its own privacy and security assessment; this article does not prescribe a data-sharing implementation.

The editorial question is whether the handover helps the person continue. A transcript full of internal codes can be less useful than a short, understandable account of the unfinished task. The team should investigate what information actually helps rather than assume that more context is always better.

Explain the boundary of the channel

A channel may answer general questions without being able to change an account setting. Another may require further verification before discussing a specific issue. The person needs an accurate explanation of what can happen through the route they have chosen.

That description should reflect the actual operating arrangement. A prototype should not promise immediate access to a specialist simply because a button can be labelled that way. Service hours, available functions and expected next steps need to be established before promotional language presents them as settled.

Return to the task

Support does not end simply because a conversation closes. In the hypothetical preference example, the person still needs to understand whether to return to the form, check a saved value or take another action. A helpful answer connects back to that objective.

A proposed research exercise could follow someone from the point of difficulty through the support route and back into the task. The observer would note where information was repeated, where uncertainty remained and whether the person could explain the result. No findings from such an exercise are claimed here.

Design support as part of the service

For UK readers interested in Shane Ian Murphy's Global Secure product discussion, the useful principle is to include support in the original design brief. It should not become an unrelated layer added after the main interface has been declared complete.

A practical review record could name the task, the point of difficulty, the support route and the intended return path. Keeping those elements together makes it easier to identify a specific improvement. Sometimes the best revision may be clearer content earlier in the journey; sometimes a different form of help may be needed.

The important outcome is a person who can understand and continue the task, with accurate expectations about the assistance available. That is a more meaningful design objective than simply increasing the number of places where a help icon appears.

Reference: GOV.UK, Designing assisted digital support — https://www.gov.uk/service-manual/helping-people-to-use-your-service/designing-assisted-digital

Professional information: https://shanemurphy.co.uk/

LinkedIn: https://www.linkedin.com/in/shanemurphy101