Sunday 28 October 2012

Text enquiry service for Student Information Points


Text enquiry service for Student Information Points

In addition to the face to face enquiry service that we offer at the Student Information Points we are developing a number of other channels of communication and delivery. We don't offer a telephone service at present but we do offer an email service. Students can email infopoint@ed.ac.uk with enquiries about anything and we will email them back as soon as possible which is usually within an hour.
Also we have now developed and launched a text service. This means that students can text their enquiry to a number and they will receive a reply asap - we will aim for an immediate response between 9.00 - 5.00 Mon - Fri. To send an enquiry, text SIP then a space then the enquiry to 07950081379

Basically the text service uses txttools which is now Blackboard ConnectTxt. I've used it before in my previous job and most of the system was already set up at the University of Edinburgh and it just required a few additions to make it 'two way'. It is most commonly used to text out - to send students messages about their course, assignment dates, cancelled lectures, upcoming events etc. But it can be set up and used for incoming text messages which is how we are using it for the Student Information Points.
The texts can be sent and received through the web interface which is simple and straightforward to use. (It is possible to use the text through a Blackboard building block although this used to be a little slow but may have improved now). We have had the system set up so that the texts come into the Outlook email inbox and are replied to as an email which then appears as a text to the enquirers phone. It's a fairly simple system that works well. The advantage of the texts coming to the Outlook email are that they can be processed by the same person and in the same way as any email enquiries. Also you don't have to be logged into the ConnectTxt web site as the text will just appear in your inbox. This also provides a way of tracking any text replies so that they can be retrieved and followed up at a later if necessary.

So the text service is live and it will be interesting to see how it is used.  Text messaging is to some extent an old technology as it has been in common usage for at least 10 years but I think it is one of the best forms of communication technology that there is or ever will be.  It is simple, effective and used by almost everyone.  I don't think it's use as part of the enquiry service will have a mass take up but I think there will be some use and also it is important to provide choice and convenience.  If you have a question then the quickest and simplest way to get an answer is to text particularly if you are on the move.

The use of text as an incoming service also addresses another important issue which is the overwhelming amount of information that is 'pushed' at students.  Day be day the amount of communication is increased and we are at the tipping stage of information overload.  This is being recognised by institutions and universities and communications policies and practices are high up on the agenda for review.  But by providing a service that students can easily access but 'pull' when required has a certain appeal.




3 comments:

  1. We've finally extended our text enquiry service to send out nearly due notifications for books. For our students this is more popular, we have more responses to that than students texting us with enquiries.

    It is working well, apart from an odd glitch when the LMS tries to send the phone numbers to the wrong folder but we are working with IT to get that sorted.

    The response we have had is really good, within seconds of the texts going, we have 5-6 replies asking for books to be renewed. I want to extend it again to reservations and possibly 1st stage overdue notices.

    I haven't had chance to see if it has led to a reduction in the amount of outstanding stock, which is what I am aiming for but I think that the ease of the system appeals to the students - all we ask to renew their book is that they text back their College ID number, it's simple, streamlined and takes up little time.

    I have recently been reading a book about the use of mobile technology in libraries and it was saying that the use of texting within library services is underused and that (based on focus group response)students are happy to receive text messages so long as they are of some immediate benefit and use to them. I think that the nearly due notifications supports this.

    ReplyDelete
  2. That's great and an excellent example of using text messaging for timely reminders. Did the texts go straight from Heritage or do they have to feed into txttools then out as a text or email? Can students reply to the text to renew the book?

    ReplyDelete
  3. This sounds slightly clunky but it is really quick. Heritage automatically runs a report (before we start work)for the phone numbers of people with books due the next day we are open. It sends the information to a csv file (because Heritage won't export in Excel format). We have to pick that information up, copy & paste into Excel (we have a dedicated spreadsheet), set up to concatenate the information into an e-mail address. We copy & paste those e-mail addresses into the LRCinfo account, put a set short message about books being due back the next day and how to renew via text. That gets pushed out through txttools.

    It goes as a text, students then text back their Learner ID, which comes through txttools again to the LRCinfo account. We also have set responses, so if the books are renewed the only thing we type in is the new due date or if the books can't be renewed, we say sorry and can they bring the book in - we don't have space to say why. We give the reply responsibility to a person on a specific enquiry desk. I, at the moment, do all the rest but that's just because I want to monitor that the glitch doesn't reoccur. Once I'm happy that is resolved, i'll delegate it (probably as part of the overdue process).

    ReplyDelete