From 35e35cb1a47dc5c769f5975f10c8dfbb31df35b1 Mon Sep 17 00:00:00 2001 From: Zay Hanlon <114112018+zayhanlon@users.noreply.github.com> Date: Wed, 5 Nov 2025 08:05:05 -0800 Subject: [PATCH] Revise customer promise section for CSM (#35126) Revise customer promise section for CSM --- handbook/company/product-groups.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md index adb1adeb9a..567ba4b0e7 100644 --- a/handbook/company/product-groups.md +++ b/handbook/company/product-groups.md @@ -890,13 +890,13 @@ This meeting is to disseminate engineering-wide announcements, promote cohesion - Structured and/or unstructured social activities -### New customer promise(s) +### Customer promise(s) -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. +The Account Executive (AE) or Customer Success Manager (CSM) schedules this meeting before Fleet commits to one or more 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). +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). CSM's must reserve customer promise requests for issues that are required for a renewal to close or for an expansion to close. **Participants:** AE or CSM, SC, CEO, CTO, VP of Customer Success, Head of Product Design, and relevant EM (+ temporarily: CRO).