Add-on · articles from the admin
A “?” button in the corner opens a panel with your articles: delivery, returns, how to book, how to pay. Search, categories and a “was this helpful” vote. For teams that answer the same three questions every day.
No card. A minute to sign up, another for the tag.
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.
The “helpful / not helpful” vote under the article tells you which answers to rewrite, instead of guessing what was unclear.
A free Cenaly.ru 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.ru/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 the frame is created only on first open, so nothing loads before the tap. 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 translates it into your site languages while keeping one tone of voice. Best for small teams with no dedicated editor.
A knowledge base document can be published as a help article — 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. Best for sites with dozens of delivery, return and payment rules.
“Helpful / not helpful” under each answer shows where the text fails. Esc and the ✕ close the panel, and its colour, corner and button label are configurable. Best for anyone reducing support load on purpose.
Visitors find the times, zones and return terms themselves — usually the bulk of incoming questions.
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 in a minute and appear in the panel without touching the site.
AI translations cover questions in the language the visitor is actually reading.
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 →Add-on, price in the catalogue
| 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 | ✕ Rules are translated by hand, and not into every language | ✓ AI translates articles into your site languages |
| Feedback | ✕ You can’t tell which answers failed the visitor | ✓ Every article shows a “helpful / not helpful” score |
| Load on the team | ✕ The team repeats the same rules in circles | ✓ Repeat questions are answered before anyone contacts you |
A help centre is your own answer articles, available to the visitor right on the site: not a “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 can be published as a help article. On the site all of that appears by itself — no template changes needed.
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 both in the site panel and on the help centre page.
Yes, a knowledge base document can be published as a help page — 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.
The panel will be empty — the widget invents nothing. Start with the three or four most common questions: delivery, payment, returns, opening hours. The AI writer can draft each of them.
Into your dashboard, next to the articles: you see which answers work and which to rewrite. The vote carries no personal data about the visitor.
The shared “My website” tag plus the Help centre toggle. WordPress — footer.php or a plugin, Tilda — HTML code in head, Shopify — theme.liquid, Webflow — Custom code.
Yes, with a `window.CenalyHelp.open()` call from any link or button of yours — a “Help” item in the site menu, for instance.
The loader is one small `async` script; widgets load as separate bundles and only the ones you switched on. Nothing blocks page rendering.
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; 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 tag is already there. The first articles take an evening, and AI will draft them.
Start for freeNo card required · articles and languages never metered · yearly = 10 months instead of 12