# Release 26.10.4

October 29, 2026

## New

- **The account in Kazakh.** «Қазақша» has been added to the list of languages. Choose it in the header of the sign-in page or in your profile. The whole account, the online school student portal, mini apps, widget labels and emails are in Kazakh. Kazakh can also be the chatbot language — the bot then sends its service phrases in Kazakh. The Kazakh version of the website opens the account in Kazakh straight away. There is no Kazakh help center yet; links lead to the Russian one. More — [Language](https://support.leadcontact.ru/en/account/profile#language-and-region).
- **Search on the mini-app map.** A magnifier has appeared on the toolbar above the map, just like in the chatbot builder. You can search by the block's ID and name, screen titles and texts, labels of buttons and menu items, variables, texts of toasts and alerts, request URLs and code. The found block shows where the match is, and a click moves the map to the block. Learn more — [Map search](https://support.leadcontact.ru/en/mini-apps/builder#map-search).
- **Consent to data processing before the widget chat.** The widget chat settings have new fields "Consent to personal data processing" and "Privacy policy". If you set at least one link, the visitor sees a sentence with your documents and the "Accept and start chat" button before the chat — the chat opens only after it. The fields are optional: without them the chat opens right away, as before. On websites where a visitor has opened the widget before, the consent screen may appear not right away but within a month: the browser still keeps the previous version of the widget. Future widget updates will reach visitors within minutes. More — [Visitor consent](https://support.leadcontact.ru/en/widgets/chat#visitor-consent).
- **Widget chat as an input bar.** The chat settings have a new "Chat view": besides the widget window, you can choose an input bar in the center of the site, like in AI chats. The conversation appears above the bar when the visitor clicks into it. The bar can be shown right after the site loads or on the widget button — then the button stretches into the bar and folds back. The bot starts when the visitor clicks into the bar, and if the widget has documents — after consent. On a phone a tap opens the usual full-screen chat. The bar can be limited to some pages — for example, promo pages, while the customer account shows the window. The widget window stays the default view. Learn more — [The "Input bar" view](https://support.leadcontact.ru/en/widgets/chat#the-input-bar-view).
- **Tickets in the "Messages" section.** Customer requests can now be handled as tickets: each has a number, a status — "Awaiting reply", "Awaiting customer" or "Closed" — and an assignee. Tickets are turned on for a bot in the "Messages" section settings and are off by default. A ticket is opened by the new "Ticket" block in the scenario — for example, after a "Contact an operator" button — or by an operator with the button in the chat header. Above the chat list there are now "Mine", "Unassigned", "Open" and "Closed" tabs with counters. The conversation feed shows the ticket's history: who took it, who assigned it, who changed the status and closed it. If the customer stays silent, the ticket closes on its own after the set time, and closing can start a scenario for the customer — for example, a "Rate the answer" survey. Notifications about new and assigned tickets arrive, including in Telegram and MAX. The "Ticket chats: only own and unassigned" permission shows a team member only their own tickets and unassigned ones. First reply time, resolution time and each team member's work are on the "Tickets" tab of the "Statistics" section. More — [Tickets](https://support.leadcontact.ru/en/chatbots/messages/tickets).
- **Automatic mailings.** Mailings have a third sending option — "Automatically — to new contacts who match the filters". Such a mailing runs continuously: once a minute it finds contacts who have started matching the filters — for example, got a tag — and sends them the scenario, once to each. You can also send it to those who match at the moment of launch, limit sending to set hours and set an end date. A message sequence is built in the mailing's scenario with the "Delay" and "Timer" blocks. Moving an auto mailing now also creates such a mailing: new matching contacts enter the sequence on their own, as they used to in the auto mailing. More — [Automatic mailing](https://support.leadcontact.ru/en/chatbots/mailings/auto) and [Moving from auto mailings](https://support.leadcontact.ru/en/chatbots/mailings/from-autofunnels).

## Changes

- **Block search by content and with typos.** The magnifier on the chatbot scheme now searches not only by name and ID but also by message text, button labels, variables, tags, HTTP request URLs, prompts and code, and finds blocks without a name by their type. The found block shows where the match is: "button: Book now", "variable: phone". Images and files themselves are not searched — only their captions. The search forgives typos, the other keyboard layout and transliteration: "mesage" finds "Simple message", and "chain mes" finds "Message chain". The "Block creation" window and the list of blocks at the end of a connection now search the same way — in both chatbots and mini apps. Learn more — [Block search](https://support.leadcontact.ru/en/chatbots/builder/canvas#block-search).
- **Language and region in one place.** Language and region are now set in one "Language and region" window in the profile. The Russian variants by country — "Русский (Казахстан)" and others — are gone: their interface was the same, and the country is set by the region. Those who had such a variant now have "Русский", and the country moved to the region if it was empty. The sample number in the request to send a phone before payment now follows the bot owner's region. More — [Language and region](https://support.leadcontact.ru/en/account/profile#language-and-region).
- **The old chatbot scheme view is turned off.** The old view was left only for those who signed up before May 1, 2026: accounts created before February 24, 2026 opened the scheme in it by default, and the others could switch back with the "Revert to old grid design" button. Now that button is gone — the scheme opens in the new view for everyone. It has color schemes, a grid of lines or dots, fullscreen mode, selecting and dragging several blocks at once, and copying blocks to another account. Color and grid are set with the palette button on the top toolbar. More — [The scheme's appearance](https://support.leadcontact.ru/en/chatbots/builder/canvas#the-schemes-appearance).

## Fixes

- **Bot avatar and widget icon when it is the only one in the project.** If a bot or widget was the only one in the project, the switcher in the side menu was not shown — and with it "Avatar and description" and "Change icon" were gone, so they could only be changed from the project list. Now the item is always there: with a single bot or widget, a click opens just the actions — change the avatar or icon, the project list and creating a new one. The same goes for shops and online booking. More — [Widget icon](https://support.leadcontact.ru/en/widgets/editor#widget-icon).
- **Signing in with a phone number.** Signing in to the account with a phone number and password works again — instead of signing in, "An error occurred" was shown.
- **Resending the email confirmation.** If the mail server does not accept the email, the sign-in page now shows a clear message instead of "An error occurred".
- **amoCRM requests did not become deals.** If a request landed in another pipeline or the stage chosen in the settings had been deleted, it stayed in "Incoming leads". Now the deal goes to the stage from the settings. New integrations get the first working stage of the pipeline by default, not "Incoming leads". Learn more — [Integrations](https://support.leadcontact.ru/en/chatbots/settings/integrations#crm).
- **API contact requests with `bot_id` did not get a response.** For bots whose contacts appeared recently, `getContacts` with `bot_id` could take so long to respond that the HTTP block or an external integration cut it off by timeout — the block log showed "Timeout exception". Now the bot's contacts are selected right away, and the response arrives quickly at any page size. Learn more — [getContacts](https://support.leadcontact.ru/en/api/contacts#getcontacts).