Turn your help center into a chatbot that answers from your own articles
SleekAI reads your docs, kb_article, or helpie post types directly from wp_posts and wp_postmeta, retrieves the matching articles for each question, and answers in plain language using your OpenAI, Anthropic, Google, or OpenRouter key.
Most help center search is still a list of blue links
Help center search has been the same shape for fifteen years. The visitor types a phrase, the page reloads with a stack of titles, and they click through three articles before finding the one with the actual answer (often buried in step seven of a long guide).
Search teams have tried algolia, elastic, and synonym tuning, and the experience still bottlenecks on the human having to skim a list. A chatbot trained on the same content can read those articles for the user and reply with a synthesized answer plus a link.
What makes this different from a generic site chatbot is the scoping. A help center is a specific surface with different rules than your homepage. SleekAI lets you constrain the bot to the docs custom post type, exclude marketing pages, and apply a sterner system prompt that says ‘do not invent steps, cite the article’.
You can run a separate, friendlier bot on the homepage that does answer from blog posts and product pages. Two bots on one site, each scoped to the content that matters for that surface.
Features
Docs-aware retrieval
Point SleekAI at the docs custom post type your help center already uses.
Two-bot pattern
SleekAI’s multibot feature handles two bots on one site with separate prompts, models, and scopes.
Answers from your data
Map post titles, content, post meta, taxonomies or a WP_Query into the instruction, and the bot answers from what your site actually publishes.
Where a knowledge base chatbot pays off
Support ticket deflection
Teams see the support volume drop on questions whose answers were already in the docs.
Onboarding for new users
Trial users ask their actual first questions in plain language, the bot points them at the right walkthrough, and the friction of finding the article is removed entirely.
Internal team enablement
Staff querying the same docs save the back-and-forth in Slack. The internal version of the bot can also pull from a private staff CPT alongside the public docs.
How the chatbot reads your help center
Identify the docs CPT
In the Variables tab, tick the custom post types your docs plugin uses (BetterDocs docs, Helpie helpie_kb, weDocs, or a custom CPT).
Scope the bot to the help center
The chatbot only loads on those pages, leaving marketing and home pages free for a different bot.
Set display conditions
Decide which pages, post types, roles or logged-in states show the chatbot.
Map your data
Choose the posts, fields, taxonomies or users the bot should know and reference them in the instruction.
Why a knowledge base chatbot is not just nicer search
It is tempting to treat a chatbot as a fancier search bar bolted onto the help center, but the interaction is different in kind. Search answers with a list of documents and leaves the synthesis to the user. A chatbot answers with a synthesis and points at the documents for verification. The first works when the user already knows roughly which article they need.
The second works when they do not, which is the actual entry point for most help center traffic. The visitor who searches ‘reset 2FA’ might find the right article on the first try. The visitor who types ‘I changed my phone and now I cannot log in’ will not find that article through search because none of those words appear in the title.
A chatbot with retrieval can match the intent rather than the keyword, find the 2FA recovery article anyway, and surface it. Building that experience on top of WordPress, with the docs CPT read directly and the bot scoped to the help center, gives you something that improves with the same workflow your editors already use.
They write the article, save the post, the bot uses it within seconds. There is no separate index, no separate vendor, and no separate dashboard for the support team to learn. The chatbot becomes a thin layer over content the team is already maintaining, which is the only way it stays accurate for long.
Frequently asked questions
Which docs plugins are supported?
BetterDocs (post type docs), Helpie WP (helpie_kb), weDocs (docs), Echo Knowledge Base (epkb_post_type_*), and any custom CPT you register yourself.
Can I exclude certain articles from the bot?
Yes. The Variables tab lets you exclude specific post IDs, exclude a docs category or tag (taxonomy term), or set a custom meta flag like kb_exclude_from_chat. A common pattern is to keep deprecated articles published for SEO while excluding them from the chatbot’s index.
Which AI providers does it support?
OpenAI, Anthropic, Google and OpenRouter, plus custom OpenAI-compatible endpoints. You bring your own API key and the provider bills you directly.
Where does the chatbot get its answers?
From the WordPress data you map into its instruction: post titles and content, post meta, ACF and Meta Box fields, taxonomies, terms, users and user meta, or a WP_Query. Values resolve on every request.
Can it act on a visitor’s behalf?
No. A chatbot answers questions.
Can I control where the chatbot appears?
Yes. Display conditions cover post type, post, post status, post template, taxonomy, term, user role, logged-in state and WordPress conditional tags such as front page, archive, search and 404.
Are conversations stored?
Only if you turn on logging for that chatbot. SleekAI then stores each visitor message and each completed reply, which you read and delete on the chatbot’s Logs page, and a retention period can delete old logs.
Can I run more than one chatbot?
Yes. Each chatbot has its own instruction, data, display conditions and styling, so different sections of a site can get different bots.
Pricing
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
…or get the Bundle Deal
and save €250
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
SleekAI
SleekByte
SleekMotion
SleekPixel
SleekView
SleekRank
SleekTrack