LEO Chat
LEO Chat — the agency's own chat-commerce product; channels: Telegram and a website widget
- Task
- Measure the two parts of our own product that we carry over to Viber: whether the engine answers only from the knowledge base, and whether the queue loses confirmed messages. The measurements were made in LEO Chat (Telegram and website).
- Solution
- An answer engine working from the store's knowledge base that hands anything unknown to an operator; a durable queue on NATS JetStream with deduplication and retries.
- Result
- 4 July 2026, on a benchmark set of 45 questions — 89.7% accurate answers and not one outside the knowledge base. 17 August 2026, under a load of 300 messages per second with the engine, NATS and Redis forcibly killed — 0 lost and 0 duplicated confirmed messages; a k6 test on a full local stack, not in production. These measurements were not made in Viber: the channel is built for the project and tested on it.