Meet the big update of the ChatApp bot builder!
The bot can be even more finely tuned for your business, because now it can receive and send webhooks, perform actions depending on specified conditions, personalize dialogues with customers using variables, and much more. We talk about new blocks and types of scenarios in detail.
New blocks
The ChatApp chatbot autonomously communicates with the client in a closed dialogue until the trigger for connecting the operator is triggered. The scripts work in all instant messengers you use, and all conversations will be collected in a single ChatApp Dialog window.
Incoming and outgoing webhook
A webhook is a mechanism for notifying one system about changes in another system. Unlike the API, which involves constantly sending requests, a webhook fires only when the desired event occurs.
A webhook can make changes to CRM cards directly during a dialogue with a client - and trigger the necessary events in the dialogue after changes in CRM. You don't have to do this manually.
The “Incoming webhook” block is needed to accept a request from CRM.
The “Send webhook” block is needed for requests to be sent to CRM.
We analyzed the scenario with webhooks using the example of integration with Bitrix24 and recorded a video - watch it to make it easier to understand.
Condition
You can configure the bot to perform actions depending on specified conditions. For example, the bot can ask the client to send missing contact information. Read more about the “Condition” block in the knowledge base.
Variables
Personalize communication with the client and increase the level of trust in the company using variables. There are two types of variables: local and global. Local values are unique for each dialog - they include, for example, the client's name and contact information. The global variable, in turn, is saved for all dialogs - for example, this is the line on which the bot is working.
Blocks “Pause” and “Return to Beginning”
The Pause block is useful if you want to wait some time before sending the next message to the client - for example, wait until he reads the previous one.
And the “Return to start” block will help you start the bot script again when it ends.
Block “Waiting for message”
This block will wait for the client to respond and only then continue the script. It is needed because all the blocks of the script are triggered automatically one after another - and this way the dialogue with the bot will be more comfortable for the client.
Types of scenarios
The editor has two types of scripts - interactive and for accepting requests.
A conversational script is used to respond to a customer when they message you first. It starts with the starting block.
The Request Acceptance Script is used when you need to write to the client first. It starts with the “Incoming webhook” block - for example, it receives a request from CRM and sends a message to the client. When this script completes, the dialog script opens after the next message from the client.