> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/using-the-app/account-summaries.md). # Account Summaries (AI) An account summary is a short, AI-written overview of how an account's contacts and visitors interact with your website: who visited, which pages they looked at, and what that suggests about their interest. Use it to get up to speed on an account before you reach out. *** ### Generate a summary 1. Open **Reports** and go to the **Top accounts** table. 2. Click **Generate Summary** for an account. 3. The summary appears in the table once it is ready. Click **What is this?** next to the button for a short explanation. ### Summarise all accounts To generate summaries for every account in the current table at once, use **Summarize all**. A confirmation shows how many accounts will be summarised and what it will cost. Depending on the size of the table, it can take a few minutes to generate all summaries. *** ### Credits Each account summary uses **100 credits**. See [LeadBoxer Credits](/leadboxer/account-and-billing/leadboxer-credits.md) and [LeadBoxer Pricing Explained](/leadboxer/account-and-billing/leadboxer-pricing-explained.md). ### Tips * Summaries are based on the visits and contacts LeadBoxer has collected for the account, so they are most useful for accounts with several visits. * Generate a new summary after an account has been active again to include the latest visits. --- # 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://help.leadboxer.com/leadboxer/using-the-app/account-summaries.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.