Abhord Quickstart Guide (Refreshed for March 2026)
What’s new since the last edition
- Expanded model coverage and normalization: Out‑of‑the‑box surveys now include the latest flagship LLMs (e.g., GPT‑4.1 family, Claude 3 series, Gemini 1.5, Llama 3) with improved cross‑model scoring so results are comparable across vendors and settings.
- Smarter entity handling: Better alias/canonicalization reduces duplicate brand mentions and distinguishes product vs. company references.
- Weighted insights: Optional weighting by model reach and locale provides more realistic market‑level Share of Voice (SOV).
- Intent templates: Ready‑made prompt packs for brand baseline, comparisons, buyers‑guide, and troubleshooting queries.
- Alerts and annotations: Threshold‑based alerts for swings in mentions/sentiment/SOV, plus experiment annotations for before‑after content changes.
- Governance upgrades: SSO/SAML, role‑based permissions, project‑level data retention, and built‑in PII redaction for prompts and responses.
1) Initial setup and configuration
- Create your workspace
- Name your workspace after your brand or product line.
- Invite teammates and assign roles: Admin (settings/billing), Analyst (run/view surveys), Collaborator (view/annotate).
- Define entities and aliases
- Add your primary brand entity, products, and common aliases/misspellings. Example: “Acme Solar,” “AcmeSolar,” “Acme PV.”
- Map competitors and their aliases now—you’ll reuse this list in tracking.
- Connect properties (optional but recommended)
- Verify your primary domain(s) via DNS or HTML file.
- Add documentation/help‑center URLs, data sheets, and comparison pages. These act as “source‑of‑truth” references in analysis.
- Choose locales and weighting
- Select languages/regions you sell into.
- If you know your audience’s assistant usage (e.g., Android‑heavy vs. iOS‑heavy), set custom model weights; otherwise keep the default balanced mix.
- Privacy and retention
- Enable PII redaction for prompts and responses.
- Set retention to 12–18 months for trend analysis; use project‑level overrides for sensitive launches.
Pro tips
- Keep aliases tight at first. Over‑broad aliases inflate mentions and muddy sentiment.