From b6c9a5e3b22df056822e8ffeac6ba196ab30e2f3 Mon Sep 17 00:00:00 2001 From: Rachel Whitton Date: Fri, 23 Aug 2024 14:46:43 -0500 Subject: [PATCH] Support engineers --- source/content/guides/disaster-recovery/01-introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/content/guides/disaster-recovery/01-introduction.md b/source/content/guides/disaster-recovery/01-introduction.md index 77b6e3552e..618ffa1daf 100644 --- a/source/content/guides/disaster-recovery/01-introduction.md +++ b/source/content/guides/disaster-recovery/01-introduction.md @@ -17,6 +17,6 @@ product: [--] integration: [--] --- -This guide is focused on the immediate actions a Pantheon customer should take in the event of a catastrophic site failure. In all cases, the first step should be to file an emergency ticket, a general support ticket, or start a live chat depending on your [account tier](/guides/support/#support-features-and-response-times). Filing an emergency ticket will immediately escalate the incident to our engineering team, and ensure the fastest and most effective service. +This guide is focused on the immediate actions a Pantheon customer should take in the event of a catastrophic site failure. In all cases, the first step should be to file an emergency ticket, a general support ticket, or start a live chat depending on your [account tier](/guides/support/#support-features-and-response-times). Filing an emergency ticket will immediately escalate the incident to our support engineers, and ensure the fastest and most effective service. This guide does not cover all potential post-disaster recovery processes, as these will depend on the nature of the incident and its impact on your site. It's essential to engage with Pantheon Support during the incident; our team will help determine the necessary remediation steps.