Blog / Shopify & e-commerce /

Organising help content around customer tasks

Someone needs to return an order, so they search your help centre and find three articles. One explains the returns policy. One explains how to start a return. A product page has its own version of both.

Which one applies? Help centres grow by accretion, and customers pay for it. Organise help around customer tasks and the answers get easier to find, with fewer repeated explanations.

Start from what customers are trying to do

List the tasks people need to complete: choose a product, set it up, change an order, resolve an issue, arrange a return or understand a charge. Use support themes and customer language as clues, but confirm them with the people who handle the work. An internal department structure may not match the order a customer needs help in.

Group content by task and decision. A customer who wants to return an item may need to check eligibility, start the request and prepare the package. Those steps belong together even if separate teams own parts of the process.

Inventory existing answers

Find current help pages, product instructions, saved support replies and relevant policy documents. Record who owns each item, when it was last checked and where it appears. Look for duplicate explanations and contradictory steps. I don’t merge content until I know which source is authoritative.

Assign an action to each item: keep, update, combine, redirect or retire. If an article covers multiple tasks, decide whether to split it or improve its navigation. The choice should make the customer’s path clearer, not simply reduce the page count.

Design a clear path

Create a simple hierarchy that reflects common tasks and lets people reach a specific answer quickly. Use category names customers recognise. Add links between related steps where they help someone continue, such as from eligibility to the return request form. I dislike overview pages that send readers in circles by repeating the same links.

A page should say what it covers and when a different route applies. If a process depends on product type, location or order status, make the condition visible and provide the correct next step. Don’t assume a customer can infer their category from internal terminology.

Give each answer an owner

Every help page needs someone who can verify its facts and approve changes. Record review triggers, such as product releases, policy changes or support channel updates. If no team owns a page, it will likely become stale. A named owner is more useful than a general instruction to “review regularly”.

Separate public guidance from internal agent notes. Support teams may need escalation rules, exceptions or diagnostic details that customers shouldn’t see. Both versions should share a source of truth for policy facts, but each should be designed for its audience.

Make the content easy to use

Use descriptive headings, short steps and links with clear labels. Put warnings before the action they affect. Check accessibility, mobile layouts and search within the help centre. If a form or tool is part of the task, test that it works and explain what information the customer will need.

Search can land people on a single article before they ever see a category page. Make each page make sense on its own, with enough context and links to the next steps.

Review real journeys

I ask someone unfamiliar with the site to complete a task using only the help content. Watch where they hesitate or open unrelated pages. Support data can show repeated questions after publication, but interpret it alongside product and process changes. A rise in contacts may have several causes.

Keep a record of changes and redirects so old links remain useful. If you combine pages, update internal links and saved replies, then verify the destination. The goal is a coherent journey, not merely an updated sitemap.

Use search and navigation labels that match customer tasks rather than internal teams. A category called “Operations” may make sense to staff but may not tell a shopper where to find delivery or returns guidance. Test labels with people who didn’t build the help centre. If they predict the wrong destination, the structure or wording needs to change.

Avoid a single catch-all page that repeats links to every task. A landing page should help readers narrow their need, not make them scan a long list. Consider whether search within the help centre returns specific answers and whether filters are understandable.

Keep a record of the route a page supports: its audience, task, source of truth and related next steps. This lets editors decide whether a proposed article fills a gap or duplicates an existing step. It also makes it easier to update connected pages when a process changes.

For a task that crosses teams, keep the public guidance focused on the customer and use internal handoffs behind the scenes. The shopper shouldn’t need to understand whether fulfilment, finance or product support owns a step. The organisation can route the request internally while the page presents one clear path. Confirm that the service team agrees with the customer-facing description before publishing it.

So pick one task on your help centre, like starting a return: can a customer finish it without being sent to a second page that repeats the same steps?