Basic actions
Basic actions are available directly in ChatRex and are not tied to a specific CRM or recording system. In the current catalog there are seven standard actions.
Send webhook
Transfers data from the script to an external system at webhook. Use it for your own API, automation, or service for which there is no ready-made integration.
Before setting up, determine the address of the handler, the data transmitted, the format of the expected response and the rules for re-calling. In the URL, GET and POST parameters, you can insert values using @: the list shows the integration variables and the bot's own variables. Do not place private keys in the plain text of the Prompt.
Stop the bot
Completes automatic dialog processing. Suitable for relaying a conversation to an employee, completing a script or situation in which the bot should not respond further.
In the prompt, specify the exact stopping condition. If the bot does not have to send a generated response after the action, turn on Do not send a response. By default, this parameter is enabled.
Sammari dialogue
Forms a summary of the correspondence. Sammari is convenient to use before transferring a dialogue to an employee or in further automation, so as not to reread the entire history of messages.
Describe what information should be included in the result: customer request, contacts, selected goods or services, agreements and unresolved issues.
Dynamic handbook
Stores editable pairs Question-Answer and returns the appropriate background information to the bot. Suitable for short rules, statuses, correspondences, and frequently changing answers.
- Add the action Dynamic directory.
- Press Add the line.
- Fill in the columns Question and Answer.
- Add the other pairs and save the action.
Send a media file
Sends a file to the user from the connected storage. You can select a specific file or let the bot pick it up according to the description and request of the user.
Before adding the action, upload the materials to Mediafiles and fill out a clear description of each file. Detailed instructions: Use of media files.
Hand over to another bot
Transfers further processing of the current dialogue to the selected bot without creating new correspondence. In the action settings, select the receiving bot. Use the action if different bots are responsible for individual topics, products, languages, or service steps.
Describe the transfer criterion and make sure that the receiving bot has its own channels, prompt and knowledge base set up. Avoid cyclical transmission between bots.
Notification in Telegram
Sends an official notification via Telegram. Suitable for alerting an employee of a new application, dialogue transfer, error, or event requiring a manual response. You can insert eigenvalue and integration variables into the text via @.
Include only the necessary data in the message and do not send passwords, access keys and other sensitive information.
If an operation accesses a CRM, calendar, recording system, or acquiring, look for it under Actions in integrations.