Five Upcoming Academic Books on Data Work, Big Tech, and Misinformation
Our most hotly anticipated books for fall!
Posted on in Blog Posts
Posted on January 22, 2024 in Blog Posts
Authors:
Robin Camille Davis
I’ve got a confession to make. For the first eight years of my career, I, a user experience (UX) librarian who could talk for any amount of time about best practices for creating and formatting web content, did not think once about the UX of emails. Not their formatting, not their content, and certainly not how to make them readable and useful for users.
Then I became involved in a project at my library to evaluate and rewrite the automated emails sent out by our integrated library system (ILS), Sirsi. These include courtesy notices (your book is due soon), overdue notices (your book is overdue), billing notices (you have now been charged for the overdue book), and more. This was one of my favorite projects in my time as a UX librarian, and I’ve now become the kind of person who corners friends and acquaintances at parties to talk about the importance of a good email subject line.
In this spirit, I’ll share my top three tips for useful, usable email notices.
The subject line and the snippet—the first 50 or so characters of the email’s body—should contain the gist of the email itself. In a weird inversion of a typical for-profit marketing strategy, we don’t want users to open the email if they understand its purpose.
To test this, send a dummy email to yourself and take a look at it in your email client and on your smartphone. Without opening the email, what do you see?
Library notice – Dear patron, Thank you for using the XYZ Library. We appreciate your continued use of our services. Your library items are…
Library items due in 3 days – Hello, You checked out some item(s) from the XYZ Library that will be due in 3 days. Please renew or return…
🌟 Subscribe to the LibTech Insights newsletter for weekly roundups and bonus content, including:
Some of these automated email notices are giving bad news to the patron. The email should state these facts neutrally and avoid imparting blame. Mistakes happen, for both the patron and library staff. For instance, the patron might have returned an item but a staff member accidentally shelved it without checking it back in. Or perhaps the email was sent out automatically a mere two minutes after the patron had actually returned it. With this in mind, the email should state the facts without assuming what happened, and it should include contact information in case the user has a question.
You have been fined for the following items since you have not yet returned them.
You have been fined for the following items because we did not receive them back on time.
Automated emails don’t have to sound like they were written by a robot. When it’s appropriate, your email can sound informative and friendly! It’s okay for email communication to be less formal-sounding than a snail-mail letter. (Within reason, of course. Overdue and billing notices should avoid jollity.) You can use contractions, use the salutation “Hello” instead of “Dear patron,” and even impart enthusiasm when it’s relevant.
Subject: Requested library item available for pickup
Subject: Good news! Your library item is available for pickup
There’s much more to say about this topic, and if you’re feeling inspired by this post to examine your library’s ILS email templates, I encourage you to read more about it!
Excellent style guides:
About the email improvement project at NC State University Libraries by my colleagues and me:
🔥 Sign up for LibTech Insights (LTI) new post notifications and updates.
📅 Join us for a free webinar on AI citations and ethics for librarians.
✍️ Interested in contributing to LTI? Send an email to Deb V. at Choice with your topic idea.
Our most hotly anticipated books for fall!
Posted on in Blog Posts
What if work could feel remoralizing?
Posted on in Blog Posts
Insights and best practices for teaching AI literacy to history students
Posted on in Blog Posts
What our micro-course participants had to say about AI in libraries
Posted on in Blog Posts