From 9d5aca09e04fa38c2f40fba54a47e0778d597ccc Mon Sep 17 00:00:00 2001
From: Gabe Torres <69164745+gabtorre@users.noreply.github.com>
Date: Mon, 25 Mar 2024 17:46:01 -0700
Subject: [PATCH] Update pg process (#8772)

---
 .../technical-success/support/process/product-gap-process.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/departments/technical-success/support/process/product-gap-process.md b/content/departments/technical-success/support/process/product-gap-process.md
index 8811e5a95e2d..d42cee1831b2 100644
--- a/content/departments/technical-success/support/process/product-gap-process.md
+++ b/content/departments/technical-success/support/process/product-gap-process.md
@@ -6,7 +6,7 @@ Product gaps are submitted by the customer’s assigned TA or Scaled Success. Th
 
 > If you come across an account that doesn’t have a TA assigned and isn’t under Scaled Success management, feel free to ask in the #discuss-technical-advisors channel about assigning someone to the request.
 
-**Accounts with a TA**: Head to the #discuss-technical-advisors channel and follow the Product Gap Request workflow. Keep the ticket open for a few days in case the TA or customer has more to say.
+**Accounts with a TA**: Include the TA in the issue thread, providing them with the details of the product gap. Keep the ticket open for a few days in case the TA or customer has more to say.
 
 **Scaled Success accounts**: Head to the #discuss-scaled-success channel and follow the Product Gap Request workflow. Leave the ticket open for a few days, allowing the team or customer to follow up.