Creating a Support Ticket Sample Clauses
Creating a Support Ticket. The Supplier will use their ticketing portal, to ensure that the Supplier is aware of any/all issues, can ensure that matters get dealt with promptly and provide the Customer with an initial point of contact for all issues. Once a ticket has been logged with the Supplier, it will then be assigned to the most appropriate consultant. An Incident is defined as an event where it is not a standard operation of service for live and implemented modules. A request is for minor changes, enhancements or any other required operation not classified as an incident. When an incident has arisen that is identified as an issue with the actual implementation, the Supplier will highlight this.
Creating a Support Ticket. The Supplier will use their ticketing portal, to ensure that the Supplier is aware of any/all issues, can ensure that matters get dealt with promptly and provide the Customer with an initial point of contact for all issues. An Incident is defined as an event where it is not a standard operation of service for live and implemented modules. A request is for any other required operation not classified as an incident e.g. a query. Exports of the current list of open tickets, their current statuses and owners are also available on request.
Creating a Support Ticket. The Supplier will use their ticketing portal, to ensure that the Supplier is aware of any/all issues, can ensure that matters get dealt with promptly and provide the Customer with an initial point of contact for all issues. Once a ticket has been logged with the Supplier, it will then be assigned to the most appropriate consultant. An Incident is defined as an event where it is not a standard operation of service for live and implemented modules. A request is for minor changes, enhancements or any other required operation not classified as an incident. When an incident has arisen that is identified as an issue with the actual implementation, HPS will highlight this.