From 57137d3d314d3d1eb5f4d9519fde05fa5bf950e2 Mon Sep 17 00:00:00 2001
From: Tony Gauda <5620541+tgauda@users.noreply.github.com>
Date: Fri, 17 Dec 2021 00:30:36 -0500
Subject: [PATCH] Moving support process documentation to CX area (#3385)

---
 handbook/product.md | 19 -------------------
 1 file changed, 19 deletions(-)

diff --git a/handbook/product.md b/handbook/product.md
index c12ce65df6..257e7cfe68 100644
--- a/handbook/product.md
+++ b/handbook/product.md
@@ -258,25 +258,6 @@ Non-release blocking bugs may include known issues that were not targeted for th
 
 Documentation on completing the release process can be found [here](../docs/03-Contributing/05-Releasing-Fleet.md).  
 
-
-## Support process
-
-This section outlines the customer and community support process at Fleet.
-
-The support process is accomplished via an on-call rotation and the weekly on-call retro meeting.
-
-The on-call engineer is responsible for responding to Slack comments, Slack threads, and GitHub issues raised by customers and the community.
-
-The weekly on-call retro at Fleet provides time to discuss highlights and answer the following questions about the previous week's on-call:
-
-1. What went well?
-
-2. What could have gone better?
-
-3. What should we remember next time?
-
-This way, the Fleet team can constantly improve the effectiveness and experience during future on-call rotations.
-
 ### Goals
 At Fleet, our primary quality objectives are *customer service* and *defect reduction*. This entails Key Performance Indicators such as customer response time and number of bugs resolved per cycle and.