Skip to content

DSP - Customer Escalation Process

Standard Operating Procedure

January 2025 - V1.2

Paul Akester - Service Delivery Manager

Kevin Blackshaw - Group Head of Service Management 

Review Cycle - Annually - Q1

Partner Logos

Document Control

Confidentiality and Copyright

The information contained in this document is confidential and is issued by DSP on the understanding that it will be used only by the staff of, or consultants to, the Client and where consultants are employed, the use of this information is restricted to use in relation to the business. In particular, the contents of this document may not be disclosed in whole or in part to any other party without the prior written consent of DSP © - Database Service Provider Global Limited. All rights reserved.

Validity of Information

DSP has made every effort to ensure that all statements and information contained herein are accurate as per the document release date. Any questions regarding the content of this document should be directed to our Service Delivery Department - ServiceDelivery@dsp-explorer.com

Change Control History

Version Date Update Owner
1.0
08/07/2022
Document - Live
KB
1.1
08/07/2022
Typo Correction to Section 2.4 and amended to section 3 flow chart
KB
1.2
31/08/2022
Emphasis of customers calling the Service Delivery Team for out of hours escalation added
KB

Document Review

Reviewers Date Update Owner
KB/PA
19/12/2022
Review complete - No changes recommended
KB
KB/PA
12/09/2023
Review Complete - No changes recommended
KB
KB/PA
18/03/2025
Review Complete - 1 diagram removed no additions to Process
KB

Section 1.0 - Overview

This document defines the DSP standard operating procedure (SOP) for Customer Escalations.

To ensure DSP are able to provide the best quality of service to all customers DSP urge all customers to consider which type of escalation best suits their needs prior to making an escalation (Section 3 – Quick Reference Guide).

One of the challenges all Managed Service Providers face is lower priority escalations consuming time that can be optimised to deal with urgent issues. If a customer is chasing an update on a ticket for example or a resource booking it is possible an email or update to the relevant ticket would suffice as a request for information rather than an escalation via phone or multiple entry points into DSP.

However, DSP accept that on occasion significant events do require direct / telephone escalation such as -

  • Major Incidents where a business is facing financial loss, reputational damage, or an interruption to critical business processes (such as payroll) – P1 Only
  • Incidents where resolution within SLA or prescribed timeframe is required to prevent financial loss or disruption to critical business processes – P2 or P1 Only
  • A change to planned work with limited time to inform DSP

Section 1.1 – Exclusions

DSP Technical Resources will not respond to initial escalations or to events where a ticket has not been raised either via email or in real-time chat tools and are actively encouraged to channel all customer escalations in accordance with this Process (Section 2). This is to ensure DSP can provide the correct response, level of visibility and tracking of escalated issues within the business.

However, once an issue is live, escalated, and visible within DSP, DSP encourages direct communications with technical resources where required to resolve urgent customer issues.

Section 1.2 – Portal Limitations Regarding P1 / Major Incident

A customer cannot raise a P1 directly via the ITSM Toolset Portal. This is by design to prevent tickets being raised incorrectly as a P1. Should P1 priority be required we ask that DSP customers detail the requirement for P1 status within the ticket and phone DSP as per section 2.2.1.

Section 1.3 – Email Ticket Limitations

A ticket received by the ITSM toolset from a direct email will always be raised at the default priority setting – P3. If the issue is more severe and the customer is unable to access the ITSM portal or needs to confirm P1 issue – please escalate the ticket as per section 2.2.1.

Section 1.4 – Account Management

Please note for all operational and technical issues the customer’s Account Manager should not be viewed as an escalation point. Only where the customer has a commercial escalation (see section 2.4) should the Account Manager be contacted. Commercial Escalations are serviced during UK Business Hours Only.

Section 1.5 – Escalation Process Validity

Please note this escalation process supersedes all previously released DSP Escalation Process documents and was made live by DSP in July 2022.

Section 1.6 – Before Performing an Escalation

Before performing an escalation (see section 2 for guidance) please ensure:

  • Where possible there is a ticket raised within the DSP ITSM Toolset and the reference number is available
  • The ticket is raised at the correct severity / priority level (for P1 incident tickets see Section 1.2)
  • Ensure the business impact is understood and the reason the event needs to be escalated is articulated to DSP
  • The main contact for the issue is known, articulated to DSP and available for any follow-up actions
  • Consider if other members of your organisation need to be added to the ticket watchlist at the point of escalation to ensure timely ticket updates are received by the correct audience
  • If you are requesting a call-back at the time of escalation that is communicated to the call handler
  • If corresponding via email – please ensure the correspondence is from a business email address. Emails from personal email addresses may not be responded to fully. If your email service is down as a result of the issue – please phone DSP directly -

