How to install the shop demo from Shared library
Status: the main flow for version 1.3.2 has been verified locally on a fresh copy. All 4 components were installed, and a new visitor received AI answers from the transferred knowledge base. The follow-up retained the exchange context and the 14-day limit. The customer and operator exchanged text and PNG files in the same widget. After closure, AI answered a new delivery question. Confirm availability on your instance with the demo owner.
The “Магазин Рух Онлайн” 1.3.2 template contains 12 fictional products, 6 knowledge base sections, and 2 histories with PNG/PDF files. The author prepares a .c1pkg from a verified synthetic template and adds the agreed version to the catalog once. You do not need to create data manually. Orders are simulated; no real payments, deliveries, or refunds are made.
Before you start
- You have a separate demo environment, configuration permissions, and the “Магазин Рух Онлайн” 1.3.2 card in Shared catalog.
- The environment owner has prepared an available AI model and knowledge base processing for real answers.
- You have a valid operator account. Historical operators in the package cannot sign in.
- You have your copy's name, demo date, history and live widget links, and a unique topic Alias for your copy.
Before launch, the demo owner must confirm that all 4 parts are ready: package, AI and knowledge base, operator, and widget.
Install and check the shop
- Open Menu → Shared library → Shared catalog, select the “Магазин Рух Онлайн” card and version 1.3.2. If the catalog is unavailable or the card is missing, contact the demo owner.
- Click Audit and review all 4 components: scenario, consultant, knowledge base, and demo data. Select New for your own copy and click Install. Continue only when all 4 components are installed or your own dependencies have been reused successfully. A failed or missing component blocks launch. If names conflict or installation is blocked, ask the author for a separate copy; do not overwrite an existing shop.
- Before starting a new conversation, open the supplied histories T1 and T3: each should contain 9 messages, including 1 attachment. Open the PNG and PDF. In statistics, select only the installed bot. Set the period from 29 days before the demo date through that date. Expect 7 conversations — 5 tickets and 2 chats.
- Open Menu → Fast Line Pro → Agents → “shop name — Консультант”. Check the automatically transferred model and the installed “shop name — База знань” under Context. Wait for indexing to finish. A prepared compatible package already publishes the consultant settings during installation. If the model is missing or unavailable in this environment, choose an agreed available model. Then click Publish. If no compatible model is available or the knowledge base is not ready, contact the environment owner.
- In Menu → Operator Panel → Settings → Subjects, open the installed “shop name — Повернення” topic and paste the supplied value into Unique identity. (Alias). In Constructor, open the installed bot → Constants and set
shop_support_aliasto exactly the same value. Save both changes. Do not copy an Alias from another shop. - In Operator Panel settings, open Skill groups → “shop name — Підтримка”. Check the topic from the previous step and add the valid operator. After the topic and group are activated, the operator must sign in or reload the panel page. This refreshes the available topics. They must then switch to Online, allow incoming widget chats, and have a free slot for a new conversation.
- Open the supplied live widget for this bot in a new customer session. Ask “Я замовила кросівки, але розмір не підійшов. Як їх обміняти?” (I ordered trainers, but the size is wrong. How can I exchange them?). Then ask “А протягом скількох днів?” (Within how many days?). Check the answer against the installed knowledge base. It must include “Для demo-обміну додайте фото етикетки.” (Add a label photo for the demo exchange) and the 14-day limit. The follow-up must retain the exchange context. The scenario editor test does not replace this check.
- In the same widget, send “Хочу поговорити з оператором” (I want to speak to an operator). The operator must accept the correct shop's conversation, see the earlier messages, and reply. Check the reply in the same widget; after acceptance, send a PNG from the customer and from the operator. Open both files. Close the conversation and ask a new question: it should start a new exchange rather than go into the closed chat.
Shop content and the names of installed components remain Ukrainian in both interface languages.
Check the result
Success means AI answers from the installed knowledge base and the operator replies to the customer in the same widget. Installation alone does not confirm this. If AI is unavailable, check “Оператор” (Operator) and tell the environment owner.
Historical messages retain their dates and are not sent to channels again. New test conversations change the statistics, so check 7/5/2 beforehand.
If you received a file instead of a card
In Shared library → Import, select the supplied .c1pkg, click Add to local catalog, then audit and install from step 2. This is a separate package transfer route: it does not confirm that the shop is available in Shared catalog.