Skip to content
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.

Commit

Permalink
Merge branch 'main' into rrhyne-patch-3
Browse files Browse the repository at this point in the history
  • Loading branch information
@sourcegraph-bot
sourcegraph-bot authored Mar 26, 2024
2 parents 7a65a38 + 9d5aca0 commit 341235d
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/departments/technical-success/support/process/product-gap-process.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down

0 comments on commit 341235d

Please sign in to comment.