Service Desk - phone published numbers

  • 0330 058 8367
  • 0203 086 7065

Section 2.0 - Escalations and Ticket Enquiries

Each of the sections below detail how a customer can perform an escalation at DSP. For a quick reference guide see Section 3.

Section 2.1 - General Escalations, Resource Bookings and Ticket Enquiries (Answered in UK Business hours) – Ticket Severities – P2 to P5

For General Escalations, resource booking enquiries and requests for information please ensure that the corresponding ticket has been updated where possible (see section 4 for DSP guidelines as to how to write a ticket escalation).

If there has not been a timely response to a ticket or the ticket cannot be updated, general ticket escalations and requests for updates should be carried out by emailing Service Delivery using the following email address: servicedelivery@dsp-explorer.com

This is for non-urgent queries and will only be reviewed and acknowledged during standard UK Business hours

Section 2.2 - Urgent Escalations and Ticket Enquiries (24x7x365) – P1 / Pending P1

Section 2.2.1 - 1st Level Escalation (24x7x365)

To escalate a ticket requiring urgent action please contact on one of the published numbers below. Your call will be handled by one of our service delivery team and will engage with the relevant technician.

Should the severity of the ticket need to be increased please discuss this with your call handler who may increase this should it fall in line with the defined impact and urgency matrix.

Where possible customers are asked to detail the escalation within the DSP ticket (section 4).

Please note, when escalating a ticket outside of UK business hours customers must phone the DSP Service Desk number as well as updating the ticket / emailing.

Service Desk - phone published numbers

  • 0330 058 8367
  • 0203 086 7065
Section 2.2.2 - Major incident escalation and awareness (24x7x365)

If a customer is experiencing a major incident and further engagement is required, please contact the DSP Service Desk who will engage with the assigned technical resource. The DSP Service Desk will also escalate to the DSP Major Incident Manager.

Where possible customers are asked to detail the escalation within the DSP ticket (section 4).

Please note, when escalating a ticket outside of UK business hours customers must phone the DSP Service Desk number as well as updating the ticket / emailing.

Service Desk - phone published numbers

  • 0330 058 8367
  • 0203 086 7065

Section 2.3 – 2nd Level (Management) Escalations (24x7x365)

DSP provide a 2nd Level Escalation (or management escalation) that can be used by customers in the event a 1st Level Escalation has not provided the necessary results in line with customer expectations.

Should a 2nd Level Escalation (or management escalation) be required, DSP requires customers to contact the Service Desk stating the reason for a 2nd level escalation. The Service Desk will work with the customer to help direct the 2nd level escalation to the correct manager within DSP.

All 2nd Level Escalations are reviewed by the Managed Services Management Forum lead by the Head of Managed Services.

Should the escalation require executive involvement, this will be managed on your behalf by the Head of Managed Service. Your account manager will be notified for awareness only however they will not have direct involvement in any technical escalation.

Service Desk - phone published numbers

  • 0330 058 8367
  • 0203 086 7065

Section 2.4 - Commercial Escalations (UK Business Hours)

Should there be any commercial escalations, these will be managed during UK business hours only by a customer’s account manager. Customers are recommended to email their account manager regarding commercial enquiries. If a customer is unaware of their account manager’s details – they are advised to request the details of their account manager from Service Delivery (servicedelivery@dsp-explorer.com). Customers do not need to detail your commercial question to Service Delivery and can ask directly for the details of their account manager. Unfortunately, any emails from personal email addresses will not be provided with account manager details.

Section 2.5 - Technical Escalations - for in-flight Incident or Service Request chases and escalations (24x7x365 – P1 / UK Business Hours Only – P2-P5)

To obtain updates on ticket progress please add an entry to the corresponding ticket via the ITSM Portal as the first action. Should a technical resource fail to respond in a timely manner please contact the Service Desk. They will attempt to connect you to the technical expert working on your case. Should this not be possible during the call they will arrange for the technical expert to contact you at the earliest opportunity. The Service Delivery team will also inform the corresponding team lead should the ticket need to be re-assigned to another technical resource.

Service Desk - phone published numbers

  • 0330 058 8367
  • 0203 086 7065

Should you believe the incident requires additional focus you will be put in contact with the Team Lead for the appropriate team and, should they not be available you will be contacted by the DSP Service Delivery Manager who will ensure the matter is progressed.

Where possible customers are asked to detail the escalation within the corresponding ticket within the ITSM portal using the escalation template (section 4).

