Knowledge Capture in Zendesk
The answer already exists. An agent wrote it out beautifully at 4pm on Tuesday, sent it to one customer, and it died in a ticket. Knowledge capture in Zendesk is the fix.
What knowledge capture in Zendesk is
Knowledge capture is the set of features that let an agent work with help centre content without leaving the ticket. It started life as a separate app and now lives in the knowledge section of the agent context panel.
Three actions, and they get used in wildly different proportions.
The linking gets adopted immediately because it makes an agent's job faster. The drafting needs deliberate encouragement, because it makes today slower in exchange for making three months from now faster, and that's a trade nobody under pressure makes on their own.
Which tickets are worth capturing
Not many, which is the point people miss. Capturing everything produces a knowledge base nobody can search.
The test is simple: would a second customer ever ask this? If yes, and the answer took real effort to construct, it's a candidate.
What is not worth capturing: account-specific answers, one-off incidents, and anything that will be untrue after the next release. Writing an article with a two-week shelf life is a cost, not an asset.
Keeping the quality bar up
Drafts created from tickets have a specific failure mode. They read like a reply to one person, because that is what they were.
The gap between a good ticket reply and a good article is real work. A reply assumes context: it knows the account, the plan, what was already tried. An article knows none of that and has to open by telling a stranger whether they're in the right place.
Four rules keep the bar where it needs to be.
One owner per publish. Somebody reviews and publishes. Drafts do not self-promote, and a queue of 200 unreviewed drafts is a graveyard, not a backlog.
A template. What this covers, who it is for, the steps, what to do if it doesn't work. Same shape every time so readers learn where to look.
Strip the specifics. Remove the account name, the order number, the "as we discussed on the call". Generalise the problem statement.
A retirement date. Every article gets reviewed on a schedule or it gets archived. Wrong documentation causes more tickets than missing documentation, because people follow it.
Making it happen at all
Every support team agrees knowledge capture is important and most do it for six weeks.
What survives is the version with a small, specific commitment attached: one draft per agent per week, reviewed on Friday, published or rejected within a fortnight. Not "capture knowledge when you can". Nobody has ever had a spare hour in support.
Two things help more than exhortation. Give agents thirty protected minutes for it, in the calendar, off the queue. And show them the article view counts, because a writer who sees their article read 400 times writes another one.
What to measure
Keep it to three numbers and you'll actually look at them.
Articles linked per solved ticket, which tells you whether the content is findable and whether agents trust it. Articles created and published per month, which tells you whether capture is alive. And self-service views against ticket volume for your top topics, which is the only number that shows deflection.
If linking is high and creation is zero, your content is good and going stale. If creation is high and linking is low, you're writing things nobody can find. The help centre guide covers the findability half.
Frequently asked questions
How do you create an article from a ticket in Zendesk?
With the Knowledge app in the ticket sidebar: draft from the reply you just wrote and send it for review. That single habit is the whole Zendesk knowledge base workflow, and it's what turns knowledge capture into Zendesk knowledge management rather than a folder of drafts.
Do I need the app for knowledge capture in Zendesk?
The capability is built into the knowledge section of the agent context panel in the modern workspace. Older accounts may still run it as a separate app.
Can agents publish articles directly?
You control that with permissions. Most teams let agents create drafts and restrict publishing to a small group, which is the right balance.
How many articles should we have?
Fewer than you think. Twenty articles covering your top twenty questions beats 300 covering everything, because search quality falls as volume rises.
Does knowledge capture reduce ticket volume?
Indirectly. Linking articles into replies teaches customers the content exists. Deflection comes from the help centre being findable and current, not from the capture step itself.
Same question, three tickets
The questions worth documenting are the ones arriving repeatedly, sometimes from the same person twice.
Start free trial14-day free trial. No credit card required.