> For the complete documentation index, see [llms.txt](https://support.suptask.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.suptask.com/working-with-tickets/essentials-for-your-daily-work/how-to-search-for-tickets.md). # How to search for tickets ### Overview You can easily find any of your Suptask tickets within Slack. In Slack you will have access to search across the tickets you have access to in Suptask. An Agent who have access to Inbox A can only search and find tickets within Inbox A. {% embed url="" %} ### Use Slack's built-in search Use the search bar at the top of Slack, you can also type **⌘+G** on a Mac or **Ctrl+G** on Windows or Linux, in order to access it. *** ### Search for a Ticket ID All tickets that your users have access to will be searchable in Slack. Simply search for the Ticket ID with Slack search like this: ***#423*** *** ### Search for keywords in tickets You can search across all ticket comments and replies that your user have access to in Suptask. Simply enter any phrase in the Slack search and it will search across your tickets. *** ### Expanding searchable keywords In your [Account settings](https://app.suptask.com/account/settings) you can turn on these two options: * Publish submitted form fields in ticket thread * AI summary of closed tickets This allow you to be able to search for all the submitted Fields in the Form used by the ticket. Making it possible to get additional content seachable in Slack. Searching across the generated AI content where the Problem and Solution of a ticket is recorded will help you to build knowledge and easily search across all of this directly in Slack. ### --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.suptask.com/working-with-tickets/essentials-for-your-daily-work/how-to-search-for-tickets.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.