# data[].attributes.body
Noise for internal chats

Option for selecting more than one internal member of staff to talk to (but not all)

iFrame explanation and quick launch similar to ask for contact details

# data[].attributes.body
LibWizard forms v LibAnswers Forms

# data[].attributes.headline
Really useful to be able to have screensharing when on chat, particularly for queries regarding electronic resources access

# data[].attributes.subject
Really useful to be able to have screensharing when on chat, particularly for queries regarding electronic resources access

# data[].attributes.headline
Where is SpringShare is relation to working with QuestionPoint?

# data[].attributes.subject
Where is SpringShare is relation to working with QuestionPoint?

# data[].attributes.headline
Be able to do more customisation, more colourful etc

# data[].attributes.subject
Be able to do more customisation, more colourful etc

# data[].attributes.headline
The free version to allow for document uploads - I think this is only an option with the paid version

# data[].attributes.subject
The free version to allow for document uploads - I think this is only an option with the paid version

# data[].attributes.headline
in the new chat dashboard why does it say new chat when it is actually a new ticket

# data[].attributes.subject
in the new chat dashboard why does it say new chat when it is actually a new ticket

# data[].attributes.body
is Springshare consideringadopting anything that will check LibGuides etc according to W3A standards?

+ making image alt tags and descriptors a mandatory part of adding an image

# data[].attributes.headline
When transferring Chat disappears from everyone's queue except person accepting chat when transferred

# data[].attributes.subject
When transferring Chat disappears from everyone's queue except person accepting chat when transferred

# data[].attributes.headline
Set own default settings - notification for incoming tickets - have to change each time log in

# data[].attributes.subject
Set own default settings - notification for incoming tickets - have to change each time log in

# data[].attributes.body
How do people manage the upkeep of their FAQs? At Leicester we have assigned FAQs to individuals but with constant turn over of staff and re-training this is becoming challenging, does anyone do it another way?

# data[].attributes.headline
At Aston we use NORMAN for out of hours support.  Is there scope for integrating this with LibChat?

# data[].attributes.subject
At Aston we use NORMAN for out of hours support.  Is there scope for integrating this with LibChat?

# data[].attributes.body
In what ways are FAQs advertised at your institutions?

# data[].attributes.headline
Is anyone using the equipment booking add on module?  If so what for and how have you found it?

# data[].attributes.subject
Is anyone using the equipment booking add on module?  If so what for and how have you found it?

# data[].attributes.headline
We link to FAQs from the Library homepage under the brand of Ask the Library which has the LibAnswers homepage.  This is also the knowledge base for our evening team and out of hours service (Norman).  We also quote links to relevant FAQs when answering chats

# data[].attributes.subject
We link to FAQs from the Library homepage under the brand of Ask the Library which has the LibAnswers homepage.  This is also the knowledge base for our evening team and out of hours service (Norman).  We also quote links to relevant FAQs when answering chats

# data[].attributes.body
Thanks! Thats really helpful

# data[].attributes.headline
In chat it would be really useful if you had to click send to send the message rather than the message being sent as soon as you press return.  At the moment we often get a list of a few words where people have pressed return and it can also lead to a lot of information all in one big paragraph.

# data[].attributes.subject
In chat it would be really useful if you had to click send to send the message rather than the message being sent as soon as you press return.  At the moment we often get a list of a few words where people have pressed return and it can also lead to a lot of information all in one big paragraph.

# data[].attributes.headline
Is  there a way to more visually display database links in a LibGuide ?  At the moment adding a database link from the A-Z is just small wording we would like more visual display of a database link

# data[].attributes.subject
Is  there a way to more visually display database links in a LibGuide ?  At the moment adding a database link from the A-Z is just small wording we would like more visual display of a database link

# data[].attributes.headline
can libguides offer the display of 'new' and 'trial' items on the A-Z in two separate sections?

# data[].attributes.subject
can libguides offer the display of 'new' and 'trial' items on the A-Z in two separate sections?

# data[].attributes.headline
Students can book as many sessions as they want - could book a librarian out all day

# data[].attributes.subject
Students can book as many sessions as they want - could book a librarian out all day

# data[].attributes.headline
have settings  on for all or not at all - no individual option

# data[].attributes.subject
have settings  on for all or not at all - no individual option

# data[].attributes.body
feedback follow-ups extend from 1 week
Add attachments to send slides following workshops

# data[].attributes.headline
Option to swap shifts over different schedules?

# data[].attributes.subject
Option to swap shifts over different schedules?

# data[].attributes.headline
week 1 week 2 on schedule. Could there be more than 1 week for working hours section - staff works different hours each week

# data[].attributes.subject
week 1 week 2 on schedule. Could there be more than 1 week for working hours section - staff works different hours each week

# data[].attributes.body
Ability to customise the public facing time format so it's consistent with the system settings would be really helpful.

# data[].attributes.body
More options for classifying tickets - e.g. we could do with more than new, open, pending and closed.

# data[].attributes.body
more than 30 fields
current issue choices are set

# data[].attributes.headline
Advanced communcation of any changes/updates

# data[].attributes.subject
Advanced communcation of any changes/updates

# data[].attributes.body
how is libapps working to improve responsive web design (especially LibGuides)

# data[].attributes.headline
Various issues regarding new Chat interface - we will forward these to Springshare after the meeting

# data[].attributes.subject
Various issues regarding new Chat interface - we will forward these to Springshare after the meeting

# data[].attributes.headline
How would Springshare prefer us to send feedback / development ideas from the UK on various different Lib

# data[].attributes.subject
How would Springshare prefer us to send feedback / development ideas from the UK on various different Lib