> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/account-intelligence/account-intelligence-faq.md). # Account Intelligence FAQ ## Account Scoring > **Q:** Can HockeyStack score all accounts or just some? What are some best approaches? > > **A:** We score accounts that are in a **View** where **Configuration → Rescore all accounts** is toggled **on** and the **Schedule** is **not Off**. Best practice is to create separate Views for distinct product lines/segments and enable scoring per View. Avoid giant, catch‑all Views; use filters first (ICP, geos, lifecycle). Limit each View to be under 5,000 companies for best performance. > **Q:** What signals/fields can scoring reference? > > **A:** Any **Account/Contact/Lead/Opportunity** fields synced from SFDC/HubSpot (standard + custom), plus first-party web activity, AI research outputs, and third‑party intent (if connected). ## Persona Creation > **Q:** Best practices for building personas and prompt detail? What to avoid? > > **A:** Treat the prompt like instructions to a junior sourcer reviewing a LinkedIn profile: > > * Specify **department**, **seniority**, **keywords**, **exclusions**, and **context** (use case, product fit). > * Give **positive & negative examples** ("Good fit if… / Not a fit if…"). > * Ask for a **binary decision + rationale** (short). > * Limit scraping scope to **recent roles** to avoid legacy titles. --- # 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://docs.hockeystack.com/account-intelligence/account-intelligence-faq.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.