Zendesk integration guide

How to keep Zendesk up to date

Your Zendesk Help Center has review tools, but none of them keep your articles in sync with your product's changes.

Book a demo Audit your help center for free →

Keeping help centers accurate at

The short answer

What Zendesk offers: Your Zendesk knowledge base has features like article verification, flagging conflicts from tickets, and Team Publishing, which cover basic article maintenance for Enterprise plans.
Where it stops: Zendesk's help center features are reactionary. When a feature in your product changes, the article is only identified as incorrect when a customer notices.
Where Solo fits: Solo reads your code and feature flags, identifies the articles that a change to your product made wrong, and drafts updated copy that your team approves.

On this pageShort answer

Why it matters

Why an accurate Help Center matters

Reduce tickets with self-serve support

You train your customers to visit the Help Center first, but as soon as an article describes an outdated step, they lose trust and revert back to opening support tickets. An accurate help center is the only way to scale support

AI agents repeat whatever the articles say

Zendesk AI agents, like Forethought, draw their answers from your knowledge sources, so an out-of-date article turns into an incorrect reply to a customer. What started as an incorrect article now turns into an unhappy customer.

Help Center articles also feed search results

A public Help Center shows up in search engines, and AI answer engines may quote it, so an undocumented feature could mean you're missing out on website traffic.

Built-in tools

What Zendesk already offers for knowledge base maintenance

Zendesk Knowledge features have some features already in place for article maintenance, like review reminders, flagging inaccuracies from tickets, and a staged approval flow. Most of these features sit on the Enterprise plans. These tools run on dates and on what people notice, which suits products that don't change frequently more than the modern company that ships daily.

Stage	Zendesk's features	Missing features
01Know upcoming changes	Zendesk has no feature for this stage, so knowledge of a change to your product has to come from outside the platform, like a product manager or a developer.	Nothing warns you that an article is about to become out of date. Zendesk has no feature for this stage, so a change to your product reaches the Help Center only if someone outside the platform mentions it.
02Identify outdated articles	Zendesk's article verification feature reminds owners to re-confirm articles on a predefined schedule. Users can also use Add feedback in the Knowledge panel to flag an article from a ticket.	Article verification runs on a schedule and flagging from tickets relies on someone noticing, so both depend on your team's capacity. Neither compares an article with your product.
03Draft updated copy	Drafting happens by hand in the article editor, where the owner rewrites the text themselves.	Zendesk gives no context on what has changed in your product and proposes no updated copy, so the owner rewrites the text by hand.
04Collaborate on updates	Team Publishing lets you assign articles and move them through Draft, Awaiting Review and Ready to Publish.	Team Publishing tracks who is reviewing, not what is wrong, so reviewers still have to find out what changed in your product.
05Publish changes	The Ready to Publish and Published states let you stage an update without touching the live article.	The last step stays manual. Nothing publishes an update when a feature flag turns on, so the article goes live on someone's schedule rather than when your product changes.

Content Cues was removed in 2025

Zendesk announced that one of their main content editing features was going to be sunset on January 13, 2025. Content Cues removal took effect on May 1, 2025.

What it did

Content Cues used ticket data to point out gaps in a knowledge base.

What Zendesk suggests now

Zendesk's removal notice points to a new feature called Knowledge Base Gaps Discovery, which works from AI agent conversations instead of ticket data.

With Solo

Knowledge base management with Solo on top of Zendesk

Solo connects to your code base, feature flags, and your Zendesk articles. It finds the articles a change to your product made wrong and drafts the fix. Your team reviews each draft before anything goes live.

What Solo adds to Zendesk's built-in tools

Stage	Zendesk without Solo	Zendesk with Solo
01Know upcoming changes	Zendesk has no feature for this stage, so knowledge of a change to your product has to come from outside the platform, like a product manager or a developer.	Solo watches your code and feature flags and warns you which articles are about to go out of date, with no need to involve engineers.
02Identify outdated articles	Zendesk's article verification feature reminds owners to re-confirm articles on a predefined schedule. Users can also use Add feedback in the Knowledge panel to flag an article from a ticket.	Solo compares each change to your product with your articles and flags the ones that are now wrong, with the reason, without waiting for a review date or a ticket.
03Draft updated copy	Drafting happens by hand in the article editor, where the owner rewrites the text themselves.	Solo drafts the corrected text from your product change, so editors start from a draft with context instead of a blank page.
04Collaborate on updates	Team Publishing lets you assign articles and move them through Draft, Awaiting Review and Ready to Publish.	Each draft goes to a person with your product change behind it, so reviewers see what changed and approve before anything goes live.
05Publish changes	The Ready to Publish and Published states let you stage an update without touching the live article.	Once your team approves a draft, Solo can hold it until the feature flag is enabled, then publish it to the Zendesk article, so the Help Center changes when customers get the feature.

Questions

Zendesk knowledge base best practices

These are the questions teams ask most when they start reviewing their articles.

How often should help articles be reviewed?

Article verification lets you set an interval, such as flagging articles not verified within six months, and owners get reminders until they confirm. Pick the interval by how fast the feature behind each article changes, and review fast-moving areas sooner. A review interval only measures based on time, so a product that changes frequently needs a different style of review.

How do I run a knowledge base audit in Zendesk?

Start with Zendesk's Needs verification list and the articles agents have flagged from tickets. Then check the articles tied to features you changed since your last audit against your product itself. To save time, try using an AI tool like Solo that compares your Zendesk articles against your product's code.

Can Zendesk AI agents use outdated articles?

Zendesk AI agents answer from your knowledge sources, so they repeat what the articles say, right or wrong. Fixing articles is what fixes AI agent answers. You can use tools like Solo to fix articles before they're used by AI agents.

Does Zendesk update articles when your product changes?

No. Zendesk's maintenance features run on schedules and on people raising flags, not on your code or feature flags like Solo does, so none of them can tell when a screen or setting in your product moved. Verification, flagging and Team Publishing all rely on someone noticing, and Solo covers the product-change side.

Do I need an Enterprise plan to maintain Zendesk articles?

Article verification and Team Publishing require Enterprise or Enterprise Plus with Knowledge Enterprise. Flagging from tickets is available on Growth and above suites, and on Support with Guide Professional or Enterprise. On lower plans you can still review articles by hand. Solo is a tool that can audit your Zendesk articles without changing your Zendesk plan.