> For the complete documentation index, see [llms.txt](https://engineering.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engineering.umh.app/engineering/development-process/how-to-decide-what-to-build/signals/customer-requests.md). # Customer requests What customers ask us for, and what they mention in passing. Owner: Jeremy A customer request records what one customer said, whether they asked for it or mentioned it in passing, and it lives on the ticket for the problem they are talking about. Several customers can have a request on the same ticket. ## Rules * Whoever hears a customer request posts it in #dev-2-product. The post says what broke, which customer, whether it is [blocking](/product/product-manager/blocking.md) and how to reproduce it. * File the ticket straight away, by saying `@linear create a ticket` in the thread. If a ticket for the problem already exists, mark the new one a duplicate afterwards: Linear moves its customer requests onto the ticket we keep. * Add the customer request to the ticket and link the Slack thread. * The ticket describes the problem rather than a solution. * Everything else goes in the Slack thread after filing: the metrics, similar tickets, older implementations. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://engineering.umh.app/engineering/development-process/how-to-decide-what-to-build/signals/customer-requests.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.