Sending speed limit
Each messenger limits the speed of sending messages:
- On VKontakte there are 10 messages per second.
- Facebook*, Instagram* — 30 messages per second.
- Telegram has a limit of 30 messages per second from one bot, but no more than one message per second per chat. Short-term excesses of the API call rate are not scary, but at that moment Telegram pauses for 30 seconds. The next time — for 120 seconds. During this time, your bot stops working completely until the “cooling down” period passes.
BotHelp distributes the load on your channels in such a way as to ensure the maximum speed of sending mailings, but not to exceed the platform limits.
Mailings leave BotHelp at an average rate of 20 messages per second.
Each file and each text block in a mailing list or bot are considered messages. A signature to a file or picture is also considered a separate message. The Gallery block should be used most carefully: each file is considered one message.
Bot messages are processed first and slow down mailings
When multiple bots and mailings are running in one channel, they all compete with each other for the right to be sent.
First, the service processes tasks to send and receive messages from bots, then — to send auto-mailings and mailings. Lastly, tasks to edit and delete mailings are processed.
When there are many blocks in the mailing, BotHelp tries to send it as quickly as possible. At the same time, no more than messages can be sent to one chat per second. Therefore, the sending program sends the first 1-2 messages to the subscriber and moves on to reduce the time for sending. During this second, the program will process another 20 subscribers. When the first messages are sent to the recipients, the sender will return and send the rest.
In practice, this means that if you send a mailing to a large database, recipients will see a noticeable pause between the first and last messages.
For example: if a mailing to 10,000 users contains 5 message blocks, then the pause between blocks will be approximately 4 minutes.
The best way to illustrate this process is when disembarking from an airplane. When exiting from the middle of the cabin, passengers in the aisle seats will get to the exit faster than those in the window seats closer to the exit . In this analogy, one row of seats corresponds to a three-block mailing list.
BotHelp successfully copes with such traffic jams from the message queue and optimizes the sending of the mailing so that the work goes without slowdowns and your bots are not blocked by messengers.
Preparing the mailing list
During the mailing, you configure the sending parameters: compliance with labels and certain conditions. When the mailing starts, the system will check your channel subscribers for compliance with the conditions. The more conditions and the larger the base, the longer it takes to prepare the mailing. The number of fields and global variables also affects.
As an example, let's recall the behavior of a 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 completely full large hard drive, the search can take tens of minutes.
For large databases, we recommend taking into account the time for preparing mailings and allocating an additional 5 minutes for every 20,000 subscribers.
Deleting and editing a mailing list
We recommend avoiding simultaneously running editing and sending large-volume mailings, as they also consume the Telegram request limit.
Imagine you are disembarking passengers from a plane and at the same time letting new passengers on the next flight through the same door.
Segmentation of a large audience by telegram bots
When you have more than 20,000 subscribers in one channel, we recommend that you start dividing your audience. This will allow you to send out newsletters with your offers faster, and preparing newsletters will take less time.
Example:
In a bot with 100,000 subscribers, sending a newsletter containing a picture and a message will take more than 2.5 hours. By dividing this audience into 5 channels with 20,000 subscribers, you can deliver the newsletter in 30-40 minutes.
You can segment your audience by products, news items, cities, webinars, and any other parameters that suit you.
Recommendations for databases over 20,000 subscribers
- Launch mailings in advance. Send the mailing 15 minutes before the webinar, taking into account the time for formation and delivery.
- In mailings to an audience of more than 5,000 subscribers, place no more than two blocks. In large volumes, part of the mailing may be delayed and reach the user in a few minutes.
- Segment the base into different telegram bots when one has more than 20,000 subscribers.
- Avoid editing and sending newsletters through the same channel in parallel.
- Separate the channels for warming up, lead generation and product delivery - then sudden surges in traffic will not affect the response speed of bots.
- Give each employee their own access to the BotHelp account with the required access level. Enter real emails and phone numbers to receive notifications about important events.
- Set mailings to be sent at non-round times. A mailing at 9:53 will be sent faster than one at 10:00. Rush hours on the BotHelp platform are at 10:00, 16:00, 18:00, and 19:00.
- Alert your account manager about big launches after which you expect 20,000 incoming applications .
Google Sheets Limits
There is also a speed limit for reading and writing the database to tables. In 1 minute you can read no more than 60 cells and write no more than 60 cells.
We recommend writing and reading only the most necessary data. It is important to remember that with high traffic in the bot, the tables may not have time to write your data.
* Belongs to the extremist organization Meta, which is banned in the Russian Federation.
If you have not found the answer to your question, ask us in the chat inside your account or write to BotHelpSupportBot or to hello@bothelp.io
Get 14 days of full functionality of the platform for creating mailings, autofunnels and chatbots BotHelp.