Yes, this would be at the ILS server host level. Rough Setup steps:
1. Account with Flowroute. 2. Action Trigger reactor installed. 3. New action trigger templates formatted to output in the json format that the API requires. 4. Action Trigger runner script setup. (We pre-process the action trigger events right before running the action trigger runner so we only send out one message a day for each type of notice.) Josh On Wed, Feb 8, 2023 at 11:42 AM Diane Disbro <ddis...@scenicregional.org> wrote: > This would need to be done at the ILS server host level rather than at the > library level? > > Diane Disbro > Pronouns: she/her > Circulation Coordinator > Scenic Regional Library > 251 Union Plaza Drive > Union, MO 63084 > (636) 583-0652 ext 110 > ddis...@scenicregional.org > > > > On Wed, Feb 8, 2023 at 11:31 AM Josh Stompro via Evergreen-general < > evergreen-general@list.evergreen-ils.org> wrote: > >> Just in case you were looking for alternatives, We switched from the >> email sms gateway to using an API provided by a vendor (flowroute) back in >> 2018 and that works so much better. No need to know the carrier of the >> user. And we can check each message for deliverability with another api >> call later on, to know which numbers are having issues. >> >> I hacked together a new action trigger reactor to send the message, and a >> perl script to go back and check deliverability later. >> https://bugs.launchpad.net/evergreen/+bug/1667080 >> >> The cost is minimal for us, $100 a year or so for the per message cost. >> >> I currently need to figure out a way to get replies routed back to the >> customers home/pickup library though. Right now they just go to me, and >> figuring out which customer and what notice is time consuming. >> >> Josh >> >> On Thu, Jan 26, 2023 at 11:42 AM Elizabeth Davis via Evergreen-general < >> evergreen-general@list.evergreen-ils.org> wrote: >> >>> >>> >>> Hi, >>> >>> >>> >>> I’m curious if anyone else is having bounce back issues with their SMS >>> notices. Our libraries have seen an increase in bounce backs from a few >>> different carriers, mostly Verizon and AT&T. The bounce backs usually say >>> that the user can’t be found or that the service is unavailable. In most >>> cases the users are getting the SMS messages, albeit on a delay. These >>> locations are not having email notice issues, so the sending address is >>> good. >>> >>> >>> >>> I was just curious if anyone is also experiencing this and if they found >>> anything to remedy the situation. >>> >>> >>> >>> Thanks, >>> >>> >>> >>> >>> >>> *Elizabeth Davis* (she/her), *Support & Project Management Specialist* >>> >>> *Pennsylvania Integrated Library System **(PaILS) | SPARK* >>> >>> (717) 256-1627 | elizabeth.da...@sparkpa.org >>> <katherine.dann...@sparkpa.org> >>> support.sparkpa.org | supp...@sparkpa.org >>> >>> >>> _______________________________________________ >>> Evergreen-general mailing list >>> Evergreen-general@list.evergreen-ils.org >>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general >>> >> _______________________________________________ >> Evergreen-general mailing list >> Evergreen-general@list.evergreen-ils.org >> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general >> >
_______________________________________________ Evergreen-general mailing list Evergreen-general@list.evergreen-ils.org http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
