Messaging Sizes & Character Limit Updates
We are rolling out updates to our system that align how we segment messages in our platform to match the limits of the carriers. This will ensure that we are billing customers for the same count of messages that we are being charged by the carriers.
While most of the details are covered in the article above, here are some key things:
Max message composition size is being increased from 500 to 600 characters (imposed on the API as well)
We have added counters to all message composition boxes throughout the platform to give real-time feedback to the client as they type
Added an overall campaign message counter on the Blast Create screen
This is only applicable to clients on our v2 platform
NOTE: Because CCaaS agents primarily use the native chat message box, we cannot interject a customer character/message counter in that view. However, the counters do exist on any of the outbound forms.
Public API Rate Limits
Recently we had a client's system get a process stuck in a loop that caused them to send millions of calls to our public API. As a result, we have implemented limits on our gateway to prevent rogue client processes or bad actors from impacting our system performance.
Limits
Send Message endpoint is limited to 100 calls per second
All other public API endpoints are limited to 5 calls per second
Updated Sending Status from Twilio & Bandwidth
We don't always get the final delivery confirmation from Twilio and Bandwidth, so we have made the Twilio Sent status and Bandwidth Sending status a final status that maps to Delivered.Â
Failed messages would get a separate status update.
Platform Health
Foundation | System to Process Deadletter Queues
Foundation | Move Incoming to Message Microservice
Foundation | Fix External Line Row Locking
Update JobRequestBody to nvarchar(max)