Koha How-To

Communicating with Koha: Third-Party Notice Integrations

Koha has email and SMS messaging options built in. These templates are all configured in Tools > Notices and slips. Recently, some Partners have reported issues with cellular providers in their areas discontinuing email to SMS functionality (the way that Koha sends SMS messages to patrons). Others have had issues with their messages being flagged as spam. For these reasons, we strongly recommend that our Partners not use email to SMS in Koha. There are a few third-party vendors who provide marketing and messaging solutions that libraries can use to communicate with their patrons and develop more robust templates and reports. If you are looking for other SMS providers that can integrate with Koha or if you’re looking for a more robust tool than the inbuilt functionality provides, here are some third-party vendors to consider.

Patron Point

Patron Point uses an API connection in Koha so the setup is relatively easy, involving just a few system preferences and an API user. They offer a variety of options, including email, SMS, and phone. Once the connection is established and configured, notices are maintained in Patron Point. For these reasons, Patron Point is the most simple and straightforward option for third-party messaging in Koha.

https://springshare.com/patronpoint/

Twilio

Twilio offers both SMS and voice, but not email. Our Systems team will need to do a little bit of backend setup for SMS, but the notice templates are maintained in Koha, the same as if you’re using the Koha email to SMS option. You’re just switching how those messages are relayed to your patrons. Twilio voice messages are controlled via a plugin and, like SMS, the notice templates are maintained in Koha. The setup and maintenance of Twilio in Koha are relatively easy, but the lack of an email option keeps them from being a comprehensive all-in-one solution.

https://www.twilio.com/en-us

MessageBee

MessageBee provides email, SMS, and voice notices using a Koha plugin and a few system preferences. The notice templates in Koha require YAML code specified in the plugin documentation. Once set up, Koha sends the relevant metadata to MessageBee. The actual, pretty notice templates are maintained in MessageBee and sent from them to your patrons. Partners like having a comprehensive solution but troubleshooting issues requires Developer eyes to look into the code, since only the metadata numerical codes are stored in the patron’s account.

https://uniquelibrary.com/messagebee/

Other Vendors

Koha can integrate with other vendors not detailed here, but doing so would require development.

Patron Messaging Comparison Chart

If you decide to contract with one of these vendors and you’re a ByWater Partner, just submit a ticket and we’ll help you with the setup process.