Sending speed limit
Each messenger limits the speed of sending messages:
- In VKontakte — 10 messages per second.
- Facebook*, Instagram* — 30 messages per second.
- Telegram has a limit of 30 messages per second from one flow, but no more than one message per second per chat. Short-term exceeding of the speed limit for API requests is not a big deal, but at this point Telegram pauses for 30 seconds. Next time — for 120 seconds. During this time, your flow stops working completely until the “cool down” period is over.
BotHelp distributes the load on your channels in such a way as to ensure the maximum speed of sending broadcasting, but not to exceed the limits of the platforms.
Broadcasting leaves BotHelp at an average rate of 20 messages per second.
Messages are considered to be each file and each text block in the broadcasting or flow. The caption to a file or image is also considered a separate message. The most accurate way is to use the “Gallery” block: each file counts as one message.
Flow messages are processed first and slow down broadcasting
When several flows and broadcasting are launched in the same channel, they all compete for the right to go to <url>.
First, the service processes the tasks of sending and receiving messages from flows, then — of sending sequences and broadcasting. Last of all, tasks of editing and deleting broadcasting are processed.
When there are a lot of blocks in the broadcasting, BotHelp tries to send it as quickly as possible. At the same time, you can send no more than one message per second per chat. Therefore, the sending program sends the first 1-2 messages to the person and goes further to reduce the time for sending. During this second, the program will process another 20 people. When the first messages go to the recipients, the sender returns and sends the remaining messages.
In practice, this means that if a broadcasting is sent over a large database, recipients will see a noticeable pause between the first and last messages.
For example: if there are 5 message blocks per 10,000 users in a broadcasting, then the pause between blocks will be approximately 4 minutes.
This process is best illustrated by the process of getting off the airplane. When exiting from the middle of the cabin, passengers from aisle seats will reach the exit faster than those sitting at the window closer to the exit. In this analogy, a single row of seats corresponds to a broadcasting of three blocks.
BotHelp successfully copes with such traffic jams from the message queue and optimizes sending broadcasting so that operation goes smoothly and your flows are not blocked by messengers.
Preparing the broadcasting
During the broadcasting, you set up sending parameters: compliance with tags and certain conditions. When the broadcasting starts, the system will check the people of your channel for compliance with the conditions. The more conditions and the larger the database, the longer it takes to prepare the broadcasting. The number of fields and global variables also affects this.
For example, you can recall the behavior of your computer when you try to find a file. If you search for a file named “Report” on a flash drive, the search is almost instantaneous. If you connect a full large hard drive, the search may take tens of minutes.
For large databases, we recommend taking into account the time required for preparing broadcasting and setting an additional 5 minutes for every 20,000 people.
Deleting and editing broadcasting
We recommend that you avoid simultaneously running editing and sending broadcasting to large volumes, because they also consume the limit of requests to Telegram.
Imagine that you are letting the passengers disembark the airplane and at the same time letting new passengers on the next flight through the same door.
Segmentation of a large audience by telegram flows
When one channel has more than 20,000 people, we recommend segmenting the audience. This will allow you to send broadcasting with your offers faster, and preparing broadcasting will take less time.
Example:
In a flow with 100,000 people, sending a broadcasting containing an image and a message will take more than 2.5 hours. By segmenting this audience into 5 channels of 20,000 people each, you can deliver your broadcasting in 30-40 minutes.
You can segment your audience by products, news hooks, cities, webinars, and any other parameters that suit you.
Recommendations for databases with more than 20,000 people
- Launch broadcasting in advance. Send the broadcasting that is supposed to reach people 15 minutes before the webinar earlier, taking into account the time required for generating and delivering the message.
- In broadcasting for an audience of more than 5,000 people, put no more than two blocks. For large volumes, part of the broadcasting may be delayed and reach the user in a few minutes.
- Segment the database into different telegram flows when there are more than 20,000 people in one flow.
- Avoid parallel editing and sending broadcasting through the same channel.
- Separate the warming up channels, lead generating, and product delivery — then sharp spikes in traffic will not affect the response speed of flows.
- Grant each employee their own access to the BotHelp profile with the required access level. Enter your email address and phone number to receive notifications about important events.
- Set broadcasting to be sent at a non-round time. The 9:53 a.m. broadcasting will leave faster than the 10:00 a.m. one. The BotHelp platform rush hour starts in 10:00, 16:00, 18:00 and 19: 00.
- Warn your personal manager about large launches, after which you expect more than 20,000 incoming applications.
Google Sheets limits
For reading and entering the database in spreadsheets, there is also a speed limit. In 1 minute, you can read no more than 60 cells and enter no more than 60 cells.
We recommend that you enter and read only the most relevant data. It is important to keep in mind that when there is a lot of traffic in the flow, spreadsheets may not have time to record your data.
* Owned by Meta, an organization recognized as extremist and banned in Russia.
_________________________________
If you haven’t found the answer to your question, contact us in the chat in your profile or email [email protected] 😃
Get 14 days of full functionality of BotHelp, a platform for creating broadcasting, autofunnels, and chatbots.