I use RingEX for my team for day-to-day cross-regional communications between our engineering teams in India and the US, as well as programmable notifications for our backend fulfillment service infrastructure. Setting up our automated alerts system in Spring Boot by making a private app in the RingCentral Developer Console using JWT-based authentication (RC_USER_JWT) and integrating the official Java SDK was done in just one afternoon. Configuring Incoming Webhooks with Adaptive Card JSON messages allowed us to send real-time order-pipeline failure alerts to specific Team Messaging rooms, and sending out texts to on-call leads via the v1.0 SMS endpoint when our SLAs are violated for store-pickup orders. In terms of day-to-day communication, the combination of voice, HD video, and messaging in one desktop application is what makes our incident management faster. Having AVA turn on for my meetings and automatically make notes for me in the evening means I don’t have to write down my own meeting notes manually anymore. Review collected by and hosted on G2.com.

The implementation of an outbound programmatic SMS via The Campaign Registry (TCR) 10DLC vetting in the Admin Portal has been quite a challenge since it has taken us several days to comply with it. The REST API also has strict per-extension rate limits, and if burst traffic exceeds around 40 requests per minute, then it will give HTTP 429 (CMN-301) errors. Thus, I have had to develop a mechanism that would help me handle the rate limits on my side through token bucket throttling. Moreover, in Team Messaging, the Adaptive Card webhook parser is quite sensitive to the payload size and character escaping, and thus, if there are unescaped brackets or the stack trace is too long, the webhook will fail silently if I won’t escape and reduce the JSON content. Also, keeping the desktop application with active screen sharing together with lots of messaging channels takes up some amount of local RAM. Review collected by and hosted on G2.com.