It’s time again for the annual list of the most commonly reported comments sent to our Quality Team. In 2012, Quality received comments 528 transcripts: 319 (60%) related to sessions handled by librarians from Coop libraries and 209 (40%) related to sessions handled by QP Backup librarians. In addition to these 528 sessions, we received an additional 89 sessions sent to compliment the outstanding work of the chatting librarian. To put this in perspective, the Cooperative (including QP Backup librarians) handled 367,128 chat sessions in 2012, so 528 represents 0.14% of the total.
The list below reflects the most commonly reported issues in these 528 sessions (some sessions had multiple issues), listed in order of frequency:
1. Policy Page
Librarian does not check the policy page. This inference arises when the information provided in session by the librarian either ignores or contradicts the information provided on the patron library’s policy page. This was also the most often reported issue in 2009, 2010 and 2011.
2. Resolution Code
Incorrect resolution code is assigned. Examples: incorrect use of the “Lost Call” code; librarian coding a session as “Answered” when telling the patron that another librarian will follow up; librarian coding a session for “Follow Up” when patron did not leave an email address.
3. Reference Conversation
Librarian does not properly clarify the question or otherwise engage in the “reference interview”, thus risking miscommunication with the patron.
4. Incorrect information was provided in the session.
In addition to factual errors, this issue refers to any type of "incorrect" piece of information provided during the chat. This issue is often used in conjunction with other issues, for instance if the librarian provides incorrect information regarding a library policy (many times, this happens when the chatting librarian provides an answer based on his own library policies rather than those of the patron’s library: we may code this issue as both “policy page” and “incorrect info”). It also applies if the librarian says "Your librarians have not given me the ability to access your databases, so I cannot help you" but the library did provide a barcode number on the policy page. Or, if a librarian told the patron to use the Academic Search Premier database but the library doesn't subscribe to any EBSCO databases.
5. Contact/Followup Option (tie with No Searching)
With questions of a local nature, the Cooperative librarian may be unable to provide a complete answer to the patron. This is almost always the case when patrons have circulation issues, problems with their library card, etc. Unfortunately, some librarians tell the patron to “contact your library” rather than giving the patron the option to call the library (in which case the chatting librarian should provide the correct phone number, as per the policy page) or offering to code the session for Follow Up.
5. No Searching (tie with Contact/Followup Option)
The librarian sent a question to Followup or ended the call without attempting a specific search for the information. Examples include: patron queries whether the library owns a known item and the librarian tells patron to contact the library rather than searching the library catalog and/or databases.
-- Compliments!! --
6. Patron Info (tie with Source Choice)
Librarian should have checked the patron information section to find out the patron's location. For example, the librarian may have asked the patron, "What library do you use?" when the patron already indicated his preferred branch. It is better to ask, "Is ___ your library?"
This code is also used when the librarian does not review the Patron Info tab in the chat monitor and thus fails to note the patron’s library. Example: librarian assumes a New York customer is a patron of New York Public Library although the Patron Info tab reveals that patron is affiliated with another library in New York State.
6. Source Choice (tie with Patron Info)
This issue arises when librarian could have sent better sources (i.e. more authoritative, more current, more appropriate to the patron's level). For example: Librarian does a Google search or sends a wikipedia article for queries that could better be handled by reference to the library’s online databases or catalog.
7. Tone/Phrasing
The chatting tone of the librarian affected the quality of the session, or, the librarian used negative phrasing .
8. Abrupt Ending
Ended session abruptly without a natural closure to the conversation or when the patron still seemed to need help.
9. Goodbye (tie with Transfer/IM)
The wrong goodbye message was sent (chatting librarian sent their own library's goodbye message rather than patron library goodbye message).
9. Transfer/IM (tie with Goodbye)
When librarian either (1) incorrectly transferred a chat; (2) transferred a chat without using IM first; or (3) the librarian should have offered the transfer option but did not.
10. Hello
Librarian did not use a hello message that conforms to guidelines listed in the Best Practices.
A plea to the Cooperative: Help us with Quality!
Thanks to all for using the 24/7 Reference quality process! By sending sessions to Quality, you not only help us provide guidance when needed to the Coop librarians, but you also help us track issues both for individual libraries and the Cooperative as a whole. And, if you think a Cooperative librarian has done a nice job with one of your patrons’ questions, please send the compliment to Quality. We will pass the compliment along to the chatting librarian, and this helps us keep track of our star libraries. So, don’t hesitate to send a compliment – we love passing those along!
How to send a session to Quality:
In the Ask a Librarian (Ask) module, click the Review Transcripts tab. When viewing the full text of the session, click the “Send to Quality Control” button. Type in any concerns or compliments in the text box, and click submit. The Quality Team will receive your comment with the full transcript, and will respond.
If you have questions about quality, don’t hesitate to email me at [email protected]
Recent Comments