Print

Print


Probably not cheap and built more for IT, but... I led the implementation of a Service Now instance for my last job at a law firm library. I think it was very successful. 

https://www.servicenow.com/solutions/customer-experience/enterprise-cx.html

If you're interested, I could tell you more offline about it. 

Jessica Trenary (she/her)
MARINet, Systems Librarian
Cell: 415-867-5562
[log in to unmask]

-----Original Message-----
From: Code for Libraries <[log in to unmask]> On Behalf Of Haitz, Lisa (haitzlm)
Sent: Wednesday, May 4, 2022 8:59 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] Email ticket system

WordPress has several plugins that will do this. Some require purchases. Here's an article discussing how one might approach doing it for free:
https://wpmudev.com/blog/free-ticketing-system-wordpress/

---------------------------------
Lisa Haitz (she/her/hers)
Software Developer
Application Development Unit
University of Cincinnati Libraries
513-556-1431
[log in to unmask]
 

 

´╗┐On 5/4/22, 11:28 AM, "Code for Libraries on behalf of Elizabeth Leonard" <[log in to unmask] on behalf of [log in to unmask]> wrote:

    We've been using LibAnswers and it hasn't been working. Every email sent to the system becomes a new ticket (even if it is from the same people on the same topic with the same subject line, etc.) From what Springshare has said, it isn't Springshare's fault. They have said that the way our email server manages headers is cutting off vital information that LibAnswers uses to decide if the ticket is new or not. Our IT department disagrees. Springshare's solution has been to tell us to only respond to the ticket within the LibAnswers interface. Not realistic.

    The system seems to work fine when it is a single reference librarian chatting with a single end user. But for some reason, the multiple stakeholders aspect of our tech issues just doesn't work.

    We had ZenDesk prior but the cost was prohibitive and they kept changing the cost structure, and charging more for less services.

    Regardless, we are now looking for a new ticketing system. 

    Elizabeth

    Elizabeth Leonard
    973-761-9445

    -----Original Message-----
    From: Code for Libraries <[log in to unmask]> On Behalf Of Matthew Adair
    Sent: Wednesday, May 4, 2022 9:04 AM
    To: [log in to unmask]
    Subject: [CODE4LIB] Email ticket system

    Greetings everyone -

    We're looking at implementing an email ticket system for our Library (well, technically we're an archive, despite the name.) We would be interested in hearing what systems other institutions are using and their experiences with them. Right now, our strongest candidate is LibAnswers from SpringShare. So far, most of the other systems we've looked at are geared towards IT or Business/CRM.

    As we've been investigating, a couple of  important pieces of context that have cropped are:

       - We are an independent unit at the University of Michigan. A lot of
       special collections / archives tend to be part of a larger library at their
       respective institutions, but we are not.
       - As an archive, we are non-circulating

    Thanks!
    - Matt
    ----
    *Matthew Adair*
    Lead Archivist for Digital Imaging and Infrastructure


    Bentley Historical Library
    1150 Beal Avenue
    Ann Arbor, Michigan 48109-2113
    734-647-3537
    https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbentley.umich.edu%2F&amp;data=05%7C01%7Chaitzlm%40UCMAIL.UC.EDU%7Cd85a27d854fa4ac89cbf08da2de2b959%7Cf5222e6c5fc648eb8f0373db18203b63%7C1%7C0%7C637872749148918467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=ynBzj4uMXviNM8iLr5c3Hroy%2FUJVh9wV2C%2BL%2F1tVAgQ%3D&amp;reserved=0
    @UmichBentley

    *The Bentley Historical Library acknowledges that coerced cessions of land by the Anishnaabeg and Wyandot made the University of Michigan possible, and we seek to reaffirm the ancestral and contemporary ties of these peoples to the lands where the University now stands.*
    ** WARNING: This email originated from outside of Seton Hall University. Do not click links or open attachments unless you recognize the sender and know the content is safe. **