Simplify product feedback process

- Architecture diagram with history (git history).

- List of [Members in the Zendesk Support](https://about.gitlab.com/support/managing-support-contacts/#managing-contacts) [Shared Organization](https://about.gitlab.com/support/managing-support-contacts/#shared-organizations) maintained by the customer with full history for governance (git history).

- [TAM Issue tracker](https://gitlab.com/gitlab-com/cs-tools/gitlab-cs-tools/tam-issue-tracking) Tracking of product feature requests.

- Interacting with the Product Team and [Prioritizing Customer issues](/handbook/product/product-processes/customer-issues-prioritization-framework/#customer-success).

- Interacting with the Product Team and [Prioritizing Customer issues](/handbook/product/product-processes/customer-issues-prioritization-framework/).

- [Public Pages for Issue creation](https://gitlab.com/gitlab-com/account-management/templates/customer-collaboration-project-template/-/tree/master/public).

- [ServiceDesk Function](https://docs.gitlab.com/ee/user/project/service_desk/), to enable other users of the customer without a role in the Customer Collaboration Project to create issues. The CSM should notify the customer that the Collaboration Project is not meant for product support and troubleshooting inquiries.

- Sharing service ping metrics, graphics, and Usage metrics guides via PDF, CSV with GitLab from the Customer ([configure Collab project for LFS](https://docs.gitlab.com/ee/user/project/settings/index.html#configure-project-visibility-features-and-permissions)).

#### Feedback template

You can copy/paste this to make sure you don't miss anything or [create a comment template](https://docs.gitlab.com/user/profile/comment_templates/#create-comment-templates) for reusability:

```markdown

<!-- Select the appropriate subscription and product text below and remove the others (note: do not add them as labels)>

<!-- Click on ~customer priority:: below to select an appropriate label 1 through 10 with 10 being the highest>

The following ~customer is interested in this capability

- Subscription: ~"GitLab Ultimate" OR ~"GitLab Premium" OR ~"GitLab Free"

- Product: ~"self-managed" OR ~"gitlab.com" OR ~"GitLab Dedicated"

- Link to request:

- Priority: ~customer priority::

- Why interested:

- Problem they are trying to solve:

- Current solution for this problem:

- Impact to the customer of not having this:

- Questions:

- PM to mention:

- CSM to mention:

```

The `~customer priority::*` labels are inputs for the prioritization model powering the customer issue prioritization framework dashboard:

[See Guidance Here](../product-processes/customer-issues-prioritization-framework/)

- [Customer Requested Issues](https://10az.online.tableau.com/#/site/gitlab/workbooks/2015827/views)

These dashboards represent the relative importance of a given issue to the specific customer. 1 is the lowest priority and 10 is the highest. These can be updated at any point in time and will be reflected in the model within 24 hours. You can find more context about priority labels on the [customer issues prioritization framework handbook page](/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-points).

These dashboards represent the relative importance of a given issue to the specific customer. These can be updated at any point in time and will be reflected in the model within 24 hours. 

##### Good example