Add-on · articles from the admin
A “?” button in the corner opens a side panel with your articles: delivery, returns, how to book, how to pay. Search, categories and a “was this helpful” vote — without leaving the page. For shops and service sites where the same things are asked every day.
Registration is free and needs no card · the help centre is a paid add-on you switch on in the catalogue · article edits reach your site in 5 minutes
The button sits in the corner of the page, and it can become a pill with your own label — “Help” or “How it works”.
The page stays where it is: the answer appears next to what the question was about, and no cart or half-filled form is lost.
Search runs across your articles — titles, categories, descriptions and body text — rather than the whole internet.
They leave a “helpful / not helpful” vote and close the panel with ✕ or Esc, back to the page. The vote goes into your report.
A free Cenaly.com account and your site domain in the "My website" section.
One line before </body> — in your theme, in a Tilda or Wix HTML block, in Shopify's theme.liquid. It serves every widget.
Each widget is a toggle and a settings form. Changes reach your site without touching code; CDN cache is five minutes.
The tag
<script src="https://cdn.cenaly.com/site/v1.js" data-domain="your-site.com" async></script> One tag for all widgets. `data-domain` is your site; everything else lives in the admin.
The answer opens as a side panel over your site rather than a jump to another section, and it loads only on the first tap, so nothing is fetched before that. Best for shops where leaving a page means an abandoned cart.
The “Articles and pages” section in the admin: categories, a section editor, autosaved drafts. On the site the article updates itself — no code involved. Best for anyone whose FAQ hasn’t changed since launch.
The AI writer produces a draft from a description, and the translations panel renders it in your site languages — a whole section or a single field. Best for small teams with no dedicated editor.
A knowledge base document is published as a help article in one action and unpublished the same way — the visitor sees no difference and you don’t write the same text twice. Best where instructions already exist for staff.
Search covers titles, categories, descriptions and body text, with up to 20,000 characters of an article indexed. Results come from your help centre only, never from the open web. Best for sites with dozens of delivery, return and payment rules.
The “Analytics” tab of the Knowledge base section shows article views, visitor search queries with the number of results found, and the “was this helpful” votes. A query with zero results is a gap in your help centre, named out loud. The events are anonymous: no identifiers, no cookies. Best for anyone extending a help centre on facts rather than guesses.
Visitors find the times, zones and return terms themselves — right on the product page, without abandoning the cart.
For salons and clinics: how late you can cancel, what happens if you are late, whether a deposit is needed.
Payment methods, receipts, invoices for companies — right where the order is being placed.
Holiday hours are edited in the admin and, once published, appear in the panel without touching the site.
An article goes out in the languages you have enabled, and AI translation helps prepare the versions you are missing.
The same text is available as a help centre page — handy to link from emails and social posts.
Colour, position and labels adapt to your site. The widget lives in a Shadow DOM — your styles don't break it, and it doesn't break yours.
On desktop
On mobile
Exact menu names and plan requirements, taken from each platform’s own help center.
Sites built with our website builder ship with the widgets already wired — nothing to paste.
Step-by-step guides per platform — in the help center →$19/mo
| Without the widget | With the widget | |
|---|---|---|
| Where visitors look | ✕ The same question arrives in chat, by email and by phone | ✓ The answer opens as a panel on the page where the question came up |
| Who updates the text | ✕ The FAQ page is edited by whoever has access to the markup | ✓ Articles are edited in the admin and update themselves on the site |
| Languages | ✕ Language versions of the rules have to be assembled and published separately | ✓ Articles go out in the languages you enable, with AI translation for the missing versions |
| Feedback | ✕ You judge your answers by the support queue — what people actually searched for stays unknown | ✓ The report shows article votes and the queries that returned nothing |
| Load on the team | ✕ The team repeats the same rules in circles | ✓ Repeat questions are closed by the visitor before anyone contacts support |
A help centre is your own answer articles, available to the visitor right on the site: not an FAQ page that opens somewhere else and never gets updated, but a panel that appears next to the place the question came from.
You need one when the same questions arrive every day: delivery times, return terms, how to move an appointment, whether you take cards. Those messages bring no revenue, occupy a person, and the visitor still waits longer than they are willing to.
Here the articles live in the admin next to your menu, appointments and orders: any staff member with access can write and edit them, AI helps with drafts and translations, and an internal knowledge base document is published as a help article in one action. The help centre also tells you what to add: the “Analytics” tab of the Knowledge base section shows which articles are read, what people searched for, and which queries returned nothing at all.
A help centre is pointless if you have two questions and the pricing page already answers them: the panel earns its place where answers accumulate and change. It is also not a replacement for chat — the help centre answers with ready text, without a human, and only about what you have already written; chat is for the personal or the urgent. They work best as a pair: the visitor looks for the answer first and steps into chat from the panel when they don't find it.
The “Help centre” add-on is $19 a month or $190 a year — paying yearly means 10 months instead of 12. The number of articles, languages and views is never metered.
In the admin, under “Articles and pages”: categories, a section editor, translations and an AI draft. Once published, the article appears on three surfaces at once: the panel on your site, the help centre page, and the “Help” tab inside our guest chat widget.
Yes, a knowledge base document is published as a help page in one action and unpublished the same way — to the visitor it is an ordinary article. You don’t write the same text twice for staff and for customers.
Visitors search your articles: titles, categories, descriptions and body text, with up to 20,000 characters of each article indexed. There is deliberately no web-wide search in the panel — visitors only ever see your own rules.
The panel will be empty — the widget invents nothing. Start with the questions already arriving in chat: delivery, payment, returns, opening hours. The AI writer can draft each of them.
On the “Analytics” tab of the Knowledge base section: article views, search queries with the number of results found, and the “was this helpful” votes. A query that returned nothing is a ready-made topic for your next article. These events carry no personal data about the visitor.
The shared “My website” tag plus the Help centre toggle — one tag powers all 12 widgets. WordPress — footer.php or a plugin, Tilda — HTML code in head, Shopify — theme.liquid, Webflow — Custom code. Changes arrive within 5 minutes.
The help bundle is about 21 KB gzipped — a button, a search box and the panel shell. The articles are not inside it: they live as a page on our domain and open in an embedded frame that is created only when the panel is first opened. A visitor who never touched the help centre downloads not a single article. Button and panel live in a Shadow DOM.
Yes, with a `window.CenalyHelp.open()` call from any link or button of yours — a “Help” item in the site menu, for instance.
One loader — about 26 KB gzipped, with the async attribute: it reads which widgets you switched on and pulls only those, as separate files. A widget you left off is never downloaded, and the weight of each one you did switch on is stated on its own page.
No. Widgets render inside a Shadow DOM: your site's CSS doesn't affect them and theirs doesn't leak out.
It reads your page's `<html lang>` or a `data-lang` attribute on the tag. Built-in labels are translated into 45 languages — the guest chat covers the same list; your own texts you write in the admin in the languages you need.
In the cloud your account lives in: cenaly.com — AWS, cenaly.ru — Yandex Cloud in Russia. Requests, conversations and bookings stay within the brand's contour.
More — installation per platform, settings and troubleshooting — in the help center. Installation guide →
Switch the add-on on — the “My website” tag is already there. The first articles are the questions you are asked every day anyway, and AI will draft them.
Start for freeArticles and languages never metered · yearly = 10 months instead of 12 · the search report is included