What happens when I raise a support case? (Article)

This article is aimed at both new and existing users of the Support Helpdesk.

Introduction

The Services Team are available for support by raising a request at support.talis.com. We are here for those small questions, reporting errors or wanting to know about how we can help you with training or consultancy.

Status

if you have an issue with either Talis Aspire Reading Lists or Talis Aspire Digitised Content, then first head to status.talis.com to see if it is already a known issue and what the latest advice is. If you don't see it there then please do raise a support request.

Ticket Received - 1st Line (Support)

1st Line (Support) will assess the information in the ticket and possibly ask for more information. We aim to be able to view the issue first hand or to recreate the issue. Where you are requesting changes to your tenancy configuration, we will let you know when we have completed the change, or ask for further clarification or detail prior to making the change. To speed up our investigation and get us closer to resolution we ask that you include the following details in each support case:

  • A summary of the task being carried out.
  • Where errors messages appear, we ask that you take a screenshot the error or copy and paste the error text into the support ticket.
  • The Browser and version being used.
  • The Operating System and version being used.
  • If the issue is concerning bookmarking, we ask that you provide a URL of the source (the webpage where the Add to My Bookmarks button is clicked) and also the URL of the created Bookmark if it has been achieved. If the bookmark could not be created satisfactorily, send us the URL of the bookmarklet page which shows the preview on the right and the bookmark fields on the left.
  • If the issue is concerning a certain list, the URL of the list.
  • If the issue is concerning a specific user or group of users, we need user details in order to investigate or create a service login to enable us to recreate or view the issue as the user.

Service Login (copy and paste the following in the support ticket)

Where possible we try to resolve your issue in 1st Line (Support) by providing clear advice, and point you to useful information on the knowledge base. Where further investigation is required by our technical team the ticket is assigned to Tech Team and the Stage set to 2nd line (Triage), you are informed at this stage.

What priority should I give a ticket

Here is what we suggest in terms of Priority choices.

  • Low: Affecting a small number or 1 user, it is not stopping workflow as you can work around the issue, and is not time bound.
  • Normal: Affecting more than 1 user but is not stopping the use or access to reading list or digitisations, but is having a small impact on workflow.
  • High: Affecting all or many users, it is stopping access to/hindering access reading lists or digitisations, or is stopping workflow which is time bound, in the run up to a key period like the start of the academic year.
  • Urgent: System down/can’t login preventing access to any reading lists and/or digitisations.

If we adjust the priority we will advise you likewise you can add more detail on the impact the issue is having in order to justify you priority decision, this will be taken into account.

Viewing an existing or closed support case

  1. Log in to the support portal.
  2. Select 'Check your existing requests'. You will be shown your open requests.
  3. To view your closed requests, select 'View your recently solved and closed requests' from the right hand panel.

Adding a comment to an existing support case

You can add a comment to an existing support case or respond to a comment made by a support operator, in two ways:

  1. Log in to Support.
  2. Reply to the "Request confirmation" email you received when submitting your request, or to any subsequent email alerts from the support operator.  Note: Ensure you write your text above the "Do not write below this line".

Moving the ticket to Triage and Queued for Development

Tickets are looked at by the technical team to assess the issue and the information provided, they are generally viewed in priority and chronological order unless a potential customer wide or high impact issues take priority. Tickets assigned to Triage can either be solved or move onto Development or it is logged as a Known Defect. Queued for Development is there in order for an identified fix for the issue to be developed, it could be that a code line change is needed or the issue requires more effort to resolve.

Known Defect what does that mean?

For issues that you have raised that are known defects, and are currently not prioritised for resolution, Talis will be closing these support cases with the status of ‘known defect’. These cases have been noted for development work, and once it is completed we will open a new support ticket to notify you directly.

If this issue is having a significant impact on the way you, or your colleagues work, and you would like Talis to review the priority of scheduling this work, please do respond to this support ticket, otherwise it will close in 10 days.

Our aim in this change of process is to be clearer on the issues that you raise that we are working to address, versus those that we feel are low impact, and currently not prioritised. If you would like to discuss this change of process, then please do email Alison Spencer and reference this support case number.

My ticket is 'Pending' what does that mean?

This will mean we are waiting for more information from you in which case you need to respond to the support case when you have the information we require. Or the ticket is set to Pending Closure so we will have advised that the ticket will close within 7 days, if all is fine you can just leave the ticket to close, or respond if you have further issues.

My ticket is 'Open' what does that mean?

This usually means the issue is with us and we will be taking action. However if you have responded to a Pending ticket to simply say you are waiting for a user to get in touch with the details this will also set the ticket back to Open, though the response is still waiting from you.

My ticket is 'Solved' what does that mean?

This means we believe the issue to be solved or the question answered. If this is not the case simply respond with further information.

My ticket is Solved and I’m being asked to rate the service, what am I rating?

You are rating the service you have received in dealing with your ticket you are not rating the product.

How can I escalate a ticket?

If you feel your ticket is not being dealt with correctly or the issue reported is urgent or time bound you can escalate the ticket. To escalate please email Alison Spencer with your ticket details detailing your concerns and telephone number, we will then work to review the issue and prioritise as appropriate, before updating you directly. We also are happy to arrange a catch up call with each University and you can raise concerns or discuss tickets of note as part of that call, if you haven’t had a call with us recently please do log a ticket and we will be touch to arrange.

24/7 monitoring

Talis has a full 24/7 service monitoring and alerts in place, so if there were to be an issue that effected the service, the wider Talis team are in place to respond, and resolve this issue as quickly as possible limiting any impact to service. This monitoring is in place for both Talis Aspire Reading Lists, and Talis Aspire Digitised Content. This is always in place even when the services team are not available due to bank holidays.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk