Facebook is diligent about keeping users safe from spam and unnecessary commercial mailings. All activities of an entrepreneur in WABA are evaluated and controlled.
One of the tools of such control is the quality indicator. It is calculated on the basis of data on communications with users. It is significantly influenced by user complaints about spam, but there are also other factors that are taken into account. You can find out your Quality Score by opening the Phone Numbers tab in WhatsApp Manager.
Limits on the contacts number
There are three so-called trust levels in total. Your trust level determines how many users you can initiate a dialog with. Level 1 allows you to send template messages to up to 1,000 contacts per day, Level 2 - up to 10,000, and Level 3 - up to 100,000. It is the number of users, not the number of messages.
Each registered number is immediately assigned the 1st level.
Further increase of the trust level is automatic. Two conditions must be met.
First, your quality score must not be low. Therefore, it is in your interest to keep an eye on it.
Secondly, it is necessary that within a few days the number of sent notifications exceeds twice the set daily limit of outgoing messages.
Therefore, to move from level 1 to level 2, you need to have 2000 sent notifications and not a low-quality score. This is followed by a few more days of trust level improvement.
Recommendations to ensure a high-quality level
- All messages should be in full compliance with WABA policies and requirements;
- messages should only be sent to customers who have consented to receive them;
- too many messages should not be sent to a user;
- the message should contain useful information for the particular customer, be informative and concise.
Limitations on the number of requests
WABA also has a technical limit on the number of requests for API endpoints. If this limit is exhausted, an error 429, 503 or other error will occur (depends on the specific system state).
There are two kinds of such limits: a limit on the number of requests and a limit on the number of concurrent messages.
Request limitation regulates incoming requests at one or another API point. If exceeded, error 429 follows. Since version 2.25.3. the limit for the messages point is 50 requests per second (a short-term increase to 150 requests is allowed). For previous versions and for other points in all versions, the limit is lower: 20 requests per second (with a short-term increase up to 60 requests).
The concurrent requests limit regulates incoming requests if the load on Coreapp reaches critical values. The error number generated in this case is 503.
If this or that limit has been reached, you should suspend sending requests and reduce the frequency of API calls. If these errors occur to you frequently, it is recommended to create your own queue to adjust requests.