For online stores and company websites
It answers your site's visitors in their language. Prices and availability come only from your catalog, delivery and return terms from your pages. Complex questions are handed to a manager.
Assistant's knowledge
Refreshed on a schedule
How it works
The assistant takes its knowledge from what you already have: the catalog feed, your site's pages and your documents.
The domain and a catalog feed: Google Merchant XML, agentic.json or UCP. Delivery, return and FAQ pages are found via your sitemap.
A script before </body> — and the widget appears on your site. No modules: it suits a store on any engine and a company site without a catalog.
<script
src="https://cdn.[domain]/w.js"
data-site="pk_live_7Hq2…Xy9"
defer></script>The key works only on your domains
It answers from your data. Complex questions go to a manager: a contact form in the widget and an email request to you.
Can I return sneakers if I've already run in them?
Returns — 14 days with a receipt. A worn pair is for the manager: shall I pass your question on?
Features
The assistant relies only on your site's data. You see what it answered, where that came from and what it cost.
Prices, sizes and availability — from the catalog; terms — from your pages. If something is not in the data, the assistant says so.
English, Spanish, German or any other: the assistant replies in the language the visitor writes in. The greeting and the widget buttons use your site's languages.
A hard question or a request for a human — a contact form in the widget and an email request to you.
Which questions visitors ask, which products get shown and clicked, where the assistant lacked data.
Economy, Standard or Smart — a balance of price and quality. A daily credit limit keeps spending within plan.
One connection for everyone: a line of code on the site, no CMS modules and no engine changes. A store brings a standard feed, a company site brings pages and documents.
Security
Visitors write to the assistant about orders and leave contact details, so access to conversations is restricted and transparent.
Visitors' dialog texts are stored in the database only in encrypted form.
A visitor's contacts are hidden. Every view is recorded: who, when and in which dialog.
Your company's catalog, knowledge and dialogs are not available to other accounts on the platform.
| When | Who | Action | Dialog |
|---|---|---|---|
| 23.09 14:07 | o•••@demo-sport.example | Showed contacts | #4821 |
| 23.09 10:31 | m•••@demo-sport.example | Showed contacts | #4809 |
| 22.09 17:48 | o•••@demo-sport.example | Showed contacts | #4796 |
Pricing
Credits are bought in advance and spent on the assistant's answers. The spend depends on the model tier and is visible per answer.
500credits
10 000credits
55 000credits
120 000credits
Prices are preliminary. The cost per answer depends on the model tier: lower on “Economy”, higher on “Smart”. Packages are bought in the dashboard after connecting a site.
FAQ
Didn't find the answer? Write to us: [email]
No. Product cards are built only from the imported catalog. If a product or size is not in the data, the assistant says so and offers the manager.
Your site's address, a catalog feed (Google Merchant XML, agentic.json or UCP) and one line of code. Delivery, return and FAQ pages are found via the sitemap.
It depends on the model tier and the length of the conversation. The spend is visible in the dashboard per answer, and a daily limit protects from overruns.
Dialog texts are encrypted and every customer's data is isolated. A visitor's contacts open with a separate action, which is written to the log.
One line of code, a catalog import from your feed and 500 credits to try. No card and no changes to your store.