The web widget is the same agent that answers you in chat and in Telegram, but on your website: a bubble button in the corner of the page opening a chat panel. The visitor needs no account — they just write.
The widget renders inside a Shadow DOM: its styles are isolated from your site and your site styles do not leak into the widget. It can go on any site — a website builder, a CMS or hand-written HTML: all you need is the ability to insert one script tag.
The widget needs no separate behaviour setup: it uses the same personality, the same knowledge base and the same brain as the private chat, Telegram and the public page. Change a rule once and it changes everywhere.
Visitor conversations are kept per browser session, so a returning visitor continues the conversation instead of starting over.
The agent can capture leads: when a visitor leaves their contact, the request reaches the owner — as a push notification and as a signed webhook into your CRM. A hard case is escalated to a human instead of being invented away.
Just the ability to insert one script tag into the page HTML. Enable the widget on the “Widget” tab in the agent settings, copy the snippet and paste it before the closing body tag — the chat appears in the corner of your site.
No. It lives in a Shadow DOM: the widget styles do not affect the page and the page styles do not affect the widget. That is why it can be dropped onto third-party templates and website builders without touching their CSS.
No. A site visitor is an anonymous interlocutor: no account, no Corpis interface. Their conversation is tied to the browser session, while you see the conversations and the leads in your account.
Yes, there is an allowlist of domains: if someone copies your widget key, it will not start on their domain. The key is public by nature (it sits in the HTML), so the domain list is the main protection against foreign use.