Outbound SMS Concatenation
Incident Report for Simwood
Resolved
We have identified an issue with our SMS billing which has resulted in some customers being undercharged for multi-part SMS messages, specifically where the concatenation limit was set to 1 (the default) we were transmitting longer messages rather than truncating them as outlined in the API documentation.

This has now been corrected, and we do not intend to re-bill any messages sent historically, however please be aware that messages may be truncated as intended where they were not previously, in which case you will need to set the `concat` parameter to a higher value. Additionally, some customers may notice message content that was previously billed as one single part message are now (correctly) being billed as multi-part.
Posted 12 days ago. Nov 06, 2018 - 18:16 UTC
This incident affected: API and Portal.