Escalation Process

Escalation Path


The BAAR Support escalation process ensures that BAAR provides customers and partners with the means to give an issue broader attention. We are committed to delivering high-quality support to all our customers and partners. If you need to escalate a case, our technical team is ready and available to help you quickly bring your issue to closure.

Our efficient escalation management process is designed to keep you informed of your escalated case status at every step of the way. A lead and/or
manager is assigned to every escalation to oversee the case from a holistic viewpoint. This member is responsible for evaluating the situation, facilitating the issue, and acting as an advocate on your behalf.

Types of Escalation

Escalations occur in support centers for a variety of reasons. An escalation management system allows an organization to identify, track, monitor,
and manage situations that require increased awareness and swift action. BAAR provides our customers and partners with the two types of escalation described below.

2.1 Functional Escalation

We use this process when the BAAR Support team is unable to resolve the issue or stay within the agreed timeline (meaning, the targeted time for resolution is exceeded). We assign the issue to another team based on the skill set required to resolve the issue.

2.2 Hierarchical Escalation

We use this process as a communicative means to inform all the parties involved in a proactive manner of a potential SLA breach.

The essence of our escalation management is to bring order, structure, focused management attention, and additional resources to those customer situations which could otherwise result in a high level of customer dissatisfaction and/or damage to the service provider’s reputation.

Escalation Process Overview

When Should an Escalation Be Initiated?

For customers and partners who hold a valid support services contract, an escalation may be initiated anytime after the SLA response time. If you have worked through our standard support processes and with our teams and you are not satisfied with the level or timeliness of service you received, you can escalate accordingly. Additionally, an escalation should be initiated when there is tangible impact to your production environment, or there is high risk to the business operations.

Listed below are some examples of reasons to initiate an escalation:

What Is the Process for Escalating My Case?

The entry point into the BAAR escalation process is through your support case. Please note that for an issue to be escalated, a support case must be
created (we will not accept escalations solely based on communications via email). The reason behind this is to get multiple teams involved if need be in a consolidated manner. All communication between the engineer and case owner from the conception of the case should be documented within the case notes so all involved teams can view the progression of the issue.

This is the normal process for a support case:

The Support Engineer will come to a solution most of the time, sometimes after discussion with a Technical Support Lead and, if needed, with our second-line team (for the BAAR Studios, Client, Core, or Expert Services).

If the gap between the customer’s expectation and the BAAR Platform possibilities cannot be resolved, an escalation is started.

How Can I Escalate My Case?

1. Via Email

Send an email to [email protected] (and CC your Customer Success Manager). Ensure you add the following details to your email for an effective event-based escalation process:

2. Through the Support Ticket

In the case notes, CC [email protected] and in the case note, do the following:

What Can I Expect During an Escalated Status?

You will be contacted by the assigned Lead or Manager and we will collaborate and develop a communication plan. As needed, a technical plan of action will be co-developed to ensure resolution of the issue. The Lead or Manager will also update your account team (Customer Success Manager and/or Account Executive) of the case progression. The assigned Leads will work as advocates internally and become a virtual member of your own problem-resolution team.

What Criteria Does BAAR Use to Close My Escalation?

An escalation will be considered closed if it meets one or more of the following requirements:
As part of our continuous improvement process, your escalation will be documented and reviewed to help BAAR determine the steps that led to the escalation and how to avoid the issue from reoccurring.

De-Escalation Process

Once resolved to the customer’s satisfaction, the situation is monitored for an agreed-upon period. The escalation team remains on standby and available in case the problem reoccurs during the monitoring period.

The de-escalation process follows these steps:

We use cookies to ensure you get the best experience on the BAAR Technologies website, to help us understand our marketing efforts, and to reach potential customers across the web. You can learn more by viewing our privacy policy.