Bitrix24

How to collect UTM tags in messengers through a website widget

🟢Only the client can write first. 🟢The client should not edit the first message generated by Bitrix. 🟢Customers see the name of your company in the dialogue as Bitrix. 🟢To write to your company, a client needs to remember not only a single number, but also the manager’s ID and be sure to indicate it in the message, otherwise you will not receive the client’s message. 🟢After 24 hours, another company (even your competitor) can communicate with your client on this number 🟢If you do not have time to respond to a client within 24 hours, the dialogue is closed and you will no longer be able to contact this client. 🟢If you responded, but the client did not respond within 24 hours of his last request, then your message will not be delivered to the client. 🟢A large load on a single Bitrix Virtual WhatsApp number operating throughout the country can make this solution very unstable.

Now the user can choose the desired messenger without switching between tabs. The form clearly shows what instant messengers the client uses.

Bitrix24 problem: 12 characters telephon number does not save in CRM clients card

Our clients discovered the problem of freezing of Bitrix24 automation rules at the first stage of the "New" deal. Testing has shown that the hang of different automation rules doesn't always appear, therefore it's difficult to diagnose. If you install an automation rule at the first stage of the deal, the automation rule may freeze. Under the hood (programmatically via Rest), the automation rule tries to send a response to Bitrix24 about the result of its work, while CRM does not always have time to quickly finish creating a business process for a new deal, a 404 "Business process not found" error is returned. We recommend you don't use complex business processes at the first stage of the deal. ChatApp 404 error was bypassed by applying the following algorithm: 1. We send an answer from the automation rule to Bitrix as usual. 2. If we receive an error "404 Business process not found" in response, we pause for 2 seconds and repeat the attempt to send a response from the robot to Bitrix. At this point, the business process has already been created and the robot is working out without hanging.