From 31548de6576edb58c445fc744569841592e63fed Mon Sep 17 00:00:00 2001
From: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com>
Date: Tue, 11 Mar 2025 03:49:30 -0500
Subject: [PATCH] Add step to update salesforce with GitHub label (#27022)

https://github.com/fleetdm/confidential/pull/9913
---
 handbook/customer-success/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/handbook/customer-success/README.md b/handbook/customer-success/README.md
index 091ccda93e..3a77de41b5 100644
--- a/handbook/customer-success/README.md
+++ b/handbook/customer-success/README.md
@@ -32,6 +32,7 @@ Occasionally, we will need to track public issues for customers and prospects wh
 
 1. The team member creating the issue will choose an appropriate minor planet name from this [minor planets page](https://minorplanetcenter.net//iau/lists/MPNames.html) (alphabetical).
 2. Create a label in the fleetdm/fleet and fleetdm/confidential repos which can be attached to current and future issues for the customer or prospect. As part of the label description in the fleetdm/confidential repo, add the customer or prospect name. This way, we maintain a confidential mapping of codename to customer or prospect.
+3. Navigate to the account in Salesforce. Edit the "GitHub label" field to include the customer or prospect label and save the record. This enables the "fleetdm/fleet" and "fleetdm/confidential" GitHub issue searches. 
 
 
 ### Prepare for routine customer meeting