A chatbot plugin that actually fits the platform you already use

"Chatbot plugin" is one of those phrases that hides a lot of variation. For someone running a Shopify store it means an App Store listing with a one-click install button. For a Drupal site it means a module enabled through the extension manager. For a headless Strapi back-end it means a plugin that shows up in the admin panel and configures how the widget is served on the decoupled front-end. For a Ghost publication it means something different again. The word is shared, the mechanics are not, and a chat vendor that ships only a WordPress plugin is quietly excluding huge swathes of the web.

Asyntai took the opposite route on purpose. Rather than picking a single favourite CMS, the team builds and maintains a catalogue of native chatbot plugins — thirty of them and counting — across traditional CMSes, ecommerce engines, headless content platforms and back-office suites. The list as of this writing covers WordPress, Shopify, WooCommerce, Magento, OpenCart, Joomla, Drupal, Odoo, TYPO3, Concrete CMS, October CMS, Grav, Statamic, MODX, Umbraco, Strapi, Ghost, Kirby, Bludit, Craft CMS, e107, Bagisto, Sylius, Dolibarr, Medusa, BigCommerce, DatoCMS, Sanity and Contentful. For anything outside that list — custom Rails stacks, Astro builds, Laravel apps, static Hugo sites, Webflow projects, bespoke in-house frameworks — a universal JavaScript snippet gives you the same chatbot with a two-line paste into your template.

What stays identical across all of these is the part that actually matters. The AI is the same engine, served from the same infrastructure, with the same answer quality. The Asyntai dashboard is the same web app whether you arrived through the Magento extension manager or the Shopify App Store. The pricing is the same: a hundred free messages a month, then paid plans starting at thirty-nine dollars for 2,500 messages. Language coverage is the same: thirty-six UI languages, automatic detection of whichever tongue the visitor opens the chat in, and replies written in that same language without any manual toggle. What changes is the experience of installing and configuring — and that's precisely where a chatbot plugin has to feel native rather than bolted on.

Take a Drupal site as an example. A Drupal admin doesn't want to paste a blob of JavaScript into a block template, fight the cache, and hope the theme doesn't override it on the next update. They want a module in the extensions list, a settings page at admin/config/services, the usual permissions tab, and compatibility with the Drupal cache layer. The Asyntai Drupal plugin is shaped around those expectations. A Magento merchant wants an extension that shows up in the admin tree under Stores → Configuration, respects Magento's cache invalidation rules, and reads the product catalogue through Magento's own APIs rather than scraping the front-end. The Asyntai Magento extension does that. A Strapi team running a headless content back-end wants a plugin registered in Strapi's admin, with role-based access to the Asyntai settings and content-type aware training. The Asyntai Strapi plugin is built for that. None of these feel like warmed-over WordPress code with the labels changed.

For ecommerce stacks specifically, the value of a native plugin compounds. A chatbot that only reads your public blog posts can tell visitors what you wrote about, but it can't tell a shopper whether a specific SKU is in stock, what the price is today, what variants exist, or which product from the catalogue matches the description they just typed. The Asyntai plugins for WooCommerce, Magento, Shopify, OpenCart, Bagisto, Sylius, Medusa and BigCommerce all sync the catalogue — titles, prices, images, variants, stock where the platform exposes it — so the AI can answer product questions and surface product cards directly inside chat. When a shopper asks "do you have this in blue and size medium?", the plugin has already given the AI enough data to answer yes or no without guesswork.

For content-first stacks — Ghost, Statamic, Kirby, Grav, Craft, Bludit, DatoCMS, Sanity, Contentful — the shape of the training is different but the principle holds. The plugin either crawls the rendered site, reads exported JSON/GraphQL content, or subscribes to webhooks when an entry is published, depending on what the platform makes available. Either way, the AI ends up with an accurate picture of what's on the site, and it stays in sync when new articles ship. For a publication, that means a chatbot that can answer "what have you written about X" with real article links. For a documentation site, it means the plugin surfaces the right docs page in response to a natural-language question instead of sending the reader to a static search box.

The install mechanics, while platform-specific, share a common spine. You sign up for a free Asyntai account. You open the Plugins tab of the dashboard. You pick your platform from the grid and either download the package or follow the link to the relevant marketplace listing — Shopify App Store if you're going that way. You install the package through whatever your platform's standard flow is: plugin upload, extension manager, module enable, ZIP extraction. Inside your admin area, you find the Asyntai settings panel and click Connect. A popup opens, confirms you're logged into Asyntai, and stores the connection on your behalf. The site ID gets written to the plugin automatically. No API keys to copy, no manual credential shuffling, no typos in hidden config files. From there, training begins, the widget appears on your site, and you move to customisation in the dashboard.

One aspect of shipping a chatbot plugin that's easy to under-appreciate is what happens when you want to uninstall. With a pasted JavaScript snippet, removal turns into a scavenger hunt — which theme file did it go into, did a developer duplicate it into a second template, is it cached anywhere? With the plugin model, removal is boring: disable the plugin, delete it, done. The widget disappears from every page it was serving, the admin panel entry vanishes, and the cache clears on the next request. Teams that change marketing tools every eighteen months or that audit their plugin stack regularly appreciate this far more than a sales page tends to convey.

