Issue Classification Schema
Customer Support classifies each service request using two qualifiers:
This classification schema is the cornerstone around which all support processes flow. The business rules on which they are built is monitored by Salesforce to ensure service levels are enforced and that Management is aware of concerns before they escalate.
Severity
The Severity of a service request refers to the impact to the customer of the issue on our customer base. It categorizes the technical issue in terms of the effect it has on the application’s operation. The Severity is based on objective observations, its value remains the same throughout the life of the support case, unless circumstances dictate otherwise (such as an issue propagating to a larger customer base or affecting other components of the application not discovered at time of reporting the issue).
Severity Level |
Definition |
Can be set by |
S1- Critical |
Critical Service Impact
|
Team Leader+ |
S2- High |
Major Service Impact
|
Team Leader+ |
S3- Medium |
Minor Service Impact
|
All |
S4- Low |
Minor Service Impact – Workaround available
|
All |
S5 – Request / Customer Education |
No Impact Design or usability query
|
All |
Priority
The Priority of a Service Request is a subjective value that refers to the degree of urgency in which the issue must be resolved. This value drives our internal escalation management process. The Priority changes to appropriately reflect the severity of the issue.
Every Severity level has a corresponding default priority level, but priority allows for some input from human and business needs. Problems with low severity can easily get assigned a higher priority should the need arise. For example, if we have a simple typo on a customer’s page, that's Severity 4 because of its low scope, but if that page is their home page and the typo is in their company name, it may be a Priority 1 problem.
The default priority levels for the various Severity levels are shown below:
Severity Level | Priority Level |
S1 | P1 |
S2 | P2 |
S3 | P3 |
S4 | P4 |
S5 | P5 |
In order to change a priority level from its default level, a business case must be presented and approved through appropriate channels.
The table below provides definitions for the various Priority levels.
Priority level |
Definition |
Can be set by |
P1 – Critical |
Priority is so high that issue needs to be addressed immediately. Examples include:
|
Team Leaders+ |
P2 – High |
Give High Attention Example: Sensitive customers |
Team Leaders+ |
P3 – Medium |
Normal Queue Example: Day to day issues |
All |
P4 – Low |
Low Priority
|
All |
P5 – Waiting / No priority |
Waiting / No Priority
|
All |