Title: Alynivo – Live Chat & AI Chatbot for Customer Support Author: ogenco Published: 20 Jolay 2026 Last modified: 30 Aogositra 2026 --- Search plugins ![](https://ps.w.org/alynivo/assets/banner-772x250.png?rev=3622471) ![](https://ps.w.org/alynivo/assets/icon-256x256.png?rev=3615477) # Alynivo – Live Chat & AI Chatbot for Customer Support By [ogenco](https://profiles.wordpress.org/genco87/) [Download](https://downloads.wordpress.org/plugin/alynivo.0.22.40.zip) * [Details](https://mg.wordpress.org/plugins/alynivo/#description) * [Reviews](https://mg.wordpress.org/plugins/alynivo/#reviews) * [Installation](https://mg.wordpress.org/plugins/alynivo/#installation) * [Development](https://mg.wordpress.org/plugins/alynivo/#developers) [Support](https://wordpress.org/support/plugin/alynivo/) ## Description **Alynivo is live chat and AI chatbots for WordPress customer support** — answer visitors automatically, then hand over to a real person in the same chat when it matters. Engage website visitors, handle customer enquiries around the clock, and on WooCommerce guide shoppers from category and budget to a matching product. When a conversation needs a human, your team takes over without the visitor starting again. Everything lands in **one shared inbox**: browser, phone (mobile web app), and wp-admin. Think of it as a small **helpdesk** built into WordPress: the assistant answers first, and when it cannot, there is a clean **handover** to a person in the same window. Anything stored is **EU hosted** — on a server in Germany, never outside the EU. The free core plugin works entirely inside WordPress and does **not** send visitor or catalog data to any external service. Optional managed AI and Live Chat are paid add-ons when you want natural-language answers and human takeover. #### 🚀 Why teams choose Alynivo * ✅ Answers around the clock — and never a fake “agent online” when nobody is there * ✅ AI answers first, seamless takeover by your team in the same window * ✅ Shared inbox for browser, phone, and WordPress admin * ✅ Guided product selling for WooCommerce (category budget add to cart) * ✅ Works on any WordPress site — shops and service sites * ✅ GDPR-aware by design: the free core keeps funnel analytics on your own server * ✅ Customer support conversations stored in Germany, with short and controllable retention #### 🧠 It knows your website, not just its name Two things save you from typing your whole business into a settings screen. * **A first draft on setup.** When you install Alynivo, it reads your home page and your services page once and fills the knowledge fields with a suggestion. You see it before it is used, you change what does not fit, and nothing is saved until you finish the setup. Fields you have already written stay untouched — the draft only ever fills what is empty. Prices are deliberately left out: pages often carry outdated ones, and an assistant repeating them sounds confident and is wrong. * **The page in front of the visitor.** With every question, up to 1,200 characters of the page the visitor is currently reading go to the assistant. Someone standing on your services page asking “what does that mean exactly?” gets an answer about that page, not about your site in general. Nothing is stored, it is always current because it is the live page, and your own answers always outrank it. Switchable off in one click. #### 💬 Live Chat & human takeover Turn the widget into a real support channel without changing tools mid-conversation. * Watch the AI reply, then join the thread yourself * Proactive outreach: a fixed opening message after a visitor stays on a page, then a normal conversation * An honest offline path: when nobody is attending, the assistant says so and asks for an email address instead of promising a reply * Internal notes and file attachments on a conversation * Page context for agents (optional, consent-aware) Live Chat is an **optional paid add-on** and stays off until you enable it. #### 🧠 Answers that work without an account * Your own questions and answers, matched right in the visitor’s browser — no AI, no cost, included in the free version * Visitors can leave an enquiry (name, e-mail, message) when the assistant cannot help; it arrives by e-mail from your own site * Deterministic answers for delivery, payment, and security out of the box * Optional managed AI for natural free-text answers about your business * Knowledge context + persona/tone per site * Clear AI disclosure in the widget when managed AI is active #### 🛒 Built for WooCommerce (and fine without it) * Uses your published products and categories * Budget-aware recommendations and direct add-to-cart for simple products * Store / Service / Both modes — Service mode for agencies and non-shop sites * Granular page visibility (homepage, shop, product, cart, checkout, account, blog,…) * Per-product teaser bubble override from the product edit screen #### 📥 One inbox everywhere * Browser Agent App at [app.alynivo.de](https://app.alynivo.de) * WordPress admin Agent Inbox (linked personal agent login — site credentials never open chats) * Works on your phone: the Agent App is a mobile web app you can add to your home screen * Team roles, site access, and EN/DE interface #### 🎨 Widget that matches your brand * Custom title, welcome text, color, and position; own white-label logo with Starter or Pro * Proactive teaser bubble + launcher style (brand-first or neutral icon) * Responsive, keyboard-accessible chat UI * Built-in translations for DE, EN, FR, TR, IT, ES — plus per-language overrides #### 🔒 Privacy and GDPR by design * Free core: no visitor/catalog data leaves your WordPress site * Local funnel analytics only (pseudonymous session hash, no raw IPs) * Live Chat conversations stored in Germany; default **30-day** retention (7 or 14 days available) * Unsent draft text is never transmitted * Push notifications stay generic — never include message content #### 💶 What is free and what costs money The plugin itself is free and stays free — widget, guided selling, funnel analytics, all languages. * **Free** — your own questions & answers, enquiry form, guided selling, analytics, no account needed * **Starter (19 €/month)** — managed AI answers in natural language and your own white-label logo * **Pro (39 €/month)** — everything plus Live Chat, shared inbox, and human takeover Flat monthly price, not per agent — invite as many colleagues as you like. Prices and details at [alynivo.de](https://alynivo.de). ### Privacy Statement Alynivo does not transmit visitor or catalog data to Alynivo or any third-party service by default. The plugin stores the following data locally in your WordPress database, in a table it creates on activation: * Funnel events (for example: planner started, platform chosen, plan viewed, plan chosen, added to cart) with a timestamp and the associated product/category identifiers. * A daily-rotating pseudonymous session hash used only to estimate unique visitors for the funnel summary. Raw visitor IP addresses are never stored in the Alynivo events table. This data stays on your own site and is automatically deleted after 90 days. It is also removed when the plugin is uninstalled. If you enable the optional managed AI extension, the widget clearly identifies itself as an AI assistant and links to the site’s WordPress privacy-policy page. The current message, a short conversation window, the language, the title and type of the page, up to 1,200 characters of that page’s visible text, and any configured knowledge and persona context are sent to the disclosed AI provider through Alynivo’s server-side proxy; no provider API keys are ever exposed to the visitor’s browser. The page text is read from the page the visitor is already looking at, is never stored, and is sent only to answer the current question. Without Live Chat the managed service counts messages for your quota but does not store their content. With Live Chat enabled the messages are stored — see the next paragraph. Provider processing and retention are governed by the separately disclosed managed-service terms and subprocessor list. If you enable Live Chat, conversations are stored so your team can continue and review them. Storage is on a server in Germany, with a default retention of 30 days that you can shorten to 7 or 14 days. Stored data covers the messages themselves, internal notes your team writes, attachments sent in the conversation, and — only if a visitor consents — the title and path of the page they are on. Unsent text is never transmitted. Notifications to your team’s devices contain only a generic notice and opaque identifiers, never message content. When you deactivate the plugin, a short form asks why. It is entirely optional: nothing is collected in the background, and nothing leaves your site unless you press “Send and deactivate”. “Just deactivate” and the close button switch the plugin off without sending anything, and if JavaScript is unavailable the normal WordPress deactivate link is untouched. If you do send it, an e-mail goes from your own site to kontakt@alynivo.de containing only what you typed — the reason you picked, your optional note and your optional e-mail address — plus your site address, the plugin version and your WordPress version. It is used to fix problems, never for marketing, and the address can be changed with the `alynivo_deactivation_feedback_email` filter. ## Screenshots [⌊The chat on a website: a visitor asks in their own words, and the assistant answers from the business's own knowledge.⌉⌊The chat on a website: a visitor asks in their own words, and the assistant answers from the business's own knowledge.⌉[ The chat on a website: a visitor asks in their own words, and the assistant answers from the business’s own knowledge. [⌊On a phone the chat is a sheet, not a takeover — the page stays visible behind it, and it closes with a pull down, a tap above it, or the close button.⌉⌊On a phone the chat is a sheet, not a takeover — the page stays visible behind it, and it closes with a pull down, a tap above it, or the close button.⌉[ On a phone the chat is a sheet, not a takeover — the page stays visible behind it, and it closes with a pull down, a tap above it, or the close button. [⌊Guided setup — pick the kind of business and get suggested answers that fit it.⌉⌊ Guided setup — pick the kind of business and get suggested answers that fit it.⌉[ Guided setup — pick the kind of business and get suggested answers that fit it. [⌊Your own questions and answers, matched in the visitor's browser: no AI, no cost, works in the free version.⌉⌊Your own questions and answers, matched in the visitor's browser: no AI, no cost, works in the free version.⌉[ Your own questions and answers, matched in the visitor’s browser: no AI, no cost, works in the free version. [⌊Settings dashboard: status at a glance, a setup checklist, and chat statistics counted locally.⌉⌊Settings dashboard: status at a glance, a setup checklist, and chat statistics counted locally.⌉[ Settings dashboard: status at a glance, a setup checklist, and chat statistics counted locally. [⌊Design: assistant title, welcome message, logo and brand colour.⌉⌊Design: assistant title, welcome message, logo and brand colour.⌉[ Design: assistant title, welcome message, logo and brand colour. [⌊Agent inbox: conversations sorted into open, waiting, mine and closed, with your availability and how many requests came in today.⌉⌊Agent inbox: conversations sorted into open, waiting, mine and closed, with your availability and how many requests came in today.⌉[ Agent inbox: conversations sorted into open, waiting, mine and closed, with your availability and how many requests came in today. [⌊Team management for agents, roles, and site access.⌉⌊Team management for agents, roles, and site access.⌉[ Team management for agents, roles, and site access. [⌊Stored data: keep conversations 7, 14 or 30 days — shortening the period also shortens what is already stored.⌉⌊Stored data: keep conversations 7, 14 or 30 days— shortening the period also shortens what is already stored.⌉[ Stored data: keep conversations 7, 14 or 30 days — shortening the period also shortens what is already stored. ## Installation 1. Upload the `alynivo` folder to `/wp-content/plugins/` or install the ZIP through WordPress. 2. Activate Alynivo. 3. Go to **WooCommerce Alynivo** (shop) or the standalone **Alynivo** menu (any other WordPress site). 4. Finish the short setup wizard — or skip it and configure the full settings page. 5. Optional: connect Managed AI and/or Live Chat from your Alynivo account when you are ready. ## FAQ ### Does the chat still answer at night and at the weekend? Yes — but what it can answer depends on the plan, and the difference is worth knowing before you decide. The free version answers around the clock from the questions and answers you stored yourself. Those live in your own WordPress and know nothing about office hours. What it cannot do is handle a question you did not anticipate: there the visitor is offered a contact form instead. With Managed AI the assistant also answers free-text questions in natural language at three in the morning, grounded in your own business knowledge. A person only takes over when a person is there, and the widget says so plainly rather than showing an “agent online” dot to an empty room. ### What is Live Chat and do I need it? Live Chat lets a real person take over a conversation the AI started, in the same chat window. You see every conversation in one inbox — browser, phone, and wp-admin. It is optional: without it the widget keeps answering automatically. ### What is proactive outreach? An optional Live Chat setting that sends a fixed opening message on your own initiative once a visitor has stayed on a page (or the site) for a configured number of seconds— for example, “Questions about pricing? I’m here to help.” on your pricing page. No AI cost for that first message. If the visitor replies, the conversation continues exactly like any other Live conversation. Off by default. ### What happens when nobody from our team is available? Alynivo does not promise a person who is not there. While no agent is attending, the widget says so instead of showing a fake “agent online”, the assistant keeps answering, and it asks for an email address when a human reply is needed. ### Where are live chat conversations stored, and for how long? On a server in Germany, deleted automatically after 30 days by default. You can shorten that to 7 or 14 days, export a conversation, and delete any conversation at any time. Text a visitor types but never sends is never transmitted or stored. ### Does Live Chat work without WooCommerce? Yes. Guided product selling needs WooCommerce, but the chat, the takeover, and the inbox work on any WordPress site. ### Does Alynivo require an external AI account? No. The core plugin uses deterministic answers and works without any external account. A managed AI connection is available separately for sites that want natural-language answers. ### Does it support variable products? Variable products are linked to their product page so visitors can select attributes. Direct add-to-cart is limited to simple purchasable products. ### Is it compatible with custom pricing systems? Developers can adjust recommendation queries and product payloads with the documented Alynivo filters, or build a dedicated store adapter using the planner contract. ### Does Alynivo track or store visitor data? Alynivo records pseudonymous, aggregate funnel events (for example, “planner started” or “added to cart”) in your own WordPress database. No raw IP addresses are stored; sessions use a daily-rotating hash generated on your server. No data is sent to Alynivo or any third party by the core plugin. See Privacy below. ### Will it slow down my site? The widget script loads in the footer, so it does not block rendering of your page or delay your largest content element. You also control exactly which pages the widget appears on, so it is not loaded where you do not need it. ### How long does setup take? Install, activate, and the widget is live with sensible defaults. Choosing pages, tone, and welcome text takes a few minutes in one settings screen — no theme edits and no code. ### Which languages does the widget support? Built-in: German, English, French, Turkish, Italian, Spanish. You can override title, welcome, and teaser text per language in the settings. ## Reviews ![](https://secure.gravatar.com/avatar/9f57597810dc1d88851b21d7bd2700528bb29dbaa20fc815e8cbe82920199ab6? s=60&d=retro&r=g) ### 󠀁[Easy to setup](https://wordpress.org/support/topic/easy-to-setup-132/)󠁿 [instaki](https://profiles.wordpress.org/instaki/) 23 Aogositra 2026 Quick to set up and easy to use. [ Read all 1 review ](https://wordpress.org/support/plugin/alynivo/reviews/) ## Contributors & Developers “Alynivo – Live Chat & AI Chatbot for Customer Support” is open source software. The following people have contributed to this plugin. Contributors * [ ogenco ](https://profiles.wordpress.org/genco87/) “Alynivo – Live Chat & AI Chatbot for Customer Support” has been translated into 1 locale. Thank you to [the translators](https://translate.wordpress.org/projects/wp-plugins/alynivo/contributors) for their contributions. [Translate “Alynivo – Live Chat & AI Chatbot for Customer Support” into your language.](https://translate.wordpress.org/projects/wp-plugins/alynivo) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/alynivo/), check out the [SVN repository](https://plugins.svn.wordpress.org/alynivo/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/alynivo/) by [RSS](https://plugins.trac.wordpress.org/log/alynivo/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.22.40 * Setup now reads your home page and services page once and offers a first draft for the assistant’s knowledge, so you do not start with empty fields. It only ever fills what is empty, shows you the text before it is used, and saves nothing until you finish the setup. * Prices found on your pages are deliberately left out of that draft. Older releases are listed in changelog.txt, which ships with the plugin. #### 0.22.39 * The assistant can now read the page the visitor is looking at, so it answers about that page instead of only knowing its title. Up to 1,200 characters, never stored, and switchable off in the settings. * Fixes the keyboard focus ring, which sat at 1.5:1 contrast where 3:1 is required. * Screen readers now announce a new visitor message in the agent inbox. * Corrects the privacy statement: it claimed the managed service never stores message content, which is not true once Live Chat is on. #### 0.22.38 * The knowledge context and persona fields no longer use a monospace font; they hold prose, not code. * The overlap hint now only appears for topics that are genuinely hard to tell apart, instead of every pair sharing two words. #### 0.22.37 * The settings now point out which of your own topics are too similar to tell apart, naming the words they share. Overlapping topics are why the assistant sometimes has to ask back instead of answering, and until now nothing showed you that. #### 0.22.36 * With Managed AI active, a question that matches several of your own topics equally is now answered by the assistant instead of being met with a “which one do you mean?” menu. The free version keeps the menu, where there is nothing better to offer. #### 0.22.35 * The launcher now recognises on its own whether your logo carries its own background, and lets it fill the button instead of sitting inside a white ring. You can still override the decision either way. #### 0.22.34 * Adds a launcher background setting: automatic (unchanged), brand colour, white, or a colour of your own. * Adds a “logo fills the launcher” option for logos that carry their own background, so the mark no longer sits as a smaller tile inside a white button. * Gives the closed button a light edge instead of the soft shadow when its background is dark, where the shadow was invisible. #### 0.22.33 * Reworks the chat sheet on phones: the page stays visible behind a dimmed backdrop instead of a full-screen takeover, and a larger gap at the top makes clear the chat is a layer over the site. * Adds two more ways to close the chat on a phone — pull the sheet down by its handle, or tap the strip above it — alongside the existing close button. * Softens the close button so it no longer sits in a grey circle, while keeping its full touch target. * Stops a host theme’s section spacing from leaking into the chat panel, which left an empty white block above the header on themes that indent every section. * Keeps a deliberately disabled enquiry form disabled when the setup assistant is run again. #### 0.22.30 * Simplifies the Managed AI and Live Chat settings copy so site owners understand what each hosted feature does before enabling it. #### 0.22.29 * Fixes the self-service WordPress connection flow so the one-time code form never falls through to the raw WordPress settings screen. * Returns admins directly to the Managed AI & Live Chat screen after a connection attempt. #### 0.22.28 * Added a subtle setup restart action directly to the Alynivo dashboard setup card. #### 0.22.27 * Added branded HTML account activation e-mails with a clear clickable button while keeping the plain-text fallback. * Made the WordPress one-time connection code field visible directly in the Managed AI & Live Chat settings screen. * Removed duplicate single-site labels in the Agent Inbox header. #### 0.22.26 * Added self-service website pairing for Alynivo accounts: owners can create a website, generate a short-lived WordPress connection code, and pair the site without emailing permanent credentials. * Added the WordPress-side pairing flow for Starter and Pro connections. * Improved the Agent Inbox mobile reply composer with a shorter placeholder and more usable typing area. #### 0.22.25 * **The widget now appears in the shop even when Alynivo was activated before WooCommerce.** Activating wrote the page visibility into the database verbatim — including the four zeroes the default sets while WooCommerce is absent, and a stored value always beats a default. Anyone who tried the chat first and installed the shop afterwards had no widget on any shop, product, cart or checkout page, permanently, with the dashboard reporting “Live”. Activation no longer freezes those settings, and existing installations are corrected once — but only where the settings still look exactly as activation left them. * **The dashboard says “Not in the shop” instead of “Live”** when the widget is switched on but hidden on every shop page. #### 0.22.24 * **“C’è un umano?” now reaches a person.** The Italian for “is there a human?” was deliberately left out because it shares two words with “Sei un umano?” — “ are you a human?” — which asks the assistant about itself and deserves a different answer. The two are now told apart, so both get the right one. An explicit request still wins when a message contains both. #### 0.22.23 * **Your own topics can now be written in every widget language.** Until now only the frame around the click-through was translated: on a French page the heading said “En quoi puis-je vous aider ?” and the topic buttons under it stayed in the language you typed them in. Each topic now has an optional field per language, right underneath it. Leave a language empty and the original text is used; a language is only taken when both the question and the answer are filled in, because a translated question with an untranslated answer sends the visitor somewhere they cannot read. * **A mirrored reply now reaches the Inbox in the language the visitor saw.** The mirroring call runs through a REST request where a multilingual plugin often cannot tell which page the visitor was on, so the site looked the text up in its own language. The Inbox showed the German answer under the French question. * **A colleague who is suspended, or limited to fewer websites, loses their open live connection.** Removing someone already did this; changing their permissions did not, so their open tab kept receiving conversation headers it should no longer see. * **The route that mirrors your own answers can no longer be used to flood a conversation.** At most five assistant lines in a row; the longest real sequence is three. #### 0.22.22 * **A greeting is answered as a greeting again.** Site owners write their topics as full sentences, and “Hello, how do I book an appointment?” is a perfectly normal line. Anyone who then typed just “Hello” got the phone number from that topic instead of a welcome — on the most common opening message there is. * **The click-through no longer ends after an enquiry.** Sending the enquiry form left the visitor in front of an empty window: no topics, no “Show questions”. Asking for a person a second time did the same, because the form is offered only once per visit. Both now lead back into the menu. * **Typing mistakes find their answer again.** A fix against word mix-ups (“kosten”/“ konten”) also threw away the most common typo of all — a finger on the neighbouring key. Measured over 26 everyday business words, 52 of 383 mistyped spellings were still recognised; now 292 are, and both mix-ups stay apart. * **Asking for a human works in every widget language.** French, Italian, Spanish and Turkish knew two to four phrases each; over 43 real sentences, one of them matched. Now 42 do. Plain nouns like “customer service” no longer hijack a pricing question about that same thing. * **French no longer switches from “vous” to “tu” mid-conversation**, Turkish no longer switches from “sen” to “siz” in the enquiry form, and the Turkish greeting bubble asks about questions instead of asking whether something is broken. * **Nine interface texts that were missing from the translation catalogue** — among them the whole click-through — now have their German version. * **Bulk actions in the shared inbox only ever touch what is on screen.** With a search term active, selecting conversations and then deleting could remove ones the search had just hidden. * **The rate limit no longer lets a burst through** at the moment its counting window rolls over. #### 0.22.21 * **The “currently on the site” panel no longer eats half the screen on a phone.** With an empty conversation list it took 52 % of the height for three lines of text, squeezing the list into what was left. #### 0.22.20 * **The click-through menu now speaks every widget language.** On a French, Turkish, Italian or Spanish site the title, greeting and topic buttons were translated, but the six lines that carry the whole free tier were not: “What can I help you with?”, “More topics”, “Back”, “Something else”, “Show questions”. On the free plan that menu _is_ the interface. * **The Inbox inside wp-admin no longer freezes when it stays open.** WordPress renews its security token after a while; every request then failed silently and the stale list just sat there with no explanation. It now says what happened and offers a reload. * **The shared inbox is easier to scan and search.** A wider desktop list, conversation search across site, message, page and language, and clearer status pills put requests that need a reply first without inventing an unread state. * **The empty inbox now helps instead of repeating itself.** The main area shows open and waiting totals; the duplicate message in the context column is gone. * Workspace and website now read as one scope control, account destinations use clear chevrons, and the profile menu reliably covers conversation action buttons instead of letting their three dots shine through. * Login help and privacy text have stronger contrast in light and dark mode. The shared responsive Inbox improvements ship in both the browser Agent App and WordPress admin. #### 0.22.19 * **File names of attachments stay readable.** “mein foto.png” arrived as “mein20foto. png”, and anything with an umlaut turned into gibberish: the name was cleaned while still URL-encoded, which strips the percent signs. * **A damaged settings value no longer takes the whole website down.** If the stored options were ever anything other than an array — a broken serialisation, an import, a filter — every single request died with a fatal error, front end and wp-admin alike, with no way back except the database. * **Running the setup wizard a second time no longer resets where enquiries are sent.** The field always showed the WordPress admin address, and the wizard saves what the form contains — so a business that had pointed enquiries at sales@ got them sent back to the admin address, silently. #### 0.22.18 * **The assistant no longer answers the wrong question with full confidence.** Two rules that help the free tier when a visitor words things differently were treating unrelated German words as the same: “Versicherung” got the shipping answer, “Übersetzung” the bank details, “Bescheinigung” the complaints answer,“ Bestätigung” the order answer. Thirteen such mix-ups out of twenty word pairs tested. A shared prefix like _ver-_ or _an-_ no longer counts as a shared word stem — while “Öffnungszeiten”/”geöffnet”, the case the rule exists for, still matches. * **A typo is a slipped key, not a different word.** “kosten” and “konten” are one letter apart, so are “anmelden” and “abmelden” — and the pricing question was answered with the account details. Words of the same length that differ in the middle are no longer treated as typos. Forgotten letters, swapped neighbours and word endings (“kostet”/”kosten”) still match. #### 0.22.17 * **Saying “hi” no longer empties the chat.** Every message you send clears the topic buttons above it, and the friendly replies — “hi”, “thanks”, “ok”, “are you a bot?” — were the one path that did not bring them back. The most common opening line left the visitor with a greeting and nothing to click. The buttons now return after every one of them. * **An enquiry with a mistyped e-mail address is no longer lost.** “maria@gmail” without the ending was rejected by the server, but the widget showed “That did not work, please try again in a moment” — a fault message. People tried the same address again, got the same line and gave up. The form now says which field needs fixing, in all six languages, and it checks for a real address instead of just an “@” somewhere. * **Long AI answers reach the Inbox again.** Two separate faults kept them out: the proof of authorship was computed over a different text than the one sent back — any answer containing “<” or a link with an umlaut in it broke it — and the mirror rejected anything over 1000 characters while the service allows ten times that. Exactly the detailed answers an operator most needs to see. * Turkish, Greek, Cyrillic and emoji get the full message length. The limit counted bytes, so 600 Turkish characters were refused while 600 German ones went through. * “Please enter a shorter message” no longer appears for an _empty_ message. * Long live chats are no longer cut off. The request limit reset its own clock on every request, so a chat open for more than two and a half minutes stopped updating for a minute at a time. #### 0.22.16 * **A message about suicide did not reach a person.** The rule that pulls someone into the chat for a crisis only knew “umbringen” written as one word — but in German the verb splits, and the sentence people actually write is “Ich bringe mich um”. “I want to kill myself”, “Ich will nicht mehr leben” and every wording in the four other widget languages fell through as well. Measured against twenty- two real phrasings, the old rule caught three. All six languages are covered now, and twelve ordinary sentences containing “bringen” or “leben” still call nobody. * “How many employees do you have?” no longer calls an employee. The bare word was enough to trigger a handover, and since 0.22.13 that happens on the very first message — so an ordinary question notified the whole team. The same for phrases with words far apart: “How many staff do I need to run the chat?” matched“ staff chat” because the words were only required to appear in order, anywhere in the sentence. Now they have to be close together. While fixing it, a third bug surfaced: “I would like to chat with an employee” was not recognised at all. * **A link can no longer claim one address and lead to another.** An answer containing`[ alynivo.de](https://alynivo.de.attacker.example/login)` showed your domain and went somewhere else. The real domain is now named next to the link whenever the label claims a different one — the same rule every mail client uses. An honest label is left alone. * Long answers no longer stall the chat. A message packed with “@” characters took a third of a second per line to render, freezing the browser while it worked. Now it is immediate. * The Agent Inbox inside wp-admin shows AI answers the way the visitor sees them:** bold** where it says bold, links as links, paragraphs as paragraphs — instead of raw asterisks and brackets. * Line breaks in the chat window stay line breaks. A list of points used to collapse into one block of running text. #### 0.22.15 * Asking for a person is recognised far more reliably. The check only knew phrasings with a verb (“speak to an employee”), so “I would like an employee on the chat” fell through to your own answers — and on a site whose answers cover pricing, someone asking for help was handed a sales pitch. Measured against eleven real phrasings, nine were missed; now all of them are caught, and ten ordinary questions still call nobody. * The same request now also comes before your own answers on sites without Live Chat. There nobody can take over, but the reply is honest and leads to the enquiry form instead of selling something. #### 0.22.14 * The enquiry form is no longer a dead end. Once it was open there was no way back: closing and reopening the chat did not help, because the form stays where it is — the only way out was to actually hand over your contact details. There is now a “Back to the questions” button next to Send, and it brings the question menu back. * The setting for the question menu is in German again on German sites. Four new labels had been added in 0.22.11 without their translation. #### 0.22.13 * When a rule brings a person into the chat, the visitor is now told. Complaints and sensitive topics have always been able to pull someone in without the visitor asking — but it happened silently: an operator was waiting in the Inbox while the assistant kept talking, and the visitor never found out. That mattered most in exactly the case the rule exists for. * The line the assistant says about it reaches the Agent Inbox too, so your team reads what the visitor was promised. #### 0.22.12 * Everything from 0.22.11. The new self-check no longer reports the opening greeting as a missing answer: it is not a reply to anything, and at that point there is no conversation for it to be missing from. A warning that cries wolf on every visit is one nobody reads a week later. #### 0.22.11 * **A question menu for the free version.** The chat now opens with your own answers as buttons instead of an empty input box, so a visitor does not have to guess what it knows. It is fed entirely by the answers you already entered — there is no second list to maintain, and it works from the first minute without another setting. Visitors can still type freely at any time, and asking for a person always works. Six topics per page, and the menu comes back after every answer so nobody reaches a dead end. On by default; switch it off under Question menu. * **Common wording now finds your answers.** “When are you open?” reaches an entry stored as “Opening hours” — around twenty topic groups covering prices, hours, appointments, directions, delivery, payment, cancellation, warranty and more. A topic match never answers on its own, it only ever suggests, so a broad word costs an unnecessary button rather than a confidently wrong answer. * **Typos no longer cost the answer.** One edit from five characters, two from eight, and swapped neighbours count as one — “Presie” finds “Preise”. The first letter has to match, so “Preis” and “Kreis” never become neighbours. * All three only apply without Managed AI. With it, the model answers the question properly and in the visitor’s own language. #### 0.22.10 * Everything from 0.22.9, plus: without Managed AI, a question that nearly matches one of your own answers is now offered as a suggestion instead of being turned away. The free tier has nothing but your own answers, and a question phrased slightly differently used to end in “I cannot answer that reliably” while the right answer sat one wording away. A weak match still never answers on its own— a single short word would hit the wrong entry — it asks, and the visitor decides. With Managed AI nothing changes: the model answers the question properly, in the visitor’s own language. * If none of the suggestions fit, the enquiry form follows, so the conversation still has a way out. ## Meta * Version **0.22.40** * Last updated **18 ora ago** * Active installations **Fewer than 10** * WordPress version ** 6.4 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Languages * [English (US)](https://wordpress.org/plugins/alynivo/) sy [German](https://de.wordpress.org/plugins/alynivo/). * [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/alynivo) * Tags * [chatbot](https://mg.wordpress.org/plugins/tags/chatbot/)[helpdesk](https://mg.wordpress.org/plugins/tags/helpdesk/) [live chat](https://mg.wordpress.org/plugins/tags/live-chat/)[shared inbox](https://mg.wordpress.org/plugins/tags/shared-inbox/) [woocommerce](https://mg.wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://mg.wordpress.org/plugins/alynivo/advanced/) ## Ratings Kintana 5 amin'ny 5. * [ 1 5-star review ](https://wordpress.org/support/plugin/alynivo/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/alynivo/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/alynivo/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/alynivo/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/alynivo/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/alynivo/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/alynivo/reviews/) ## Contributors * [ ogenco ](https://profiles.wordpress.org/genco87/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/alynivo/)