From d0bac11954dd7b0fb1d7bce161c50c66a8478f5a Mon Sep 17 00:00:00 2001
From: Tony Gauda <5620541+tgauda@users.noreply.github.com>
Date: Wed, 22 Jun 2022 18:59:08 -0400
Subject: [PATCH] Link to CE Weekly Debrief (#6338)

---
 handbook/customers.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/handbook/customers.md b/handbook/customers.md
index 40ca3f5a0e..efd5db67d7 100644
--- a/handbook/customers.md
+++ b/handbook/customers.md
@@ -118,7 +118,7 @@ The following table lists the Customer's group's rituals, frequency, and Directl
 | Customer Slack channel monitoring | Daily | Continuously monitor Slack for customer feedback, feature requests, reported bugs, etc., and respond in less than an hour.   | Tony Gauda        |
 | Customer follow-up | Daily | Follow-up and tag appropriate personnel for follow-up on customer items in progress and items that remain unresolved. | Tony Gauda |
 | Internal follow-up | Daily | Go through Fleet's internal Slack channels to check for any relevant new information or tasks from other teams. | Tony Gauda |
-| Customer debriefs | Weekly | Discuss customer questions, requests, and issues with the Product team. | Tony Gauda  |
+| Customer debriefs | Weekly | [Discuss customer questions, requests, and issues with the Product team.](https://docs.google.com/document/d/15Zn6qdm9NyNM7C9kLKtvgMKsuY4Hpgo7lABOBhw7olI/edit?usp=sharing) | Tony Gauda  |
 | Stand-up | Weekly | Meet with the Engineering team three to four times a week to share information and prioritize issues. | Tony Gauda |
 | Customer request backlog | Weekly | Check-in before product office hours to make sure that all information necessary has been gathered before presenting customer requests and feedback to the Product team. | Tony Gauda |
 | Product office hours | Weekly | Present tickets and items brought to Fleet's attention by customers that are interesting from a product perspective and advocate for customer requests. | Tony Gauda |