❓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.