The solution we implemented
Posted: Sat Dec 21, 2024 3:41 am
When implementing this project, as always, we tried to take into account the specifics of the client, the features of their business process, as well as the capabilities of Bitrix24 itself.
Why didn't we implement all this functionality through regular transactions?
Bitrix24 already has ready-made standard functionality t accurate mobile phone number list hat allows you to automatically create identical transactions with a predetermined frequency. However, if we used regular transactions, we would have imposed a huge amount of work on the client's employees and would not have reduced the influence of the human factor at all.
Each time after selling the first license to a new client, the employee must create a template for a regular transaction and specify all the data there. And only then would this template create transactions with a given frequency.
It seemed that this is what we were trying to achieve, but with this option, we would make a serious mistake. When specifying the transaction frequency as "monthly", the next transaction is created when it is too late to process a new license. The current license will expire, and the client will be left without software for the entire period while a new license is being processed.
Further, if the client asks for the next license not for a month, but for three months, then we will still receive a new deal to extend the license in a month, because we specified this period when creating the template for a regular deal. In addition to the above, the use of regular deals brings many other inconveniences.
Recommended tariff
To implement such projects, in cloud versions of Bitrix 24 we recommend using the "Team" tariff. It is starting from this tariff that business processes start working on the portal, which are very important for setting up the functionality, which I will describe in more detail below. In tariffs below "Team", business processes, unfortunately, do not work. In boxed versions of Bitrix24, business processes work in all tariffs.
Why didn't we implement all this functionality through regular transactions?
Bitrix24 already has ready-made standard functionality t accurate mobile phone number list hat allows you to automatically create identical transactions with a predetermined frequency. However, if we used regular transactions, we would have imposed a huge amount of work on the client's employees and would not have reduced the influence of the human factor at all.
Each time after selling the first license to a new client, the employee must create a template for a regular transaction and specify all the data there. And only then would this template create transactions with a given frequency.
It seemed that this is what we were trying to achieve, but with this option, we would make a serious mistake. When specifying the transaction frequency as "monthly", the next transaction is created when it is too late to process a new license. The current license will expire, and the client will be left without software for the entire period while a new license is being processed.
Further, if the client asks for the next license not for a month, but for three months, then we will still receive a new deal to extend the license in a month, because we specified this period when creating the template for a regular deal. In addition to the above, the use of regular deals brings many other inconveniences.
Recommended tariff
To implement such projects, in cloud versions of Bitrix 24 we recommend using the "Team" tariff. It is starting from this tariff that business processes start working on the portal, which are very important for setting up the functionality, which I will describe in more detail below. In tariffs below "Team", business processes, unfortunately, do not work. In boxed versions of Bitrix24, business processes work in all tariffs.