NexQloud Knowledge Base

Discover tailored support solutions designed to help you succeed with NexQloud, no matter your question or challenge.

A headphone sitting on top of a desk next to a monitor.
Knowledge Base
What qualifies as a critical or emergency support request?

What qualifies as a critical or emergency support request?

Understanding the criteria for critical and emergency support requests is essential for proper issue classification and ensuring appropriate response priority for your cloud computing platform incidents. NexQloud's severity classification system balances urgent business needs with resource allocation efficiency, ensuring that truly critical issues receive immediate attention while maintaining effective support for all customers. Proper classification helps ensure your business-critical problems affecting your decentralized cloud infrastructure receive the rapid response and specialized expertise required for timely resolution.

Critical Support Request Classifications:

  1. Severity 1: Critical/Emergency Issues
    • Complete Service Outage: Total platform unavailability affecting [Information Needed - critical outage user impact thresholds and business disruption criteria]
    • Data Loss or Corruption: Active data integrity issues with [Information Needed - data loss severity criteria and recovery urgency requirements]
    • Security Breaches: Active security incidents with [Information Needed - security breach classification and immediate response triggers]
    • Revenue-Critical Failures: Direct financial impact with [Information Needed - revenue impact classification and business continuity requirements]
  2. Severity 2: High Priority Issues
    • Major Feature Failure: Core functionality unavailability with [Information Needed - major feature failure criteria and workaround availability assessment]
    • Significant Performance Degradation: System slowdown affecting [Information Needed - performance degradation thresholds and user experience impact]
    • Partial Service Outage: Limited availability impacting [Information Needed - partial outage classification and affected user percentages]
    • Integration Failures: Critical third-party connectivity with [Information Needed - integration failure severity and business process impact]
  3. Business Impact Assessment Criteria
    • User Impact Scale: Number of affected users exceeding [Information Needed - user impact thresholds for critical classification]
    • Financial Consequences: Revenue loss exceeding [Information Needed - financial impact thresholds for emergency classification]
    • Regulatory Implications: Compliance violations with [Information Needed - regulatory impact criteria and legal consequence assessment]
    • Public Relations Impact: Brand reputation concerns with [Information Needed - PR impact assessment and public visibility criteria]
  4. Time-Sensitive Circumstances
    • Deadline-Critical: Issues blocking time-sensitive deliverables with [Information Needed - deadline-critical assessment criteria and business milestone impact]
    • Event-Related: Problems affecting scheduled events with [Information Needed - event-related issue classification and time-critical resolution needs]
    • Compliance Deadlines: Regulatory reporting impacts with [Information Needed - compliance deadline impact assessment and legal requirement urgency]
    • Customer Commitment: External obligation failures with [Information Needed - customer commitment impact and contractual obligation assessment]

Emergency Response Activation:

  1. Immediate Response Procedures
    • Emergency Team Assembly: Critical response team with [Information Needed - emergency team assembly procedures and expertise coverage]
    • Management Notification: Executive awareness with [Information Needed - management notification procedures for emergency issues]
    • Resource Mobilization: Priority resource allocation with [Information Needed - emergency resource mobilization and team coordination]
    • Communication Protocols: Stakeholder updates with [Information Needed - emergency communication procedures and update frequency]
  2. Emergency Support Features
    • Dedicated Phone Line: Emergency contact with [Information Needed - emergency phone line availability and direct access procedures]
    • After-Hours Support: 24/7 emergency coverage with [Information Needed - after-hours emergency support availability and response guarantees]
    • Priority Queue: Immediate attention with [Information Needed - emergency priority queue procedures and response time guarantees]
    • Executive Escalation: Rapid management involvement with [Information Needed - emergency executive escalation procedures and decision authority]

Classification Validation and Review: Quality assurance procedures including [Information Needed - severity classification validation procedures and review processes] ensuring appropriate emergency response activation and resource utilization.

False Emergency Handling: Procedures for misclassified emergencies including [Information Needed - false emergency handling procedures and education processes] maintaining system integrity while supporting customer learning.