If a case submitted to Product Support needs the engagement of Development, Cloud Operations, or a 3rd party, it may need more time to resolve pending their analysis and findings.
Criteria for escalations
The following criteria must be met for an escalation request to be approved.
- There must be an active case. There must be an existing case open before it can be escalated.
- NOTE - When a case is closed, the Escalate Case button is inactive. To reopen a case, do so through the Support Portal or contact Product Support.
- Double-check the case. Has there been a recent update to the case that you may have missed? Is Product Support waiting on more information from you before they can proceed?
- Do not request an escalation based on change in urgency or impact. If a case warrants a priority update to High due to greater urgency or wider impact, contact Product Support.
- An escalation should not be requested for RCA (Root Cause Analysis) for Cloud Platform outages unless Product Support has had 5 business days to complete analysis for cloud deployments, per our standard Service Level Targets for RCA delivery. See PureConnect Direct Customer Handbook, PureConnect Partner Handbook, or Cloud CX Handbook.
- NOTE - After service is restored for severity 1 platform-level incidents, Genesys strives to provide a comprehensive RCA document to affected customers within five (5) business days.
- Escalations for high-priority cases need 24 hours since their last update, and the issue is actively causing significant business impact.
- Low-priority cases are not eligible for escalation.
- To change a case to medium-priority, request the change in the work notes.
- To change a case to high-priority, contact Product Support.
Critical commercial issues (non-FedRAMP)
Critical issues, like production down, may need management attention. The support expert assigned to your case will engage a Product Support Manager.
IMPORTANT - Do not request assistance for urgent issues via email, chat, or web as it leads to a delayed response in resolving your issue.
Non-critical commercial issues (non-FedRAMP)
- From the Support Portal portal, select a case.
- In the lower right of the case page, click Escalate Case.
- If the Escalate Case button is unavailable, an open escalation likely exists for the case.
Management process
- Customer or Partner submits an Escalation Request.
- The Escalation Owner reviews the request and determines if it meets the Escalation Criteria.
- The Escalation Owner replies to the request with next steps.
- NOTE - If the Escalation Request is invalid, the Escalation Owner will give reasons why and give process information to the requestor.
- If an escalation request is valid, the Escalation Owner evaluates the situation, prioritizes the escalation by importance and urgency, and works with the engineers to set expectations regarding next steps.
- Escalation Owner updates the case with all more external communications with the customer or partner regarding the escalation.
Communicate directly with an Escalation Owner (Non-FedRAMP only)
Once a non-FedRAMP case is escalated, you can communicate directly with the Owner of the escalation from the Escalation Details tab on a case. The Case Details captures the technical aspects of the case while the Escalation Detailscaptures the communication flow of the escalation.
IMPORTANT - Be sure to use the appropriate feed for your updates.
FedRAMP Cloud CX & Engage cases
FedRAMP cases can be escalated via the Support Portal site once they have been assigned.
- From the FedRAMP Support Portal, select a case.
- In the lower right of the case page, click Escalate Case.
- NOTE - If the Escalate Case button is unavailable, an open escalation likely exists for the case.
See also
- Case Escalation Process Change
- Password - Genesys2022