Chota Agents at AI ATOM GLOBAL EXPO: the workflow behind the demo

On 16 October we presented Chota Agents during the first day of AI ATOM GLOBAL EXPO at BelExpo in Minsk. We spoke with prospective customers, met existing clients and gave interviews. The photograph shows the Chota stand and the product we brought to the forum.

A business workflow often starts with an ordinary request: explain a service, accept an enquiry or arrange a callback. Staff then need the details and a clear next step. Chota Agents connects company knowledge, a conversation in a configured channel and a saved result.

The company defines the agent’s role and task, then supplies reference material such as services, prices, operating rules and frequently asked questions. Instructions describe how to handle the conversation; the materials provide the facts needed to answer it.

Define limits before launch: which questions the agent may answer, which details it should collect and when automation should stop. Missing information must not become an invented commercial promise. Test routine questions alongside cases the materials cannot answer.

Text channels include Telegram and a website widget. Choose the channel required for your workflow and check the agent against your own questions. Having one working channel does not establish that every other channel is connected.

Voice launches as a team-assisted pilot. We agree the scenario, configure the number and test calls with you. The acceptance question is whether the call leaves the right outcome, rather than whether the demonstration sounds convincing.

In the product demonstration, a caller asks to be contacted after 17:00. The agent clarifies the request, and the application retains a transcript, an outcome and a task for staff. This is an illustrative workflow, not a case study disclosing a particular customer.

Staff can see the request and the requested timing. A saved callback request is not a completed outbound call. If your workflow needs an outbound call, notification or transfer, both the connection and the actual result need separate verification.

A company may need the outcome delivered into its CRM or another system. That requires an agreement on fields, access and permitted actions: creating an enquiry, updating details or passing context to staff.

A model’s statement is not confirmation that the CRM accepted a write. The workflow needs the downstream result and an explicit failure path. We configure and accept integrations separately from the basic conversation; the available actions depend on the particular connection.

Choose one recurring task and prepare current business material. Include normal questions and difficult cases: a corrected time, an unknown service and a request for a person. Define what should remain after each conversation before comparing outcomes.

This evaluates the whole process, including the work left for staff. You can start with sanitised examples and a description of your existing systems rather than sharing a full customer database. Subscription, voice usage, telephony and specialised integration costs are separate items to clarify before connection.

AI ATOM GLOBAL EXPO continues on 17 and 18 October. Visit the Chota stand or contact us to discuss your workflow. The sources above link to the product, our day-one report and ONT’s video coverage of developers at the forum.

During day one we gave interviews and met both new companies and existing clients. We keep client identities and private terms out of this story. ONT’s item covers the forum as a whole; exhibiting at an event is not an independent product-quality assessment.