M cenaly.com

Task · the whole bundle is free

Collect inquiries without replacing your site

The forms are already on the site, nobody is going to rewrite them, and meanwhile requests get lost in an inbox — a familiar story. This bundle does not rebuild anything: chat is added with one line, the existing forms start copying their requests into your back office, and a callback covers the people who would rather talk.

  • Your forms stay yours: we neither replace nor delay them
  • A chat question arrives as its own channel in the team chat
  • Requests from forms and calls sit in one list with a source passport
  • No fee per operator, per seat or per conversation

No card. A minute to sign up, another one for the tag.

Inquiries without replacing the site
  • Website chat
  • Site form capture
  • Callback
One tag for every widget8 of 12 widgets are freeShadow DOM — your layout stays intactRequests land in your own back officeTwo clouds: AWS and Russia
per operator, seat and conversation — we count neither staff nor threads
$0
form-capture rules per venue — one rule per form
10
leave the page: name, phone and e-mail, and nothing else
3 fields
languages of built-in chat labels — it reads the language of your page
45

What the guest sees

The guest notices no «integration» at all — the site behaves as before.

  1. 1

    Writes in chat or submits your form

    The chat bubble opens without registration or e-mail. And the familiar «send a request» form works exactly as it did: same button, same validation, same page afterwards.

  2. 2

    Waits for nothing extra

    We do not intercept or delay the submit, add no validation of our own, and do not read what is typed before «Send» is pressed.

  3. 3

    Or leaves a number

    The callback button: the guest picks «now» or «at a convenient time» and sees the outcome the server named — with an hour in digits, not «we will call you soon».

  4. 4

    Comes back to the conversation

    Returning the next day from the same tab, they find the thread and their contact in place. A sent callback request is not lost either: closing the window does not cancel it, and the widget says so plainly.

What happens on your side

Three channels, one back office — no «info@» mailbox, no spreadsheet.

Conversations live in the team chat

The guest chat opens as its own channel where the shift already talks: a «waiting for the guest» queue, «👤 Take it», and visible signals of who is looking at the thread and who is typing.

Team chat →

Requests go to «Requests»

Site forms arrive as a «Site forms: <rule label>» group, callbacks as their own group. Every request carries a source passport: page, ad, device.

Requests →

A request from your form is labelled honestly

We see the «Send» press, not the fate of the data on your backend — and we write that in the request itself instead of passing it off as confirmed.

Requests →

The dashboard shows the flow

Website widgets are a separate chart source: how many inquiries and where from, next to orders and calls.

Dashboard →

What to switch on

Three free parts: one adds a channel, one picks up what you already have, one covers the phone people.

Free

Website chat

A channel the site did not have

A bubble and a window in Shadow DOM, so your styles stay intact. Your team answers from the team chat — on a computer and on a phone, with no per-seat fee. When you are ready, switch on the AI assistant that answers from your knowledge base and hands the conversation to a human. The window can also carry a «Help» tab with your articles.

Widget page →
Free

Site form capture

Picks up requests from the forms you already have

A rule is a form selector plus field mapping (name, phone, e-mail) and optional page masks. Up to 10 rules per venue. The native submit is untouched, a form that fails its own validation creates no request, and a repeat within 10 minutes yields one request rather than two. The selector is verified by a button right in the admin panel.

Read the docs →
Free

Callback

For those who call instead of typing

The server names the outcome: dialling now, trying again at a named hour, queueing for the morning, or accepting a request. There is anti-spam, page masks, a schedule tied to opening hours, and a full source passport for the lead.

Widget page →

All 12 widgets →

What you do once

1

Create a free account

A Cenaly.com account and your website domain in the «My website» section. The site stays yours — we do not move or copy it.

2

Paste one tag

One line before </body>: into your WordPress theme, the HTML block on Tilda or Wix, theme.liquid on Shopify. The tag is shared by all widgets — you will not touch the code again.

3

Switch on the widgets you need

Every widget is a toggle with its own settings. Changes reach the site without a developer; the CDN cache is five minutes.

The tag itself

<script src="https://cdn.cenaly.com/site/v1.js" data-domain="your-site.com" async></script>

One tag for every widget. `data-domain` is your site, everything else lives in the admin panel.

How it plays out in different businesses

Services and agencies

The «send a request» form on the site is already there and is not going anywhere — now its requests are mirrored into the back office with their source and ad tag, while chat handles questions before they become requests.

Salon and beauty

«Is there a slot on Saturday?» becomes a chat message rather than a call in the middle of a shift. The booking itself belongs to the neighbouring task about free slots.

Retail

Questions about stock, sizes and delivery arrive in one list; the callback picks up whoever wants to check by voice.

Food service

Private events, allergens, delivery: chat answers in text, the callback answers by voice, and the whole shift sees both — not one manager in a personal inbox.

What this bundle does not do

  • Capture works only with your own forms on your own site, and exactly three fields leave the page — name, phone, e-mail — plus the page URL without parameters.
  • We see the submit, not its fate on your backend: the request is labelled «success on the site side is not confirmed».
  • The selector check in the admin panel parses HTML without a browser — a form drawn by JavaScript it will not see, although capture in the guest’s browser will. The panel says so outright.
  • The forms of our own widgets are never listened to, so a lead is not duplicated.
  • Chat is answered by people by default: the AI assistant is switched on separately and answers from your knowledge base.
  • The language pack translates the chat window labels, but not the conversation, not the AI answers and not the knowledge base articles.
  • We do not claim WCAG conformance across the whole widget family: the chat’s main text path and the callback form are the parts that were worked through.

What the bundle costs

The whole bundle is free: chat, form capture and the callback.

  • Chat is free: no per-seat fee and no cap on conversations.
  • Form capture is free — it has no extension card at all.
  • The callback is free, with no «successful call» fee.
  • We do not charge per visitor, per widget view or per request; call minutes are billed by your carrier.

Questions and answers

Do I have to rebuild the form on my site?

No. The rule attaches to the form that is already there: you point at its selector and say which fields are the name, the phone and the e-mail.

Can capture break the form submit?

The native submit is untouched — no cancelling, no delay, no validation of ours. A form that fails its own check creates no request.

What exactly reaches the back office?

Name, phone, e-mail and the page URL without parameters or hash. What is typed before the submit is never read, and the other fields never leave the page.

How many people can answer in chat?

As many as you need: there is no per-seat fee. The conversation arrives as its own channel in the team chat and any employee with access can reply — from a phone as well.

What if a request is sent twice?

A resubmit, a retry and «back → send again» within 10 minutes produce one request: the key is computed by the server.

Is telephony required?

No. Without it the callback stays a request with an honest wording; with an outgoing channel connected the PBX dials right away.

Do I have to rebuild my website?

No. The widgets live on your site: one tag before `</body>`, and everything else is toggles in the admin panel. Your layout, hosting and domain stay as they are.

Will this slow the site down?

The loader is one small `async` script and never blocks rendering. Only the widgets you enabled are downloaded, and the heavy parts wait for the visitor: the back-in-stock form weighs 13.7 KB and loads after the click, while the page carries an 889-byte launcher until then.

Will a widget break my layout?

No. Widgets render inside Shadow DOM: your site styles do not reach them, their styles do not leak out.

Where is the data stored?

In the cloud your account lives in: cenaly.com — AWS, cenaly.ru — Yandex Cloud in Russia. Requests, conversations, reservations and appointments never leave the brand perimeter.

Platform-by-platform installation, settings and troubleshooting are in the docs. Setup guide in the docs →

Gather your inquiries in one place and leave the site alone

Chat, your forms and a callback — one tag, one back office.

Start free

No card. The whole bundle is free.