gmsspress

gmss-agent adds a customizable floating chat widget to every page of your WordPress site. Visitor questions are answered by matching them against a JSON knowledge-base file you provide. Everything runs locally on your server — no API key, no third-party service, no visitor data sent anywhere.
The plugin is designed for support, FAQ, and lightweight pre-sales conversations where you want answers limited to information you have written and approved.
Features
<ul>
<li>Floating chat widget with configurable title, welcome message, primary color, and corner position (bottom-right or bottom-left).</li>
<li>Local matcher with weighted token-overlap scoring: title hits and explicit keyword hits are ranked above body hits, with a phrase bonus when the visitor’s full query appears in an entry.</li>
<li>Optional <code>keywords</code> array on each entry to handle synonyms the body text does not contain.</li>
<li>Configurable fallback reply when no entry matches the visitor question.</li>
<li>JSON knowledge base loaded from a single <code>knowledgebase.json</code> file at the root of your WordPress install.</li>
<li>Ships with a sample knowledge base so the widget answers something out of the box.</li>
<li>REST endpoint protected by a WordPress nonce.</li>
<li>Translation-ready (text domain: <code>gmss-agent</code>).</li>
</ul>
Requirements
<ul>
<li>WordPress 5.8 or newer and PHP 7.4 or newer.</li>
</ul>
<h3>Privacy</h3>
The plugin does not set cookies, does not write to any custom database tables, does not contact any external service, and does not log visitor messages on your server. Settings are stored in the standard WordPress <code>wp_options</code> table and are removed when the plugin is uninstalled via the Plugins screen. The knowledge base file you create is read from disk on each request and is never transmitted off your server.

gmss-agent

Floating chat widget that answers visitor questions from a JSON knowledge base on your own server. No external API, no data leaves your site.

socranext

What the plugin provides 
– Custom Post Type <code>socranext_post</code> for AI-optimized articles (default URL slug <code>artikelen-sn</code>, configurable via the SocraNext platform). 
– Custom Taxonomy <code>socranext</code> (hierarchical) for categorizing those articles. 
– Knowledge Base page (WordPress page; default slug <code>kennisbank-sn</code>, configurable via the SocraNext platform). 
– Template-based rendering for single/archive and knowledge base views (plugin templates via <code>template_include</code>). 
– Admin screens under SocraNext (Overview, Articles, Categories). FAQ management is handled via the SocraNext platform. 
– Cache flush on (de)activation to correctly register permalinks.
Display 
The plugin renders views via bundled templates for: 
– Single SocraNext articles and archive list. 
– Knowledge base page with categories and Q&As.
Structured Data 
– The FAQ display includes FAQPage JSON-LD to help search engines and AI systems better understand the Q&As.
REST API (for platform integration) 
Under the namespace <code>socranext/v1</code>, routes include: 
– <code>GET /pages</code> and <code>GET /pages/{id}</code> – list site pages (for adding/showing FAQ widgets). 
– <code>POST /toggle</code> – enable/disable the FAQ widget per page. 
– <code>POST /store-aio-information</code> and <code>GET /aio-information/{page_id}</code> – store/retrieve per-page FAQ data. 
– <code>POST /kennisbank</code> and <code>POST /kennisbank-custom</code> – store knowledge base categories and custom markup/styles. 
– <code>POST /blog</code> and <code>POST /store-blog-custom</code> – create articles and store global custom HTML/CSS/JS for article display. 
– <code>POST /collection-slugs</code> – sync configurable articles/knowledge-base URL slugs from the SocraNext platform (rewrite flush + cache purge). 
– <code>GET /articles-list-custom</code> – retrieve configuration for list views. 
– <code>POST /llmstxt</code> and <code>GET /llmstxt</code> – publish and read <code>llms.txt</code> / <code>llms-full.txt</code> content from the SocraNext platform; served at <code>/llms.txt</code> and <code>/llms-full.txt</code> on the site.
<blockquote>
Note: without an account/connection to app.socranext.ai, the auto-generation routes are typically not used, but the created post types, taxonomy, and pages remain available for display.
</blockquote>
Privacy & external services 
– The plugin does not call external APIs on its own; the integration is typically initiated by the SocraNext platform to your website. 
– Websites: product site https://socranext.ai and platform https://app.socranext.ai.
<h3>Prefix & naming policy</h3>
<ul>
<li>All plugin identifiers use the unique prefix family “SocraNext”:
<ul>
<li>Functions, hooks, options, AJAX actions, REST namespace, script/style handles: <code>socranext_*</code> (lowercase)</li>
<li>Constants: <code>SOCRANEXT_*</code> (uppercase)</li>
<li>Human-facing labels and PHP namespaces (if used): <code>SocraNext</code> (PascalCase)</li>
</ul>
</li>
<li>We avoid reserved prefixes like <code>wp_</code>, <code>_</code>, and <code>__</code> for custom identifiers.</li>
<li>Existing options and routes already comply; no migrations are required.</li>
</ul>

SocraNext

AI-ready content: articles CPT, knowledge base with FAQ JSON-LD, and per-page FAQ widget. Integrates with the SocraNext platform for auto-publishing.

gmss-agent vs SocraNext