Practical framework / 5 MIN READ
Make the help article finish one customer task
Replace policy-shaped pages with answers people can find and use.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A knowledge article should help a person complete a specific task or understand a specific condition. A large collection of accurate paragraphs can still fail if the answer is buried or the next step is unclear.
What you will leave with: Create one task-focused article with prerequisites, steps, exceptions and a clear route to human help.
Use this when
- Support repeatedly answers the same practical question.
- Customers find a help page but still cannot complete the task.
This is not a strategy for hiding human support or proving ticket reduction from page views alone.
Choose a task that customers actually recognize
Start with recurring questions from legitimate support analysis. Translate internal labels into the words customers use. “Change the delivery address before dispatch” is a task; “Order-management functionality” is an organizational category. Keep private details out of the working example and source material.
Distinguish a task from a policy explanation. Someone asking how to start a return may need steps, while someone asking whether an item qualifies needs conditions. These can link to each other without becoming one long page that answers neither quickly. Define the audience and supported product or process version before drafting.
Write the shortest complete path
Begin with the outcome and any prerequisites, then provide ordered actions in the sequence the customer sees them. Use the actual names of controls and explain what should happen after an action. Include a recognizable completion state so the reader knows whether the task succeeded.
Zendesk’s primary guidance recommends clear, consistent knowledge content and article templates. Treat a template as a completeness check, not a reason to add empty sections. Screenshots can help when interface location matters, but the essential instruction should remain readable as text. Remove decorative introduction that delays the first useful answer.
Explain exceptions without making the main path unreadable
Identify the conditions under which the standard process will not work. For an address change, that might be an order already dispatched or a market-specific restriction. State the boundary before the reader spends time attempting an impossible action. Link to a suitable alternative or human route.
Do not ask people to retry indefinitely when the system cannot support their request. Specify what information support needs and why, while avoiding unnecessary sensitive data. If a task affects payment, security or legal rights, route it through the authorized process rather than inventing a shortcut. Keep internal diagnostic steps out of public instructions unless they are safe and intended for customers.
Maintain the answer as part of the product
Assign an owner and a review trigger tied to interface, policy or fulfillment changes. A fixed annual review can miss a broken instruction immediately after a release. Keep links and screenshots aligned with the current experience, and preserve appropriate version distinctions when customers still use older products.
Test the article with someone who has not seen the process. Observe whether they complete the task without being coached. Page views, helpfulness votes and ticket trends can inform the review, but none alone proves successful self-service. A sudden reduction in tickets might mean customers gave up. Keep a clear path to contact support and inspect unresolved journeys.
Make the reasoning concrete.
A fictional stationery retailer has a long “Orders” help page. Customers cannot find how to correct an address before dispatch, even though the necessary instructions appear near the bottom.
Dedicated task article
Opening: Create “Change your delivery address before dispatch” with eligibility, exact steps and a completion check.
Hypothesis: The customer can find the answer and know whether the change succeeded.
Risk: The instructions must stay aligned with the actual order system.
Longer general page
Opening: Add another paragraph about address corrections to the existing page.
Hypothesis: The content remains in one place.
Risk: The answer may still be difficult to locate or distinguish from other order topics.
Publish the task-focused answer through the approved content process, link it from relevant order help and test it without coaching the reader.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Customer task
What is the reader trying to accomplish in their own words?
Prerequisites
When is the process available and what is needed?
Completion state
How will the reader recognize success?
Exception route
What should happen when the standard path is unavailable?
Maintenance trigger
Which operational change requires this article to be reviewed?
Watch for the wrong conclusion.
- Organizing answers only around internal departments.
- Using page views as proof that the problem was solved.
- Leaving no human route when the documented process fails.
Your next action
Turn one frequently repeated support answer into a single-task article and observe an unfamiliar reader trying it.
Sources & scope
Frameworks, worksheets and proposed tests are original editorial synthesis. Examples are hypothetical and do not report measured outcomes. Source checking is not an independent audit of effectiveness. Platform features and applicable law can change. No named human author or reviewer is claimed.
- Zendesk Help: Developing content for your knowledge base →Primary provider guidance · Supports: Primary vendor guidance on clear, consistent knowledge content and article templates. It is practical vendor advice, not independent evidence of reduced support demand.