When working with Bitrix24, AmoCRM/KommoCRM, and Altegio integrations, the Message.Help system automatically recognizes verified WABA templates and sends messages exactly as official paid WABA messages—even if you don’t explicitly specify the template’s service name.
The most convenient way is to write a message that matches a verified template, substituting the necessary values for the variables. The system will automatically recognize the template and send the message as a WABA message.
Example 1. Verified template:
“Hi, {NAME}, this is {EMPLOYEE}’s manager—is now a good time to chat?”
In the integration, simply write:
“Hi, Carlos, this is Sofia, your manager—is now a good time to chat?”
The message will be sent as an official WABA message with the variable values substituted.
Example 2. Verified template with an arbitrary variable:
“Good afternoon!
{TEXT}
Thank you for your reply.”
In the integration, write:
“Good afternoon!
It’s me. I’m writing to remind you of our agreement—we’re meeting tomorrow at 1:00 PM, unless, of course, you’d like to reschedule. What do you think?
Thanks for your reply.”
The system recognizes the template structure and sends the message as a WABA.
An alternative option is to send the template’s internal name, which was specified during its verification. In this case, the system will also send a WABA message, rather than the text of the name itself.
⚠️ Important: When sending using the template’s internal name, you won’t be able to use variables—the message will be sent exactly as the template was verified, without any values being substituted.
In the Altegio integration, the principle is the same, but it is particularly convenient for automated notifications where the message text is generated by the system.
Example. Verified template:
“Confirmation code: {CODE}”
When a customer requests a confirmation code, Altegio automatically substitutes the appropriate value—and the message is sent specifically as an official WABA message, rather than through a regular channel.
This is particularly important for critical notifications—such as confirmation codes, appointment reminders, and other messages where guaranteed delivery and the sender’s official status are essential.