Keep Zendesk if its queue, routing, and agent workflows work. Evaluate a separate help center if the public site is the thing holding you back. These are two different purchases. A prettier help center won't replace an escalation queue, and a better queue won't make outdated articles easier to maintain.
This is a buyer guide based on a public review sample and current Zendesk documentation, not a hands-on rating. DocsAlot publishes this guide and competes for the help-center work, not for replacing a full help desk.
What reviewers find difficult
One current user on G2 described a slow setup when customizing triggers and workflows. The same reviewer valued automated routing, macros, and self-service. G2's review summary also surfaces setup and cost as concerns. Those are reasons to ask what you will use, not evidence that a configured Zendesk inbox needs replacing.
If you're already paying for and using that inbox, compare your incremental costs. Moving the public site while retaining the same plan doesn't remove your existing seat bill. A separate site has to earn its keep through easier publishing, a better reader experience, or less theme work.
Where the help-center tradeoff is real
Zendesk's standard Copenhagen theme supports basic branding and receives automatic updates. Zendesk also supports custom themes. Its theme editing docs warn that a trial includes code editing that isn't available on Suite Team, and code-customized themes don't automatically receive new theme features. If the stock theme fits, that tradeoff may not matter. If it doesn't, test the design on the plan you will actually buy and name the person who will maintain it.
Article freshness is a separate question. Zendesk already has article verification reminders. If nobody owns the article or checks it after a release, moving the page alone won't fix that. Try the Zendesk maintenance workflow first.
How to decide with three pages
- Pick a top landing page, an image-heavy troubleshooting article, and a restricted or translated article.
- Ask the support lead to make and preview a real edit. Check mobile navigation, search, article permissions, and who needs to approve it.
- Submit a test request through the proposed site. Verify the ticket arrives in the same Zendesk queue with the context agents need.
Keep the integrated help center if your agents depend on its audience controls or workflows and the design is good enough. If the inbox works and only the public docs need a new home, use the Zendesk migration guide and see a live DocsAlot help center before committing to a switch.