Philippines staffing blog ·

Turn a resolved ticket into a knowledge article that holds up

How to convert one good resolution into an article with a clear audience, a testable answer, and an owner who keeps it current.

Turn a resolved ticket into a knowledge article that holds up help desk operations illustration

Direct answer

Operational guidance

Pick a ticket worth turning into an article

Not every good resolution deserves an article. Choose a ticket that solved a recurring question, used a repeatable decision path, and produced an answer a new agent could apply without the original thread. A one-off exception teaches the team more about escalation than about documentation. The best candidates are the requests that appear in the queue two or three times a week under slightly different wording.

Check the ticket for hidden dependencies before you write. If the fix only worked because one administrator had a temporary permission, the article needs to say so or it will fail for everyone else. If the answer depends on a customer contract or a regional rule, name that condition in the first paragraph. A useful article describes the boundaries of its own advice, not just the happy path.

Write from the customer's question

Open the article with the question in the words customers use, because that is how the article will be found. Then give the answer in one short paragraph before any background. A reader who is already frustrated should not have to scroll through company history to learn which button to press. The title and the first sentence should match the same search phrase.

Use the second section to explain why the answer works, but keep the explanation tied to the action. A short reason helps an agent adapt when the screen looks different from the screenshot. A long theory lesson does not. If the process has more than one branch, show the branch condition first and the steps second so the reader knows which path applies.

Separate the steps from the judgment

Numbered steps should be mechanical enough that two agents produce the same result. Put judgment calls in a separate note beside the step, such as when to stop and ask the account owner. Mixing a decision into a numbered action hides the point where authority changes hands. That separation is also what lets a reviewer check the article against a real ticket.

Name the evidence the agent should leave in the ticket for each step. A step that says verify the account is not testable until the article says which system to check and what a pass looks like. The evidence note also makes the article easier to update when a system changes. When the interface moves, the steps change and the evidence rule usually survives.

Test the article against old tickets

Take ten closed tickets that match the article's topic and walk through the article without reading the original replies. Mark where you had to guess, where a link was stale, and where the customer's situation did not fit. Those marks are the edit list. This test is faster than asking the team whether the article looks good, and it produces specific changes.

Include at least one ticket that was escalated. An article that only covers clean resolutions teaches agents to force a fit when the case is unusual. Show the stopping point and the escalation route in the same article so the reader does not have to find a second page. A documented stop is part of the answer, not a failure of the article.

Give the article an owner and a review date

Every published article needs a named owner who understands the system it describes. The owner does not have to write every edit, but they must approve changes that alter the decision path. Set a review date based on how often the underlying product changes, not on a uniform annual calendar. A stable policy page and a fast-moving admin console do not need the same rhythm.

Record the review in a small log with the date, the reviewer, the change, and the tickets that prompted it. That log lets a new reviewer see why a step exists without reopening a closed debate. It also shows when an article has quietly gone two cycles without a check. An article with no owner is a page, not a maintained control.

Make the article easy to scan

Agents read under time pressure, so put the answer near the top and keep each step to one action. Use the customer's question as the section heading and avoid clever titles that only make sense after reading the page. Bold the words that appear in the interface so the eye can find them quickly. A short article that answers the question beats a comprehensive page that buries the answer below background.

Screenshots help only when they are current and annotated. A full-screen image with no marker forces the reader to search for the one field that changed. Crop to the relevant area and add a short caption that says what to look for. Review the images on a phone as well, because a screenshot that is readable on a desktop can be useless on a narrow screen.

Add a short section for related questions that the article does not answer, with links to the right page. This keeps the reader from forcing the article to cover a case it was never meant to handle. It also gives the reviewer a place to notice gaps without rewriting the whole page. Keep the list to three or four links so it stays a signpost rather than a second article.

Retire articles that no longer match

When a product change makes an article wrong, remove it from the agent's main view instead of leaving a warning at the top. Agents under pressure read the first instruction and skip the caveat. Redirect the old link to the replacement article and keep the old version in an archive for audit purposes. A visible wrong answer is worse than a missing one because it carries authority.

Review the retirement alongside the replacement so the queue does not lose a topic. If no replacement exists, write the gap into the knowledge backlog with an owner and a target week. Tell the agents which phrase to use while the gap is open so customers get a consistent answer. The measure of a knowledge base is not how many articles it holds but how many still help.

Authoritative sources

Related planning pages