--- title: "Library Text Notifications Not Delivered? How to Fix the Dead Gateway" url: "https://textbolt.com/blog/library-text-notifications/" date: "2026-08-20T04:44:21-05:00" modified: "2026-08-27T07:28:14-05:00" type: "Article" resource: "https://textbolt.com/blog/library-text-notifications/" timestamp: "2026-08-27T07:28:14-05:00" author: name: "Rakesh Patel" categories: - "SMS Alerts" word_count: 2987 reading_time: "15 min read" summary: "A hold notice can be marked sent inside the ILS and never reach the patron's phone. Staff see a green checkmark. The patron sees nothing. By then the hold has expired and the book is back on the sh..." description: "Carrier gateways are shutting down and library text notifications fail silently. Check your ILS, consent, and reply handling before you migrate patron data." keywords: "Library Text Notifications, SMS Alerts" language: "en" schema_type: "Article" related_posts: - title: "KYC Periodic Review Outreach: Text Customers Who Ignore Email" url: "https://textbolt.com/blog/kyc-periodic-review-texting/" - title: "How to Keep Bank Branch Staff Updated During System Outages " url: "https://textbolt.com/blog/bank-branch-staff-outage-text-alerts/" - title: "From Offshore Email to a Phone Ashore: A Dockside Test Plan" url: "https://textbolt.com/blog/send-text-from-boat-offshore/" --- # Library Text Notifications Not Delivered? How to Fix the Dead Gateway _Published: August 20, 2026_ _Author: Rakesh Patel_ ![Why Library Text Notifications Aren’t Delivered](https://wp.textbolt.com/wp-content/uploads/2026/08/Why-Library-Text-Notifications-Arent-Delivered-convert.io_-1024x576.webp) A hold notice can be marked sent inside the ILS and never reach the patron’s phone. Staff see a green checkmark. The patron sees nothing. By then the hold has expired and the book is back on the shelf. The usual cause is quiet but specific: the library still builds a carrier email-to-text address that routes through a carrier’s own domain, and carriers are shutting that format down one network at a time. Fixing it 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. TextBolt is an [email to SMS messaging gateway](https://textbolt.com/) built to replace retiring gateways. The ILS keeps sending the same email, only the destination address changes, and your own mail server does the work. In this blog post, you will learn how the old carrier-gateway method worked, what to check before changing any patron record, and how to pilot a replacement without guessing about consent or replies. ## Why Library Text Notifications Stopped Reaching Patrons Carrier gateways worked by disguising a text as an email. The ILS built an address from the patron’s phone number and a carrier’s domain. The carrier turned that email into an SMS on arrival. A message sent to 5551234567@vtext.com would land on that Verizon number as a text. It cost almost nothing, and it fit systems that already generated email notices. Three steps had to work every time: 1. The ILS builds the address from the phone number and the carrier domain. 2. The carrier’s gateway converts that email into a text message. 3. The patron’s phone receives the SMS, or the gateway drops it silently. Step two is where this breaks now. Carriers are retiring these consumer gateways to cut spam and fraud, and the ILS keeps reporting the notice as sent. The timeline is already behind most libraries. AT&T retired txt.att.net in June 2025, and T-Mobile stopped tmomail.net for new senders in late 2024. The [ATT migration](https://textbolt.com/migration/att/) page documents what broke and when. Verizon’s vtext.com sunsets by March 31, 2027, and delivery has already degraded. The [Verizon migration](https://textbolt.com/migration/verizon/) page tracks the current status of that gateway. ## How TextBolt Replaces a Retired Carrier Gateway Address TextBolt keeps the same 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. An [email to text solution](https://textbolt.com/solutions/email-to-text-service/) needs no SDK, app, or separate messaging client on the library side. Two things affect your timeline. TextBolt handles [10DLC compliance](https://textbolt.com/blog/10dlc-compliance/) registration for each US account, and approval can take up to 48 hours. Nothing sends until that approval clears, so build the wait into the pilot schedule rather than the go-live date. Delivery status also appears in the TextBolt dashboard, which means a failure is visible instead of assumed. TextBolt does not automatically retry a failed message and does not alert you when a recipient number is blocked. Someone on staff has to check, and [the guide to messages not delivering](https://textbolt.com/blog/why-are-not-my-message-delivering/) covers the usual causes. Point Your Existing Notice Email at an Address That Still Works TextBolt keeps the email your ILS already sends and changes only the destination, with no SDK, no vendor project, and no patron-facing app. [Try TextBolt Free for 7-Day](https://my.textbolt.com/signup/) ## How the Email to SMS Gateway Address Works in Your ILS ILS stands for integrated library system. It is the software that runs the library’s core operations, including the catalog, patron accounts, checkouts and returns, holds, and every notice the library sends about them. The library never sends a text directly. The ILS sends an email, and something on the other end converts it. Every system below already knows how to do that, so the work is redirecting the email, not adding a texting feature. ### How a TextBolt Address Is Built Every recipient address follows one pattern: the phone number, then the TextBolt domain. A message to +15551234567@sendemailtotext.com reaches that number as a text, whichever carrier the patron uses. That last part is the change that matters for an ILS. Carrier gateways needed a lookup table with a different domain for every network. One domain replaces the whole table. TextBolt’s gateway accepts the email over standard SMTP from the mail server the library already runs. It reads the number from the address, and the subject and body become the text. 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. ### Evergreen: Add a Carrier Record Turn on the library setting that enables SMS features, then open Administration, Server Administration, SMS Carriers and add a carrier. The Email Gateway field takes a $number token that Evergreen swaps for the patron’s stored number. 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. ### Koha: Set the Send Driver to Email 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 TextBolt 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, so it produces +15551234567@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. Even those two are different jobs. Nothing here supports the claim that every library can replace an address in the same patron field. Koha and Evergreen are trademarks of their respective owners. TextBolt is not affiliated with or endorsed by those projects. See the [trademark disclaimer](https://textbolt.com/legal/trademark-disclaimer/). ## Check Compatibility of Email to SMS Platform Before Touching Patron Data Use one real notice type and one test record to answer these questions with the ILS administrator, consortium, or vendor. ### Where is the Gateway Defined? Evergreen and Koha each keep this setting somewhere different, and a vendor-hosted system may not expose it to you at all. Find yours, then record the exact value and its 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. ### What Address Does the ILS Produce? TextBolt accepts US and Canadian recipient addresses in the form **+15551234567@sendemailtotext.com.** The ILS has to build a valid version of that address for every patron, with no spaces, parentheses, or dashes. Test how it 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. ### Who is the Final Email Sender? TextBolt converts messages only from approved sender addresses. Mail from an address you have not registered is ignored rather than bounced, so a failed send can look like nothing happened at all. 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. A vendor-controlled sender may need the vendor’s help to identify. ### Can Staff Manage Replies? A patron’s reply comes back 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. A reply does not update a patron record, renew an item, extend a hold, or clear a notice. If staff will invite replies, give that mailbox an owner, coverage hours, retention rules, and a documented way to find the right account. Keep patron data out of the text itself. ### Does the Program Fit the Service and the Library’s Policy? Confirm plan capacity, recipient coverage, allowed use, sender setup, STOP behavior, and reply handling with TextBolt before piloting anything. Read the [acceptable use policy](https://textbolt.com/legal/acceptable-use/) to confirm patron notifications are permitted under it. Check [current TextBolt’s pricing](https://textbolt.com/pricing/) separately before committing a budget. If the ILS workflow or the notification use case is not supported, stop here and look at an ILS-native provider instead. ## What Changes on the Library Side and What Does Not If those checks come back clean, the change itself is small. The notice email your ILS already generates goes to a maintained address instead of a retired carrier one. An email to text solution needs no SDK, app, or separate messaging client on the library side. Patrons install nothing either. What does change is the number patrons see. TextBolt assigns each account a business number for outbound SMS, and porting an existing number can be requested for established organizations. ### What to Plan For Before the First Send TextBolt handles 10DLC compliance registration for each US account, which can take up to 48 hours. Until it clears, sends are limited to your own verified number, so build that wait into the pilot schedule. Delivery status appears in the TextBolt dashboard, so a failure is visible instead of assumed. Someone still has to look, and the guide to messages not delivering covers the usual causes. Consent is the other thing to settle before the first send, and it is not a TextBolt setting. Point Your Existing Notice Email at an Address That Works TextBolt keeps the email your ILS already sends and changes only the destination, with no SDK, no vendor project, and no patron-facing app. [Start Free Trial](https://my.textbolt.com/signup/) ## Consent and Patron Privacy in a Library Text Program Treat text notices as an opt-in service from the start. The signup language should state what the library will send, roughly how often, that message and data rates may apply, and how to stop. The [SMS opt-in and opt-out](https://textbolt.com/blog/sms-opt-in-and-opt-out/) guide has disclosure wording for each of those. Store that choice in the patron record. Do not assume permission collected for an old carrier-gateway program transfers unchanged to a new sender or service. Have counsel review the migration language before it goes live. TextBolt applies STOP suppression automatically at the gateway, 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 itself 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. This is operational guidance, not legal advice. Review the program with counsel and library leadership alongside the [SMS compliance laws](https://textbolt.com/legal/sms-compliance-laws/) overview.. ## A Migration Sequence You Can Roll Back at Any Step Work in this order, and keep every step reversible until you have evidence it works. ### 1. Inventory the Existing Gateway Configuration Export the carrier records, gateway settings, notice templates, sender configuration, and affected patron preferences. Keep a backup, and name the person who can restore it. Pull notice volume by type from recent logs. Do not estimate it from the total cardholder count. ### 2. Build One Supported Configuration With Your Vendor Work with whoever supports your ILS and set the TextBolt address in the documented place, using the settings above. Avoid untested SQL and bulk find-and-replace on patron records. ### 3. Test With Staff, Then a Small Patron Group Start with staff accounts, then a small group of patrons who agreed to the pilot. Keep the existing email, phone, or print notice running as a fallback while you watch. Test both US and Canadian number formats if the library serves both countries. TextBolt 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 | ### 4. Rewrite the Notice Templates for SMS Length TextBolt counts one standard credit at up to 155 characters. A single emoji or curly quote drops that to 70, and longer messages use additional credits. The SMS character limits page covers how segments are counted. 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. ### 5. Calculate Message Credits From Real Notice Volume Start with recent ILS logs, not projections. For each notice type, multiply the monthly recipient count by the number of segments in the finished message, then add replies and retests. Compare that total against your plan allowance. 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. Before 10DLC approval clears you can text only your own verified number, so 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. Test One Hold Notice Before You Change Any Patron Record TextBolt uses the email server your library already runs, with no new dashboard, no separate login, and no training day. [Start Free Trial](https://my.textbolt.com/signup/) ## When an Email Gateway Is Too Small for Your Library An email-to-SMS gateway suits a modest notice program where the ILS can generate the required addresses and staff can handle consent and replies by hand. A purpose-built library messaging product is the stronger choice once you need preferences to sync automatically, replies to update patron records, notices in several languages, or vendor support built into the ILS. Volume is not the only threshold. If replies and opt-outs depend on one person remembering to check, that alone can justify an integrated product. ## How to Pilot One Notice Type Before a Full Rollout If the gateway pattern still fits, keep the first test narrow. Hold-ready notices are the easiest candidate, because the trigger and the outcome are both easy to observe. Pick a group small enough that the front desk can absorb problems, and run it long enough to see them. Track what patrons confirm receiving, opt-outs, replies needing staff action, credits used, and expired holds. Keep only what your retention policy requires. Expand to due-date 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. Libraries on a hosted ILS or a consortium mail system should talk with whoever supports it before changing any live setting, and can [contact TextBolt](https://textbolt.com/contact/) to confirm how the pilot should be scoped. ## Frequently Asked Questions **Why did library text notifications stop working?** The library may still be sending through a carrier email-to-text gateway that has been retired or degraded. Sender, template, and queue problems cause it too. Check the ILS event, the mail transaction, the gateway response, TextBolt delivery status where it applies, and phone receipt before assigning a cause. **Will this work with my ILS?** Not automatically. The ILS has to build a TextBolt 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. **Do patrons need to opt in again?** Do not assume permission collected for a carrier gateway covers a new sender and service. Document what the prior consent actually covered, and have counsel approve the migration or re-enrollment language. Patrons need a clear way to opt out either way. **Does a text reply update the patron’s ILS account?** No. TextBolt returns the reply to the email address that sent the message, not to the patron record. Staff, or a separately tested integration, still have to perform the account action and confirm the result. **How long before the library can send its first notice?** TextBolt account setup takes well under an hour, but A2P 10DLC registration in the US can take up to 48 hours. Until it clears, sends are limited to your own verified number. Build that window into the pilot schedule rather than the go-live date. **How much does this cost to run?** TextBolt plans start at $29 a month for 500 credits, $49 for 1,000, and $99 for 2,500. 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. --- _View the original post at: [https://textbolt.com/blog/library-text-notifications/](https://textbolt.com/blog/library-text-notifications/)_ _Served as markdown by [Third Audience](https://github.com/third-audience) v3.6.1.1_ _Generated: 2026-08-27 12:28:15 UTC_