WordPress plugin · v0.1 · GPLv3
HelpWP bundles a knowledge base, a client ticket system, an embeddable chatbot, and an auto responder that only speaks up when it’s actually useful - all in one plugin, one admin menu, one settings option.
Four modules, one plugin
Each module is independently useful. Turn on the ones you want, ignore the rest.
A first-class post type for help articles with topics, products, configurable URLs, and reader voting.
A full ticketing system with eight statuses, role-based access, and passwordless email login.
A self-contained JS widget that answers from your docs via RAG. One <script> tag, any site.
Replies to new tickets only when relevance clears your threshold — and backs off the moment a human steps in.
Docs
A first-class WordPress post type with hierarchical topics, shared products, configurable URLs, voting, syntax highlighting, and a grouped archive shortcode.
helpwp_product_post_types filter.
POST /docs/{id}/vote
so you can plug your own analytics in.
[helpwp_docs]
// scoped to one product:
[helpwp_docs product="woocommerce"]Tickets
A full client ticketing system with role-based access, automatic status transitions, a passwordless email login, and a REST API for everything.
/helpwp/tickets/embed renders the ticket UI in an iframe-safe shell,
so you can drop the help desk into any external site.
##ticket_id##, ##client_name##, ##ticket_link##.
Status: Open. Agent and client both get a notification email.
Status auto-flips to In Progress. Ball is in the client's court.
Status auto-flips to Waiting. Reappears in the agent queue.
Status: Resolved. Auto-transitions stop. Client can reopen.
Status: Reopened. The thread comes back into the active queue.
How the AI knows your product
Both the chatbot and the auto responder answer from a vector index built off your docs. No prompt engineering, no fine-tuning, no manual uploads. The whole feedback loop is two steps and lives inside WordPress.
Author it in the WordPress editor like any other post, or migrate from BetterDocs, weDocs, Echo KB, BasePress, Awesome Support, SupportCandy, or JS Help Desk in a single click.
One button in HelpWP → Settings → AI ships every published doc to the RAG backend. Embeddings are generated, the vector index is rebuilt, and only the deltas are re-embedded on subsequent runs.
The chatbot widget and the ticket auto responder both query the same index. Edit a doc, hit Sync again, and the next answer reflects it. No re-deploy, no model retraining.
Under the hood: a small Python service indexes your docs into a vector store.
Every /ask and /respond call retrieves the most relevant
chunks and grounds the model's reply on them, with a relevance score returned alongside
the answer so the auto responder can stay quiet when confidence is low.
AI Chatbot
The chatbot reads from a vector index of your synced docs - not the open internet. It answers in your voice, from your content, and never invents features you haven’t shipped.
<script> tag into any HTML page, or generate a tiny companion plugin straight from the admin.
data-show-on / data-hide-on rules with wildcards. Hide on checkout, surface on docs - without forking the script.
mon-fri:9-17. Outside hours, swap in an offline greeting or hide the launcher entirely.
<script
src="https://helpwp.dev/cdn/chat.min.js"
data-site-key="YOUR_SITE_KEY"
data-agent-name="Luna"
data-primary-color="#2563eb"
data-welcome-message="Hi! Ask me anything about
our product."
data-suggested-prompts="Reset password | Where's my
order? | Pricing"
data-auto-open="delay"
data-auto-open-value="15"
data-business-hours="mon-fri:9-17"
data-hide-on="/checkout/*"
data-panel-width="420"
data-panel-height="640"
defer
></script>AI Auto Responder
Most auto-reply systems fire on every ticket. Ours runs on a delay, checks its own confidence, and backs off when a human is already in the thread.
Client submits a question. Bot job is scheduled for +5 min.
Bot job is cancelled. Client gets a human answer. Done.
Bot queries the RAG index, scores the best match.
Post the reply as a ticket comment, optionally flip status to in progress.
Stay quiet. Log the abort. Wait for an agent.
One-click migration
HelpWP ships with first-party importers for the most common knowledge-base and ticketing plugins. Articles, categories, tickets, replies, attachments, and product terms map straight into native HelpWP posts. Resumable, batched, idempotent.
Articles and doc_category terms map to HelpWP docs and topics. Tag taxonomy is preserved.
Container pages (parents with children) become HelpWP topics; leaf pages become docs. Hierarchy is kept.
Multiple KBs supported. Articles, categories, and tags fold into one unified HelpWP library.
BasePress knowledgebase articles and knowledgebase_cat categories migrate into docs and topics.
Tickets, replies, attachments, and product / department terms become HelpWP tickets, comments, and taxonomies.
Tickets, threads, customers, agent assignments, categories, priorities, tags, custom fields, and attachments map straight into HelpWP tickets and comments.
Tickets, replies, departments, products, priorities, custom fields, and attachments from the js_ticket_* tables become HelpWP tickets, comments, reasons, and products.
Each migrated post stores a _helpwp_migrated_from_* meta key, so re-runs are idempotent and a Clean Up button rolls everything back.
Find the importer at HelpWP → Settings → Migration. Source plugins must be installed and activated before they appear in the list.
Under the hood
No hidden layers. No custom admin UI to learn. Everything you’d expect from a well-behaved plugin.
One helpwp_settings option, keyed tab → section → field. Extensible via the helpwp_settings_menus filter.
Composer-powered, namespaced HelpWP\. Controllers are glob-autodiscovered - drop a file in the right folder and it boots.
Docs, tickets, comments, taxonomies, AI register/verify/sync, and the helpwplogin flow - all at /wp-json/helpwp/v1/.
Ticket lifecycle events fire at helpwp-tickets-*. Listen, filter, replace. The auto responder itself is just another listener.
The passwordless “helpwplogin” flow means zero password-reset tickets. Clients get a short-lived link by email and they’re in.
Docs archive, ticket list, and submission form are drop-in shortcodes. Paste, save, done - works with every theme and block editor.
Doc queries cache via WP object cache (Redis/Memcached) or transients. Configurable TTL, auto-invalidated on every save or delete. Toggle under Settings → Docs → Cache.
Get running
You need to Download HelpWP, install on your site and activate it. The CPTs, taxonomies, roles, and settings are registered on first boot.
Create three pages and paste [helpwp_docs], [helpwp_tickets], and [helpwp_new_ticket]. You now have a live knowledge base and ticket system.
Open HelpWP → Settings → AI, register the site, verify by email, hit Sync. The chatbot embed and auto responder are now live.
HelpWP is free and GPLv3. No account required for the core plugin. AI features need a registered site key - also free for reasonable use.