As stated in section 1.1 Exclusions - DSP technical resources should not be viewed as the first point of contact for new escalations or events prior to a ticket being raised and, are advised to direct customers raising new escalation to follow the DSP Escalation Process.

Section 2.6 – Change to Planned Activity Notification

Section 2.6.1 – More Than 48 Hours’ Notice (UK Business Hours)

Where a customer needs to make a change to planned activity and is able to provide DSP notice greater than 48 hours, DSP recommend the following actions –

And/Or

  • Ticket Update in the ITSM Portal where access is available
Section 2.6.2 – Less Than 48 Hours’ Notice (24x7x365)

With less than 48 hours' notice both actions from 2.6.1 can still be carried out. However, to ensure that DSP are able to respond and prevent any further issues we ask that DSP customers contact the Service Desk by telephone.

Service Desk - phone published numbers

  • 0330 058 8367
  • 0203 086 7065

Section 3.0 – Quick Reference Guide

Section 3.1 – Quick Reference Guide – Tabulated with Document Section References

Shown below is a high-level summary of section 2 to act as a quick reference guide for DSP customers. This is presented graphically in section 3.2.

Required DSP Escalation Recommended Customer Action DSP Operating Hours Next Level Escalation Document Section
Ticket Update
Update Directly in Customer Support Portal
UK Business Hours Only
1st Level Escalation via telephone
(Section 2.2.1)
Section 2.1
Ticket raised either via email or the portal that needs to have its priority increased to P1
1st Level Escalation via Service Desk Telephone
24x7x365
2nd Level Escalation
(Section 2.3)
Section 2.2.1
Major Incident - P1
MI Escalation via Service Desk Telephone
24x7x365
2nd Level Escalation
(Section 2.3)
Section 2.2.1
Event likely to become P1 if not resolved - P2/P1
1st Level Escalation via Service Desk Telephone
24x7x365
2nd Level Escalation
(Section 2.3)
Section 2.2.1
Commercial Escalation
Email Account Manager (Account Manager details can be obtained from the service desk)
UK Business Hours Only
Email the DSP Service Desk with the request of whom to contact in the absence of the Account Manager
Section 2.4
Technical Escalations
Update event ticket directly in Customer Support Portal
24x7x365 (P1)
UK Business Hours Only (P2-P4)
1st Level Escalation via telephone
(Section 2.2.1)
Section 2.5
Change to Planned Activity greater than 48 hours notice
Update Directly in Customer Support Portal
UK Business Hours Only
1st Level Escalation via telephone
(Section 2.2.1)
Section 2.6.1
Change to Planned Activity less than 48 hours notice
Escalation via Service Desk Telephone
24x7x365
2nd Level Escalation
(Section 2.3)
Section 2.6.2
2nd Level Escalation
Escalation via Service Desk Telephone
24x7x365
Executive Escalation - DSP Initiate Only
Section 2.3

Section 4.0 – Information Required for Written Ticket Escalation

When performing an escalation DSP always recommend that where possible a customer adds a written escalation note within the DSP ticket as well as by telephone. This increases the visibility of the escalation within DSP and allows DSP to maintain a complete timeline of events and an accurate and up-to-date knowledge base.

When performing a written update DSP recommend the following format for an escalation (this can be copied and pasted from this document acting as a template for the ticket entry).

 

******************* Escalation Request *******************

Current time: [DD-MM.YYYY HH24:MI]

Reason For Escalation:

Business Impact:

Ask: (Examples include – call back from engineer / Manager Attention / Update / Teams Meeting request etc)

Name of the customer performing an escalation: Name / Contact Number / Email Address

Name of the customer requesting call back if required: (Can differ from the person performing the escalation and should include contact number / email address)

******************* Escalation Request *******************

Please note, when escalation a ticketing outside of UK business hours customers must phone the DSP Service Desk number as well as updating the ticket / emailing.

Customer Support Portal

Our Customer Support Portal is where you can raise and track incident and service requests.

Click the button below to access our Customer Support Portal, and continue down the page to watch short videos on the platform. Videos include a 'Customer Support Portal Overview', 'How to raise an incident' and 'How to raise a service request'.

Customer Service Manual

The purpose of this document is to welcome you as a new customer to DSP's Managed Services and provide you with some practical information about getting started on using the services you have purchased. Including how to raise incident and service requests.

 

Monitoring Set-up Requirements

Key items required to configure our monitoring product are detailed within this document.

Meet the Customer Excellence Team

At DSP, we have a dedicated team to ensure our customers are happy with the service we're providing. If you'd like to meet with the team, get in touch today!

Did you know we do more than Managed Services?

Professional Services

Application Development

Data Science