Skip to main content

​
Overview

​
Escalation Process

  • We support P1 issues 24/7
  • A Root Cause Analysis (RCA) will be provided within 24 hours of the incident.

​
Non-escalatory Issues

  • Non-escalatory issues should be submitted to help@cxconnect.ai.
  • They will be acknowledged within one business day.
  • We track issues in a support board in Clickup, which will be provided after golive. To get access to your organization’s Clickup board, please reach out ot success@cxconnect.ai.
  • Issues are resolved as fast as possible based on the nature of the issue and business impact. It is critical that all required information is submitted per the template to ensure fast triage.
  • Real-time status and progress will be accessible in the Clickup Support Board.

​
Background

Here at cxconnect.ai, we use the premier Incident Management Service, Pager DutyⓇ, which is integrated into our other communication and collaboration systems. When a client contacts our P1 email, many disparate events are automatically triggered. We’re able to ensure all of the right folks have instant access to all of the information needed to:
  • Understand the issue
  • Communicate with our clients
  • Collaborate internally across teams
  • Resolve issues quickly, and
  • Audit the entire process
Our on-call engineer (not just someone who’s answering a phone and relaying information) usually responds within seconds during normal US working hours, and with 10 minutes outside of our normal working hours. Clients have been impressed with our resolution times. How it works: PagerDuty automatically notifies our on-call Engineer directly using their preferred channel (e.g. SMS or Slack). If that person does not respond to your email within 5 minutes, they will be notified via their secondary channel. If the person on-call does not respond to your email within 5 minutes of their second notification (now, 10 minutes total), the escalation platform notifies the standby person. This process continues throughout the entire support organization, eventually notifying the CEO.

​
Incident Report Definitions

Incident - Any unplanned event interrupting a normal IT service operation, ranging from degradation of service to a complete outage. Degradation - A decline in normal IT service levels, which does not entirely interrupt the IT service. Outage - Any period of complete disruption or interruption of an IT service.

​
Service Level Agreement (SLA)

P1 issues are monitored 24/7/365 and the escalation process is outlined below: ChatLingual will make all reasonable efforts to respond within 24 hours, Monday through Friday, except for holidays, to any request during normal business hours.
SeverityFirst Response TimeEmail AddressDefinitions/Examples
P1 - Critical30 minutes, Root Cause Analysis (RCA) within 24 hoursProvided during OnboardingProduction outage at a company/organizational level, does not include
P2 - Major8 business hourshelp@cxconnect.aiImpacts user productivity but does not prevent service use for the entire
P3 - Minor24 business hourshelp@cxconnect.aiMinor bug that does not significantly affect user productivity, e.g. UI bug,
Service Request24 business hourssuccess@cxconnect.aiChanges to configuration, content, or anything else the client cannot do
⌘I