For agencies and multi-brand operators, the plugin-plus-universal-snippet combination becomes particularly pragmatic. Imagine running five client sites across three different CMSes. A purely snippet-based chat vendor forces the agency to onboard five different clients to five different dashboards, or to paste snippets into each client's theme and hope the client's developer never strips them out. With Asyntai, the agency installs a native plugin on whichever clients run WordPress, Shopify, Drupal or Magento, uses the universal snippet for the bespoke Rails build, and manages every site from one Asyntai login — the multi-site limits on the Starter, Standard and Pro plans (two, three, and up to ten sites respectively) are designed with that pattern in mind. Each site trains independently so the chatbot on site A answers from site A's content, not some mixed-up composite.

Customisation is intentionally separated from installation. The plugin itself handles three jobs: connecting to Asyntai, piping content to the training layer, and loading the widget on the public site. Everything else — welcome message, colour palette, widget position, suggested questions, smart lead-capture rules, custom instructions that steer the AI's tone, PDF uploads, team members, analytics — lives in the Asyntai dashboard. This split exists because cramming every configuration option into a CMS admin page produces either a mess or a crippled feature set. The plugin owns the parts that belong in the CMS; the dashboard owns the parts that belong in a proper web app. The seam is invisible to end users.

Multilingual behaviour deserves its own mention because it reshapes how a chatbot plugin is chosen. Sites that draw visitors from multiple countries can't afford an English-only chat — organic traffic in 2026 is global by default, and a visitor who asks a question in Portuguese and gets a reply in English usually leaves. Asyntai covers thirty-six widget UI languages — everything from Arabic, Hebrew and Hindi through the major European ones (French, German, Spanish, Italian, Portuguese, Dutch, Polish) to the Nordic set, the CEE languages, and the Asian set (Japanese, Korean, Thai, Vietnamese, Malay, Indonesian, simplified Chinese) alongside English — and the AI spots the language of the first incoming message on its own. There is no separate translation plugin to configure, no locale toggle to wire into your theme. Whatever language a visitor types in, that's the language the chatbot answers in.

Leads are where many teams ultimately measure the plugin against its cost. Every conversation the chatbot has is logged against a visitor record in the Asyntai dashboard. When the conversation includes an email address or phone number — either because the visitor volunteered it or because the AI asked politely at a sensible moment — that record becomes a lead. Flip on email alerts and the same details arrive in your inbox the moment the conversation wraps. Because the lead comes with the full chat transcript, follow-up stops being a cold email and becomes a reply to an actual conversation. Sales teams tend to close these faster than generic form-fill leads, which is exactly why chat-captured leads are worth the plugin install.

Personalisation for logged-in visitors is handled without the plugin needing elevated access to your CMS database. On Standard and Pro plans, the plugin exposes a window.Asyntai.userContext hook. Your theme or template fills that object with whatever you want the AI to know about the logged-in user — name, plan, last order, roles, membership expiry — and the AI uses the context to tailor replies. A WooCommerce shopper asking about their latest order can be answered specifically. A Moodle student asking about their current course progress can be answered specifically. An Odoo customer asking about an open ticket can be answered specifically. The plugin itself stays narrow; the personalisation layer sits in your own code where you already control what data flows out.

Analytics become a quiet editorial engine once the chatbot has been running for a while. Every question is stored, grouped, and counted. Weeks into the install, patterns surface: the five recurring objections that keep appearing before a purchase, the documentation pages that can't cope with what visitors actually want to know, the product category that raises more questions than the rest combined, the feature that reliably confuses newcomers. Each of those is a prompt to fix the underlying content — rewrite a page, add a section, clarify a policy — and a few months later the chatbot is handling fewer repeats because the site itself got better. The plugin pays off twice: once by answering each visitor, and a second time by making your content sharper over the course of a quarter.

Pricing is kept simple so the decision to install the plugin isn't gated by a quote. A free plan covers up to a hundred messages a month, which is enough for a personal blog or a tiny services site to judge whether the chatbot is useful. From there, the Starter plan at thirty-nine dollars a month covers 2,500 messages and two sites — a comfortable fit for most SMB sites. Standard and Pro scale message volumes and site allowances upward for agencies and larger operators. Usage is tracked, warnings go out before any limit bites, and upgrades happen without touching the plugin itself. The install doesn't need to be redone when a plan changes; the plugin keeps running, only the dashboard numbers move.

Putting the pieces together: a chatbot plugin is only useful if it fits the platform it runs on, learns from the content it finds there, speaks the languages your visitors actually use, and turns the conversations it has into leads and insight. Asyntai ships that combination as a native package across more than thirty platforms, and as a universal snippet for everything else. Wherever your site lives — behind a WordPress admin, a Magento back office, a Shopify store, a Drupal module manager, a Strapi panel, a Ghost dashboard, a Sanity Studio, a Contentful space, or a bespoke stack of your own — the install path is short, the training is automatic, and the chatbot that ends up on your site talks like it belongs there.