Before implementing SMS Messaging in Horizon, there are several considerations to keep in mind:
• | It is important to understand that there is no guarantee of when the SMS message will be sent by the SMS server. It depends on the number of messages being sent, Internet traffic, and the size of the backlog of messages that need to be sent. Therefore, you should not expect that the text message gets sent out immediately. |
• | The SMS server will not send more than one text message per second per site (based on the SMS server long code). So, keep that speed in mind when you set up the transmission start and end times. However, this does not affect the overall runtime of the day end processing because those messages are queued on the SMS processor for sending during the configured transmission time period. Additionally, the SMS server queues the messages that it receives from Horizon. To increase the number of messages sent per second, you would need to purchase an additional SMS server long code and install another SMS Processor. |
• | If you create a message that is longer than 160 characters, the system splits up the message into two or more messages. Therefore, you need to take this into account when planning for the number of messages you need to send, as well as the potential extra costs to your library since you would be charged for each message sent. |
• | If you need a report of how many messages have been sent and to whom they were sent, you must contact your SirsiDynix SirsiDynix Customer Support representative. Note that the Overdue Notices stat category will contain stats data that includes SMS messages for overdue items when the SMS overdue notices have been set to count as a notice sent. |
• | Pre-Overdue notices for SMS are handled separately from the regular pre-overdue notice settings. Therefore, it is not possible to use SMS in place of a pre-overdue notice (the count as notice sent option). You can configure the notice to go to SMS and email, or to go to one or the other, or you can configure when each one happens for certain situations (notice number, for example). |
• | The location table has a Default Hold Notice Type field (mail, phone, or deliver) to determine how you will notify borrowers of holds. There is all an SMS Text Messaging option. You do not need to select this option. This is for SirsiDynix internal use. Selecting this option will not have the anticipated effect and may default to an undesired default hold notice type. Instead, use the Count as Notice Sent option for Holds (sms_control table) to have the system send an SMS message instead of (Count as Notice Sent is checked) or in addition to (Count as Notice Sent is cleared) another notice type. |
• | When the SMS Processor is turned on in the Horizon Information Portal, it uses less than 1 MB (200 KB) of memory. When it is processing messages it uses less than 10 MB (8.4 MB). You should make sure that the system has at least 10 MB extra memory available. |
© 1998-2017 Sirsi Corporation