Polling is a bad option when it comes to Integromat scenarios.Polling means repeatedly sending HTTP requests to some API to check if something has changed in the state of the resource that the API server manages (i.e. REST). Besides overloading the network with too much traffic
In order to make the bot’s flow more generic, it is a good strategy to pass parameters into the bot’s flow. You pass parameters into the bot’s flow by using JSON, and then in the flow, you can use them to make decisions, display dynamic messages, etc…
In some use case, you want to stop a bot’s flow from executing. For example in a case where you ask something and wait for the user’s response. In Twilio Studio, After a waiting timeout without a response from the user, the flow will show the same message
After receiving the approval for WhatsApp business id there is another thing to take into account. During that first week after the approval, you can a maximum of 1000 messages per day. This is the allowed quota. If, during the first week, more than 1000 messages where sent,
You may need to do some computations or other logic with the values that are stored in variables. For example: Collect and order details and sum up the cost of the order items. Now, you have two choices in regards to where you want to do the computations.
During the bot’s flow, you need to collect valuable information that will help you tag or mark in some way the lead/prospect that is talking to the bot. “Valuable ” information is what’s important to your business, for example: email address, first name, last name, phone number, interest,
In this series of posts I want to lay out the foundations of bot creation, so you’ll understand how WhatsApp bot work. Every bot is being created using some third party framework that has the right to officially use WhatsApp business API, like Twilio for example.