From f8d563580f2aa352f74f9e3055ebdf9306f7b991 Mon Sep 17 00:00:00 2001
From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Date: Tue, 21 Oct 2025 18:13:45 -0400
Subject: [PATCH] New customer promises call (#34605)

---
 handbook/company/product-groups.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md
index 154507468e..481bbc8fce 100644
--- a/handbook/company/product-groups.md
+++ b/handbook/company/product-groups.md
@@ -904,13 +904,13 @@ This meeting is to disseminate engineering-wide announcements, promote cohesion
 
 ### New customer promise(s)
 
-The Account Executive (AE) schedules this meeting before Fleet commits to one or more new customer promises. It's meant to streamline communication and encourage getting the best product decisions.
+The Account Executive (AE) or Customer Success Manager (CSM) schedules this meeting before Fleet commits to one or more new customer promises. It's meant to streamline communication and encourage getting the best product decisions.
 
 If the buyer (aka the "Santa") hasn't reviewed the price in the first order form or we don't have a date attached to the promise(s), then we're not ready for this call.
 
 On the order form, customer promises are represented as [customer request](https://fleetdm.com/handbook/product-design#unpacking-the-why) issues and not [user stories](https://fleetdm.com/handbook/company/product-groups#scrum-items).
 
-**Participants:** AE, SC, CEO, CTO, VP of Customer Success, Head of Product Design, and relevant EM (+ temporarily: CRO).
+**Participants:** AE or CSM, SC, CEO, CTO, VP of Customer Success, Head of Product Design, and relevant EM (+ temporarily: CRO).
 
 **Agenda:**
 - Review each proposed customer promise on the order form.