> ## Documentation Index > Fetch the complete documentation index at: https://docs.boothrev.com/llms.txt > Use this file to discover all available pages before exploring further. # Target accounts # Named Accounts Named Accounts are how BoothRev connects event conversations back to the accounts your ABM programme is actually built around — not just "did we get leads," but "did the accounts we planned for show up, and how far did the conversation go." *** ## What a Named Account is A Named Account is a curated record: company name, email domain, territory, and line of business. It's tenant-wide, not tied to a single event — the same list applies across every event your team runs. Manage your list at **Named Accounts** in the left sidebar (under Org) — the list itself doubles as an account-first portfolio view, with each row showing its Clarity, Coverage, and Signal-strength at a glance, plus a Key Account filter. Field Marketing Managers curate this list. Unlike scorecard templates, it's editable and deletable at any time. *** ## Adding Named Accounts * **One at a time** — enter a name, domain, territory, and line of business directly. * **Bulk upload** — upload a CSV. Rows are matched (upserted) by domain, so re-uploading an updated list is safe: existing accounts get updated, new ones get added. *** ## How matching works BoothRev matches a lead to a Named Account automatically, by email domain. You never tag a lead as a Named Account by hand. Matching runs the moment a lead's email is confirmed, wherever that happens: a rep confirming on mobile, an event owner confirming on web, a CSV import, or a mobile sync push. Once a lead is matched, it's sticky — later edits to the lead never re-match or clear it. Free email domains (Gmail, Yahoo, and similar) never match a Named Account, even if the company name looks right. If you add or update Named Accounts after an event already has leads, use **Re-match named accounts** in Event Settings → Event Success (next to Re-score ICP for all leads) to re-run matching against every non-archived lead in that event. *** ## What changes when a lead is on a Named Account Rev is told when a lead matches a Named Account, and it raises that lead's priority one level — Medium becomes High, Low becomes Medium. Named Account status alone is never enough to make a lead High priority; there still has to be a real engagement signal in the conversation. This means a lead's priority in the inbox can reflect Named Account status, not just the conversation itself. See [Reading Rev's output](/rev-ai/reading-rev-output) for the full picture of how priority is set. *** ## Key Accounts: strategy-aware recommendations Mark a Named Account as a **Key Account** and give it a short authored strategy brief, and Rev goes beyond extraction into genuine reasoning for that account: * **Recommended Actions** — Rev's own suggested next step for the account, reasoned against the strategy brief plus the account's other leads across events, not just the one conversation in front of you. It posts to the lead's activity timeline like any other Rev output, in an amber "Recommended Actions" card. * **Account narrative** — a 2-4 sentence synthesis of where the account stands, kept current on the account's own page. * **Cross-account signals ("For Review")** — every lead's analysis is checked against your Key Account names, so if a conversation on one lead turns out to actually be about a *different* Key Account (mentioned as a competitor, vendor, former employer, or partner), Rev flags it for review instead of letting it get buried on the wrong lead. An account marked Key with no strategy brief yet behaves exactly like a plain Named Account — these three only run once a brief is written, since reasoning against nothing produces generic, unhelpful output. *** ## The Account Dashboard Click any account in your Named Accounts list to open its own dedicated dashboard — a third linked view alongside the Event and Portfolio dashboards, scoped to that account across **every** event it's ever shown up in, not just one. Event Owners and above can view it; only Field Marketing Managers and Admins can curate the account itself or act on what's flagged there. Top to bottom: * **Narrative** — Key Accounts only. A 2-4 sentence synthesis of where the account stands, kept current by Rev. * **Recommended Actions** — Key Accounts only. Rev's suggested next step for the account, same as what shows on the lead's own timeline. * **For Review** — Key Accounts only. Cross-account signal mentions waiting on your Accept or Dismiss — see [Cross-account signals](#key-accounts-strategy-aware-recommendations) above. Accepting one folds it into the Signal Timeline below; dismissing it is soft and can be reconsidered. * **Signal Timeline** — every signal Rev has extracted across every lead matched to this account, in one chronological list, including any cross-account mentions you've accepted. * **Stakeholder Map** — everyone captured on this account: their seniority, function, buying role (economic buyer, champion, technical validator, influencer, blocker, end user, coach), when they were last in touch, which rep talked to them, and which event. * **Scorecard status** — the account's qualification attributes, rolled up across every event it's appeared in. * **Open Questions** — a live list of gaps: buying roles you haven't identified yet, scorecard attributes still unassessed, mentions still waiting for review, and signals that have gone stale (no update in 90 days). Three bands summarize the account at a glance, here and on the Named Accounts list itself: | Band | What it tells you | | - | - | | **Clarity** | *Well understood / Partially understood / Early* — how much of the account you've actually mapped, weighted by scorecard coverage and how recent the signals are. | | **Coverage** | A plain-language description (not a score) of who you've reached — which seniority levels, functions, and buying roles, and which are still missing. | | **Signal strength** | *Strong / Moderate / Stale / None* — how much signal exists and how recent it is. | *** ## Named Account Coverage on the event dashboard Open an event's dashboard and go to the **Signal Trends** tab. Named Account Coverage shows your curated accounts side by side with this event's pre-registered invite list, so you can see two different things at once: * **Curated accounts** — every account on your list, including the ones with zero contact yet. These "not yet engaged" rows are the whitespace: accounts you planned for that haven't shown up. * **Pre-reg invite-list domains** — domains from this event's own pre-registered attendee import that aren't on your curated list, computed live at report time. A lead counts as "engaged" once it's past a bare draft or import row — actually captured or confirmed, not just imported. The Engagement tab's **Account Intelligence** row surfaces two more counts, computed live rather than stored: **Accounts Clarified** (a lead on the account produced at least one signal or an assessed scorecard attribute) and **Accounts Progressed** (a meeting agreed, a newly-reached senior stakeholder, qualification crossing the line, or a clear next-step signal). *** ## What Named Accounts are not * **Not auto-populated from a pre-registered attendee import.** That's deliberate — a one-off attendee CSV shouldn't silently bloat the curated list you maintain across every event. * **Not a replacement for ICP.** ICP defines what a good lead looks like in general. Named Accounts identify specific named companies you're tracking regardless of ICP fit. * **Not a source of a projected pipeline dollar figure.** BoothRev doesn't multiply qualified leads by an assumed deal size to produce a pipeline or ROI projection — coverage, signals, and progress are counts you can defend, not a forecast. *** ## Related * [Qualification](/qualification/index) * [Qualification → Scorecard templates](/qualification/scorecard-templates) * [Rev AI → Reading Rev's output](/rev-ai/reading-rev-output) * [Event dashboard and KPIs](/for-field-marketing-managers/event-dashboard) * [Setting up an event](/for-event-owners/setting-up-an-event) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.