Skip to main content
Accounts that surface in the Invite List Builder carry a score and a tier, so you can prioritize at a glance. This page is the legend for that in-product view.
This page describes the product UI. Do not treat it as the MCP contract.The scores and tiers described here are being withdrawn (HEY-1764, HEY-1897, HEY-2067) and are documented on no MCP tool reference page. Some of the underlying scalars are still emitted on contract v1, which is the default — their removal is implemented in contract v2, which is not yet advertised — so you may see them in a live response. Seeing one is not a reason to build on it: they are withdrawn, and the per-tool reference pages are authoritative over this page for anything an agent consumes.If you are building an agent, work from the MCP tool reference and rank on response order and source-backed fields, not on a score or tier threshold read from here.

​
Score

A 0 to 100 score that ranks an account by how strong its signals are: an open CRM opportunity, a partner relationship, event attendance history, and how many of those overlap. More independent signals push the score higher, so an account with both an open deal and event attendance ranks above one with only a single signal. The exact formula evolves as heyBTW learns what predicts pipeline outcomes. Treat the score as a ranking, not a fixed cutoff.

​
Tier

A simpler A, B, or C classification on top of the score, used across the product UI and in agent outputs:
  • Tier A. Focus here first.
  • Tier B. Worth activating.
  • Tier C. Track, but not an immediate action.
Filters like “only Tier A in DACH” work directly against the tier. If you build a workflow on a threshold, use the tier rather than a raw score, because the tier stays stable while the score’s internal formula can change.

​
Where it shows up

  • Invite List Builder. Every recommended account card shows its score and tier.
  • MCP responses. Not a supported surface for these. No MCP tool reference page documents an account score or an A/B/C tier, and they are withdrawn. Contract v1 still emits some of the underlying scalars, but they are not part of the contract you should build on. Rank on the order the tool returns and on the source-backed fields documented per tool; see get_invite_recommendations.

​
Relationship strength is scored separately

In the Context Graph Explorer, the strength of a path into an account and the credibility of the people on it are scored on their own terms, from observed event behavior and seniority, and shown with their own labels. Those describe how to reach an account, not how to prioritize it, so they are separate from the account score and tier on this page.