> 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/use-cases.md). # Use cases - [Visitor identification](https://help.leadboxer.com/leadboxer/use-cases/visitor-identification.md): Identify the companies and people behind your website visits and email engagement, so you can follow up on real interest. - [ICP & persona matching](https://help.leadboxer.com/leadboxer/use-cases/icp-and-persona-matching.md): Let LeadBoxer App highlight the companies that fit your Ideal Customer Profile and the people in them who match your target personas. - [Lead Qualification](https://help.leadboxer.com/leadboxer/use-cases/lead-qualification.md): There are several steps needed to create a qualified lead. We have used our extensive experience on this issue to build the most powerful yet easy to implement Lead generation machine. - [Lead Management](https://help.leadboxer.com/leadboxer/use-cases/lead-management.md): Track sales leads throughout the marketing lifecycle. Automatically move leads through your marketing funnel and monitor them until they are successfully converted to opportunities. --- # 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/use-cases.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.