The default throughput can be modified from the admin dashboard for a given account. This will impact all API calls, not just SMS.
It is very important to find out from the client the daily/hourly volume of SMS they are likely to send and the nature of their traffic. If their SMS are not time-critical and the daily volume is not high you should not modify the restrictions.
Also, if they are sending to a unique or small number of networks only, we should be careful to not create a bottle neck on the supplier side, which would cause throttling and queuing issues on our connection and therefore for all customers. You can see the per-supplier throughput we have under Platforms in the Admin dashboard.
As a general rule if increasing over 30 SMS per second, we need to ensure that the client will not over-load a single connection.
Articles in this section
- [Internal] Quota Violation Error
- [Internal] Send-SMS API Doc Linking Placeholder
- [Internal] What is error code 34 and why is it not documented in the Error list?
- [Internal] US Short Codes API Doc Linking Placeholder
- [Internal] UDH settings for concatenated messages
- [Internal] Do we support sending SMS messages to numbers ported to VOIP providers in the US?
- [Internal] Handling China Traffic When Sender IDs Are Blocked by an Operator
- [Internal] Blocked Numeric Sender IDs to Austria H3G (43660)
- [Internal] Setting Up an Account for SMPP Connection
- [Internal] Wordpress WP Restaurant Manager