Skip to main content

New Black helpdesk

New Black has a helpdesk to support with whatever questions or issues you might have. Please read this document VERY carefully as this outlines how support tickets should be submitted.

New Black support engineers expect a certain quality of tickets. This quality ensures our engineers can get to solving tickets as fast as possible, without first having to increase the ticket quality. A decent support tickets consists of three parts:

  1. Context
  2. Details
  3. Correct priority

Context

When submitting a ticket, you are first presented with an array of fields to fill out. These fields are designed to give us an idea of the context within which your ticket exists. Having this context again helps us towards a solution faster. Fill out as many fields as you possibly can, skipping some fields for the sake of time will negatively impact the speed with which we can help you.

Details

After all contextual fields, tell us your story. Describe exactly what is wrong, and give as many details as you possibly can gather. These details include, but are not limited to:

  • application version numbers
  • EVA version numbers
  • Order ID's
  • Organization Unit ID's
  • Timeframes
  • User ID's

If you can manage, include the service names, requests and responses that are relevant to your issue. If your error occurs in any web-based application;

  • Right-click your browser page
  • Select Inspect
  • Navigate to the Network tab
  • Perform your blocked operation again

The service that gives you an error will be marked red. Clicking this service will allow you to view its headers, request and response. Include these in your support ticket.

Correct priority

Prioritization is probably the most important setup when submitting a support ticket. Although every issue is important, some are more urgent than others. To ensure the best possible response time and resolution for your support tickets, make sure to set the correct priority on your ticket.

We have four levels of priority:

  1. Urgent
  2. High
  3. Medium
  4. Low

In order for us to handle all tickets according to their correct priority and/or impact and meet expectations, we need to agree on some clear guidelines regarding picking a ticket priority. To keep it simple, we've set up the following chart for guidance:


Note

Before disregarding all above steps and just opting for Urgent make sure to read "The Boy Who Cried Wolf".

Submit a ticket

Additional information

Response times

PriorityFirst responseWorkaroundResolution
Urgent30 minutes2 hours4 hours
High2 hours-Best effort or next business day.
Medium4 hours-Best effort or within 2 business days.
LowNext business day-Best effort or next sprint.

Region abbreviations

Region abbreviationActual endpoint
ASEAsia
CUSUS and Canada
EUWEurope
GWCGermany

Environment abbreviations

Environment abbreviationActual endpoint
PRODProduction
UATUser acceptance
ACCAcceptance
TESTTest
DEVDevelopment