> For the complete documentation index, see [llms.txt](https://mava.gitbook.io/mava-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mava.gitbook.io/mava-docs/webhooks-and-api/webhooks.md). # Webhooks You can use the webhooks to receive updates about the following collections.\ \ **Tickets**: Support requests that appear in the Mava dashboard. A single customer can have multiple - although only 1 at a time. Ticket attributes can be found here which contain custom data assigned to the ticket **Messages**: Tickets can have any number of messages. These can come from a number of different sources but most often are either the customer or one of your support agents. Messages can also come with attachments.\ \ **Customers**: Every ticket is created by a customer. Customers can create multiple tickets (not at the same time) and can have a set of customer attributes assigned to them. Example use cases could include: * Updating your CRM based on new customers, and their attributes * Creating issues/tickets in product management software and adding messages to inform other company teams about the support request details. E.g a Jira issue with a breakdown of the messages so a developer can read the bug report. --- # 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://mava.gitbook.io/mava-docs/webhooks-and-api/webhooks.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.