Start Your Library Text Pilot With One Hold Notice

Integrated library systems (ILS) such as Koha, Evergreen, Sierra and Polaris send overdue, due-soon and hold-ready notices by email or text message, and many create those texts by emailing a carrier’s email-to-text gateway. Carriers have restricted or retired that route, which is why hold and overdue texts now arrive late, at odd hours, or not at all.
Patrons usually manage these alerts in their online library account or at the circulation desk, and the exact setup depends on each library’s ILS and vendor.
Here is what the failure looks like from the desk. A hold notice is marked and sent inside the ILS. Staff see a green checkmark. The patron sees nothing. By then the hold has expired and the book is back on the shelf.
An email-to-SMS messaging gateway can replace the retired carrier address with one destination, +1[PhoneNumber]@sendemailtotext.com, while your ILS keeps sending the same email from your own mail server.
Fixing library ILS overdue and holding text alerts from email is rarely a single-field edit. Koha, Evergreen, Sierra, Polaris and Symphony each expose text notices differently, and swapping the wrong field leaves notices failing in a new way instead of an old one.
In this guide, you will learn:
ILS stands for integrated library system. The software runs the library’s core operations, including the catalog, patron accounts, checkouts and returns, holds, and every notice the library sends about them. Most systems send three patron notices:
Email and text are separate delivery channels. Most systems let each patron choose a delivery option, such as mail, email, text message or phone.
The library never sends a text directly. The ILS sends an email, and something on the other end converts it. Under the old carrier-gateway method, three steps had to work every time:
It cost almost nothing, and it fit systems that already generated email notices. It also required a lookup table with a different domain for every network, and a patron record that stored the right carrier.
The steps vary by library, so point patrons to your own account page and circulation desk as well.
When a patron says notices stopped, the cause is usually one of these:
Carriers are retiring these consumer gateways to cut spam and fraud. The timeline is already behind most libraries, and the AT&T migration page documents what broke and when.
| Carrier | Gateway domain(s) | Status | Date |
|---|---|---|---|
| AT&T | txt.att.net, mms.att.net | Retired; ILS carrier records using it now fail | June 17, 2025 |
| T-Mobile | tmomail.net | No longer converts ILS notice email | Late 2024 |
| Verizon | vtext.com, vzwpix.com | Degraded; sunsetting | By March 31, 2027 |
Verizon is the last of the three to finish, and the Verizon migration page tracks the current status of that gateway.
Fake “overdue fine” and “expired card” messages imitate library notices. The advice libraries give is consistent:
For anything about your own notices, such as which channels are offered, current service status or your sender address, ask your local library. Its ILS and vendor determine how notices work.
This is the gap most explanations skip. Staff see “sent” because, in most setups, the ILS record ends when the notice email is handed off. Everything after that hop is invisible from the circulation screen.
Trace one real notice through each hop before you assign a cause:
| Hop | What can fail | Evidence to pull | Usually owned by |
|---|---|---|---|
| 1. ILS event | Notice not generated; patron has no text preference or opt-in flag | ILS notice log and event timestamp | ILS administrator |
| 2. Mail handoff | Wrong template, malformed address, wrong sender identity | Outbound email log; envelope sender and visible From field | ILS administrator or vendor |
| 3. Mail server | Message rejected, queued or bounced | SMTP transaction record | Library or consortium IT |
| 4. Gateway | Carrier gateway drops the email with no bounce | Gateway response; TextBolt delivery status where it applies | Gateway provider |
| 5. Handset | Number blocked, wrong number, phone filtering | Patron confirmation of receipt and its timestamp | Patron and front desk |
One failure point returns no error to the ILS: a retired carrier gateway at hop 4. That is why the checkmark stays green.
Sender, template and queue problems cause failures too. Do not blame the carrier until hops 1 through 3 are clean.
Stop Losing Hold Notices at a Retired Carrier Gateway
TextBolt replaces the dead carrier address with one maintained destination, so your ILS keeps sending the same email.
| Option | How it works | Suits | What to check |
|---|---|---|---|
| Email-to-SMS gateway (TextBolt) | ILS keeps sending email; the destination becomes +1[PhoneNumber]@sendemailtotext.com | A modest notice program where staff can handle consent and replies | Sender registration, address format, reply ownership |
| Email-only notices | Library stops text notices; hold, due-soon and overdue notices go by email | Libraries that can accept losing the text channel | Spam placement; patrons who relied on text only must be contacted and switched |
| Shoutbomb | Third-party SMS service many libraries pair with their ILS; patrons enroll and manage alerts with text keywords | Libraries wanting keyword self-service | Vendor setup, patron re-enrollment, cost from the vendor |
| MessageBee SMS | Library notification service that sends from registered 10DLC numbers, positioned for libraries as carriers phase out email-to-text gateways | Libraries wanting a library-specific notification product | Vendor setup and ILS compatibility |
| ILS-native or vendor messaging | Messaging built into or certified for the ILS; Polaris, for example, can export certain notices directly to a third-party vendor | Libraries needing preference sync, replies that update records, or multilingual notices | Vendor contract and module availability |
TextBolt keeps the mechanism the ILS already knows how to use. The destination points to a maintained address instead of a retired carrier one, and the library’s own email server still does the sending. The ILS needs no SDK, and patrons install nothing.
Every recipient address follows one pattern: the phone number, then the TextBolt domain. A message to +1[PhoneNumber]@sendemailtotext.com reaches that number as a text, whichever carrier the patron uses. One domain replaces the whole per-carrier lookup table.
TextBolt’s gateway takes the email from the library’s existing mail server. It reads the phone number from the address, and the email’s subject and body become the text. The swap is one-for-one:
| Old carrier destination | TextBolt destination |
|---|---|
| +1[PhoneNumber]@vtext.com | +1[PhoneNumber]@sendemailtotext.com |
| +1[PhoneNumber]@txt.att.net | +1[PhoneNumber]@sendemailtotext.com |
| +1[PhoneNumber]@tmomail.net | +1[PhoneNumber]@sendemailtotext.com |
| +1[PhoneNumber]@sms.cricketwireless.net or @mms.cricketwireless.net | +1[PhoneNumber]@sendemailtotext.com |
A reply comes back the same way. The patron texts back as they would to any message, and it lands in the original sender’s inbox as a threaded email. TextBolt assigns each account a business number for outbound SMS. Porting an existing number can be requested for established organizations.
Before any patron gets a hold text, TextBolt files 10DLC compliance registration for your US account. Approval can take up to 48 hours. Until it clears, texts reach only your own verified number. Use that window for staff template tests, and set the patron go-live date after approval.
For a library, the TextBolt dashboard’s delivery status replaces the ILS’s misleading green checkmark by showing when a hold text actually failed. It won’t resend that text or flag a patron number that is blocked, so assign a staff member to review it. The guide to messages not delivering explains the common causes.
Every system below already knows how to send an email that becomes a text. The work is redirecting that email, not adding a texting feature.
Email Gateway $number@sendemailtotext.com
Evergreen does not reformat what the patron typed. If your stored numbers omit the country code, prefix the token instead, as +1$number@sendemailtotext.com. Patrons then pick the carrier and number in their account preferences.
Set the SMSSendDriver system preference to Email, with EnhancedMessagingPreferences allowed. That reveals an SMS cellular providers page under Administration, where you add a provider whose domain is the new gateway. Three settings carry the change:
SMSSendDriver Email
SMS cellular provider domain sendemailtotext.com
EmailSMSSendDriverFromAddress notices@yourlibrary.org
Koha builds the address from the patron’s SMS number and the provider domain. It produces +1[PhoneNumber]@sendemailtotext.com only if the country code already sits in the number field.
Every patron needs the provider selected alongside their SMS number, so switching off a carrier is a bulk update rather than one setting.
The Koha manual warns this method is not recommended unless you have a dedicated SMS-to-email gateway. That is the exact case for pointing at a maintained one.
These systems expose text notices differently from Koha and Evergreen, and a vendor-hosted instance may not expose the gateway setting to you at all. Confirm with your vendor where the carrier domain or text-notice destination is defined before changing anything.
Koha, Evergreen, Sierra, Polaris and Symphony are trademarks of their respective owners. TextBolt is not affiliated with or endorsed by those projects or vendors, as the trademark disclaimer explains.
Point Your ILS at One Maintained Text Address
Enter +1[PhoneNumber]@sendemailtotext.com in your carrier record or text-notice setting, and test it on one staff record first.
Use one real notice type and one test record to answer these questions with your ILS administrator, consortium or vendor.
Find the setting, then record its exact value and rollback state before anything changes. Do not bulk-rewrite patron records until the support owner confirms the supported configuration. A database field that accepts an email-shaped value is not, by itself, evidence that the notice engine will use it correctly.
The gateway accepts US and Canadian recipient addresses in the form +1[PhoneNumber]@sendemailtotext.com. The ILS has to build a valid version for every patron, without spaces, parentheses or dashes.
Test how the ILS handles the country code, blank numbers, extensions, duplicates and malformed data before you trust it at scale.
A stored phone number is not consent. Confirm the ILS treats the patron’s messaging preference or opt-in flag as a precondition for building the address, not just a formatting step.
The gateway converts messages only from approved sender addresses. Mail from an address you have not registered is ignored rather than bounced.
The library address a patron sees may not match the address the ILS mail service actually sends from. Pull the envelope sender and the visible From field from a real test message, then register that identity.
Additional senders are added under Coworkers, Invite, which includes a system sender option for no-reply addresses. Adding senders needs a plan with team access, and a vendor-controlled sender may need the vendor’s help to identify.
Replies go to the address that sent the message, not to a mailbox you nominate. If the ILS sends from a no-reply system address, that is where replies will land.
If staff will invite replies, give that mailbox:
Confirm plan capacity, recipient coverage, allowed use, sender setup, STOP behavior and reply handling with the provider before piloting anything. Read the acceptable use policy to confirm patron notifications are permitted under it. If the ILS workflow or the notification use case is not supported, stop here and look at an ILS-native provider instead.
Treat text notices as an opt-in service from the start. The signup language should state:
The SMS opt-in and opt-out guide has disclosure wording for each of those.
Store that choice in the patron record. Have counsel review the migration language before it goes live.
The gateway applies STOP suppression automatically, and carriers treat UNSUBSCRIBE, CANCEL, END and QUIT the same way. The ILS may keep generating notices until someone updates the patron record too. Decide upfront who gets told, how fast the record changes, and who checks that it happened.
Keep the content minimal. A hold-ready text can name the branch and the pickup deadline without naming the title. Account balances, reading history, and whether the cardholder is a child do not belong in a routine text. Who consents for a child’s card, and whose phone number goes on it, is a decision for counsel and library policy, not a default setting.
Review the program with counsel and library leadership alongside the SMS compliance laws overview.
Work in this order, and keep every step reversible until you have evidence it works.
Work with whoever supports your ILS and set the new gateway address in the documented place, using the settings above. Avoid untested SQL and bulk find-and-replace on patron records.
Libraries on a hosted ILS or a consortium mail system should talk with whoever supports it before changing any live setting. They can also contact TextBolt to scope the pilot.
Hold-ready notices are the easiest first candidate, because the trigger and the outcome are both easy to observe. Start with staff accounts, then a group of patrons who agreed to the pilot and is small enough for the front desk to absorb problems. Keep the existing email, phone or print notice running as a fallback.
Test both US and Canadian number formats if the library serves both countries. The gateway does not deliver to recipients outside them.
| Test | Evidence to capture |
|---|---|
| Hold-ready notice | ILS event timestamp, outbound email log, TextBolt delivery status, recipient phone timestamp |
| Reply | Recipient phone reply, TextBolt inbound log, email landing in the sending inbox, staff action |
| STOP | STOP message sent, no further texts received, patron record updated to opt-out |
| Bad phone format | Validation error or rejection message, error log, confirmation that no record changed |
| Rollback | Configuration restored, previous settings verified, fallback notification confirmed |
During the pilot, track:
Keep only what your retention policy requires. Expand to due-soon or overdue notices only after the library signs off on the evidence, the consent workflow and the added staff workload. A working hold-notice pilot does not automatically clear every other notice category.
One standard credit covers up to 155 characters, as the SMS character limits page explains. A single emoji or curly quote drops that to 70, and longer messages use additional credits.
Count the message as the patron will see it, with names filled in, the opt-out line attached and all punctuation. Do not estimate from the template.
A hold template might read: North Branch: your hold is ready through Wed 6 PM. Call 555-0100 with questions. Reply STOP to opt out.
Use a real branch name so the patron can identify the sender at a glance. Skip a keyword such as R for renewal unless someone can check eligibility, renew the item and reply. A text reply is a request, not a completed renewal.
For each notice type, multiply the monthly recipient count by the number of segments in the finished message, then add replies and retests. A 550-recipient month can consume more than 550 credits if a title, a smart quote or a long opt-out line pushes a message into a second segment.
The trial runs seven days and requires card verification, with no charge during that window. Because of the registration limit described above, plan to measure real volume on a paid plan. Budget for staff time, expired holds, fallback phone calls and failures patrons report.
Do not promise a specific lift in pickup rates. Let the pilot produce that number.
A hold marked sent but never received costs the library a pickup and the patron a book. The retired carrier gateway hides that failure from staff, and the checkmark stays green.
TextBolt replaces the retired address with one maintained destination. Your ILS keeps sending the same email from your own mail server, and the TextBolt dashboard shows which texts failed. The email-to-SMS guide covers the basics for any system.
Start small. Register the sending account, which can take up to 48 hours, test hold-ready notices with staff, then widen the pilot.
Your next step: Start your free TextBolt trial and send one test hold notice to a staff phone.
Text message notices are hold-ready, due-soon and overdue alerts that a library ILS delivers to a patron’s phone. In many setups the ILS never sends a text directly. It sends an email, and a gateway on the other end converts that email into an SMS. Email and text are separate delivery channels, so a patron can receive one without the other.
No. With an email-to-SMS gateway, a patron’s text reply comes back as a threaded email in the inbox of the address that sent the message. The ILS record is not changed. A text reply is a request, not a completed renewal, so staff must check eligibility, renew the item and respond. If the ILS sends from a no-reply address, replies land there, so assign that mailbox an owner.
It depends on where enrollment lives. A keyword service, where patrons sign up by texting SIGNUP with a barcode and PIN, keeps its own subscriber list, so leaving it means former subscribers have to take action. An email-to-SMS gateway works from the messaging preference already stored in the ILS patron record, so the question becomes whether that earlier consent covers the new sender. Before the switch, list which patrons currently receive texts so none are silently dropped.
Not automatically. The ILS has to build the gateway address, send from an address you register as a sender, and show failures instead of hiding them. Koha and Evergreen can do all three through their existing email-to-SMS settings. Confirm your product, version, and hosting before you commit.
Allow about two days. Account setup takes well under an hour; the wait is US A2P 10DLC registration, covered in “What should you plan for before the first send?” Use that window for staff-phone tests of templates and sender registration, so patron sends can start as soon as approval clears.
TextBolt pricing is simple and transparent, and each message credit covers one SMS segment. Cost tracks notice volume and message length, not patron count, and a long opt-out line or a smart quote can add a billed segment.