(Item from 2023 Project Ideas) SMS delivery has become problematic and inconsistent, with some popular carriers using the current Email to SMS gateway set up. Carriers are throttling or delaying delivery, blocking them entirely and in some cases delivering the message but sending a bounce back. Additionally, due to the wide variety of budget carriers or carriers who use multiple networks, we are not able to confidently offer SMS notices to those patrons.
We need to investigate and explore new SMS delivery methods development to maintain this functionality, including tie-ins to 3rd party carriers as well as better native options in Evergreen.
https://bugs.launchpad.net/evergreen/+bug/1667080
2 Responses
What would a native option in Evergreen look like? I’m having trouble imagining this.
The linked bug is essentially working with an API from flowroute. We would essentially be setting up notices the same way we do for email and email-gateway SMS notices, but they would be sent directly to flowroute.
Some of us are using a third-party service like MessageBee, but, in this case, Evergreen is using scripts and then emailing the info to the third-party service, which is probably using a service like flowroute to send the messages.
There is still a cost to using flowroute, but it is far more affordable than the services some of us are using to send our text messages.