Problem Management

Problem Management

Introduction

The following procedure ensures that we consistently manage client reported problems. A problem is defined as an issue that could lead to an incident, so it is important to understand whether the client has an issue or an incident – incidents are managed by a separate procedure, as they require a different response. Depending on the type of issue, the following resolution times apply:

Software unavailable                                                                                                      1 hour
Software partially available                                                                                          4 hours
Software feature does not perform as expected                                                48 hours
Software feature performs as expected but identified change                      1–6 months

Procedure

1.    Client logs problem

Problems can be logged using the embedded support form, email (support@gpbilling.co.uk), live chat or telephone (01534 607000). The service desk is available Monday to Friday 9am – 5pm with an out of hours P1/P2 engineer on call.

2.    Raise Ticket

Tickets are either raised automatically in Zoho Desk through the chat or support form in the application or by the product specialist taking the call. All problems must have a ticket raised.

3.    Ticket Responses

All responses to tickets must be tracked through the ticketing system, to ensure a consistent approach to quality and resilience.

4.    Open Tickets Must be Reviewed Daily

Reviewing open tickets will reveal trends and patterns and will ensure that service level agreements and contractual obligations are satisfied.

5.    Zoho Assist Should be Used to Provide Remote Desktop Assistance

Product Specialists should use Zoho Assist to support clients.

6.    Notifications to Be Sent to Clients Whenever A Status Change Occur

Clients must be informed, as problems are resolved, to ensure they are confident in the service.

7.    Problems That Cannot Be Resolved Within Contractual or Service Level Agreement Requirements Must Be Escalated to An Executive Director

This must happen promptly.

If You Are Unclear on What to Do.

You must contact your line manager for guidance.

Procedure Review

This procedure has been approved by an Executive Director and must next be reviewed by 31st May 2023.


    • Related Articles

    • Safety Management

      What is an Incident An incident is defined as a situation where information pertaining to a customer has been exposed to or accessed by an unauthorised third party or where a bug in the software has enabled a user to access information they were not ...

    • Incident Management

      Introduction The following procedure ensures that we consistently manage incidents. An incident is defined as an unplanned interruption or reduction in quality of a service, leading to services not functioning as expected. It is important that we ...

    • Change Management

      Introduction The following procedure ensures that we consistently manage change requests. A change request is defined as a request to modify a service. It is important that we handle these requests on a consistent basis, with appropriate oversight. ...

    • Account Management

      Each customer has an account in GP-Billing that holds a history of interactions. From the [Billing] dashboard, click the [View Account] button. Use the following buttons to find or add the customer account: [Sync Patient]                    ...

    • Online Training

      Training We can tailor training to suit availability of your resources and match roles within your Practice. Typically training follows these sessions: Session 1 (Up to 3 hours) Provide assistance with the installation of GP-Billing on your desktop ...