A first impression starts
with a reply at the right moment.

WhatsApp, Telegram, Instagram Direct and website chat. Capabilities vary: connection method, permissions, platform limits and follow-up messages are checked in advance. Start and Pro cover one channel; Ultra covers multiple channels, with the implementation scope agreed separately.

The assistant introduces itself honestly, then uses natural language and answers the actual question. It avoids long menus, repeating known information and forcing a phone number. A customer who wants a person should get help reaching your staff. We agree on the tone with you.

When the customer is ready for a next step, asks for a person or needs expert advice. The assistant asks how they prefer to connect and passes on the context. We test handoff and pause rules in each channel to prevent overlapping replies.

It supports the first stage; negotiation, individual terms and decisions stay with people. The goal is to reduce routine work and delays so your staff can focus on prepared enquiries. Start with one measurable part of the process.

Current company, product or service information, common questions and handoff rules, plus agreed access to the channel and systems. You don’t need a perfect complete database: start with one business area and expand after testing.

An agreed basic workflow usually takes around 1–2 weeks after we receive materials and access. Timing depends on integrations, data quality and approvals. We agree on milestones and acceptance criteria before work begins; real enquiries are connected after testing.

We first look for a way to fit your existing workflow. Options include amoCRM, Bitrix24 and other systems with a suitable API. Where appropriate, start by sending enquiries to an agreed internal channel. We check infrastructure capabilities and limitations before payment.

Start handles first replies, qualification and handoff. Pro adds matching from your catalogue and answers about selected options. Ultra covers multiple channels and higher volume. Plan limits are listed above; use the configurator to compare workflows.

Messaging platforms, AI, CRM, additional channels and custom integrations may incur external charges. Overage may also cost extra. We agree the full price, included services and overage notifications before launch.

The definition and counting period are agreed before launch, including returning customers, test enquiries and multiple channels. A plan’s dialogue allowance is not a count of individual messages.

It can converse in the customer’s language. We verify your required languages, terminology and answer quality using your materials before launch. Important enquiry details are saved in an agreed format for your staff. Try English in the demo on this page.

We can configure a polite follow-up based on context, timing and channel rules. Frequency and conditions are agreed in advance, and requests to stop must be respected. In the website demo, a reminder can appear while the visitor remains on the page.

Your workspace shows assistant status and the basic settings for your setup. You can pause AI and save changes. If you prefer not to manage it, we can do that for you. Live channel access and available controls are verified during implementation.

We use HTTPS, access checks for each company’s data, and limits on login attempts and requests. Passwords are stored as strong hashes rather than plain text, and two-factor authentication is available. Access is limited to authorised users and services needed to operate the system. These measures reduce risk but cannot guarantee absolute security: enable 2FA and use a unique password. Processing is described in the data policy.

Yes. Before launch, we define the current data source and who maintains it. A text adjustment and a new integration require different work: we explain what support includes and what needs a separate estimate. Workflow changes are tested before publication.

A backup AI model can handle a request with its conversation context if the primary model fails technically. Channel or CRM outages need separate handling. We agree on notifications, enquiry preservation and staff actions in advance.

We compare first-reply time, handled enquiries, qualification quality and handoffs. With enough volume, we can assess later CRM stages. We don’t credit every new sale to AI: your offer, traffic and staff also affect results.

Yes. The contract is with Evgeny Lazarev, a self-employed individual, Tax ID 524917142320. Before work starts, we agree the scope, stages, price, data-handling rules and acceptance criteria. A receipt is provided after payment. We correct failures in the agreed technical workflow; support and refund terms are set out in the contract. We do not promise a percentage increase in sales.

That’s a practical pilot approach. Choose the flow with the most noticeable delays, test replies and handoffs, then decide whether to expand. New channels and integrations are scoped separately so costs remain clear.

Try the demo, build your setup or contact us directly. In a short review, we look at one typical enquiry, a channel and the expected result. We then provide a clear scope and terms; you decide whether to proceed.