meebome can be monitored through an im client that can connect to an xmpp server (like pidgin or trillian pro). you’ll need a special pidgin plugin to automatically accept requests from meebome patrons, though some report problems (http://libraryvoice.com/archives/2007/09/26/problems-with-pidgin-and-meebo-or-the-chocolate-has-melted-a-little/)

also see libraryh3lp, in development at UNC (sort of):

– as many concurrent users as you want
– as many librarians as you want
– not-flash-based – javascript interfaces nicely with mobile devices
– fully customizable style with css
– maybe not free in the future, but cheap ($100-$300/yr)
– librarian monitors through xmpp-based im client like pidgin
– goes away when you browse away

sample: http://www.oregonlibraries.net/libraryh3lp_webchat_test
project site and instructions: http://code.google.com/p/libraryh3lp/

and also new “qwidget” from oclc questionpoint

– as many concurrent users as you want
– as many librarians as you want
– not-flash-based – javascript interfaces nicely with mobile devices
– some customization
– for oclc questionpoint customers only
– not yet 24/7
– librarian monitors through oclc questionpoint interface
– patrons leave message if chat is unavailable
– goes away when you browse away

sample: http://www.oregonlibraries.net/qp_chat_widget

I’ve also been encouraging libraries to show a link to our 24/7 service if staff on the widget are unavailable:

western oregon university – http://www.wou.edu/provost/library/
central oregon community college – http://campuslibrary.cocc.edu/