CRM Integration Improvements

You can now select a default pipeline and configure deal movement rules separately for each pipeline, not just the primary one. Previously, default pipeline selection was available only in AmoCRM, and movement rules applied only to the main pipeline.

Deal routing between pipelines is now available. You can configure automatic deal transfers from one pipeline to another based on defined conditions.

The ability to disable the AI assistant at specific pipeline stages is no longer limited to AmoCRM. The feature now applies across all connected CRM systems.

The assistant now automatically reads deal fields and factors them into its context, regardless of whether they were filled by the assistant or manually by an operator. Both default and custom fields are supported.

For Bitrix24, a separate setting for moving leads through the leads pipeline has been added, along with the ability to specify who is assigned as the default deal owner — the chatbot or an operator. Operator selection settings from the Bitrix24 open channel are now also applied.

AmoCRM now supports assignee settings by scenario. You can specify a particular operator for different conditions — for example, assigning a specific operator when a client is from a certain city.

The same CRM account can now be connected to multiple different assistants.