Loading.
Loading.
The old address keeps working, so the chat on your site will not break. But the widget code holds the old address: once the address changes, take the new code in the wizard and replace the old one with it.
Another name under our domain
Latin letters, digits and a hyphen. We take it ourselves, about a minute.
Your own domain
A subdomain of your site, for example support.example.com. We show the records, you add them wherever the domain is managed.
AI chat has no operators, so the free model always answers after the cloud AI.
Your own provider and the backup search are set up in your panel: there are presets, the list of providers and the state of the search. AI, Providers
The bot answers from the knowledge base and nothing else. You fill it in your panel: files, links and your sitemap.xml.
Paste this code before the closing body tag on every page.
WordPress, Shopify, Tilda, Wix, Webflow: where to paste it
loading
A chat for employees inside Confluence. Paste the code in Confluence: General Configuration → Look and Feel → Custom HTML → At end of the BODY. Only signed-in employees see the chat, the login page does not show it. Only a Confluence system administrator can paste it, and the chat then appears on every page of the whole wiki. Custom HTML exists only in self-hosted Confluence (Data Center or Server), Confluence Cloud has none. If there is no such setting or the administrator says no, set up a Telegram bot with invite link only access and put the link in the sidebar of your space.
loading
We cannot check it from here: Confluence is behind a login. Open any Confluence page, the chat button appears in the bottom right corner.
The website already works. Telegram and email you add yourself in your own panel: those are your accounts, and we do not ask for access to them.
The panel emails your agents about conversations handed over to them, invitations and password resets. By default it uses your own mail, set up in the panel under Notifications. Or switch on the EPAV mailbox: it is included in every plan, there is nothing to set up, and it sends only to confirmed addresses.
Who receives emails
Untick an address to stop emails to your agents going there. Cabinet emails about payment and limits still go to your sign-up email. With your own mail the panel writes to agents directly: to stop them, leave the team or change your email in the panel.
We send a code to this address. Ask your colleague for it and enter it next to the address.
The bot can tell a customer the status of their order or book an appointment. Enter the keys of your store or calendar: we check them and add the action to your assistant. The keys are kept in your panel, encrypted. Before showing an order or booking, the bot asks the customer to confirm their email with a code. The code goes from your own mail set up in the panel or from the EPAV mailbox, card Emails to your agents.
In Shopify: Settings, Apps, Develop apps, Build apps in Dev Dashboard. Create an app with the read_orders scope, release it, install it on your store and copy its Client ID and Client secret. An app created in the store admin before 2026 gives an Admin API token instead: paste it in the first field and leave the secret empty.
In WordPress: WooCommerce, Settings, Advanced, REST API, Add key, permission Read. Copy the Consumer key and Consumer secret.
In Cal.com: Settings, Developer, API keys, Add. The event type: open it in Cal.com and copy the address from the browser, it ends with its number.
A conversation is one visitor's chat with the bot, about three bot replies on average: a long back-and-forth uses more, a quick question and answer uses less.