Skip to main content
Read-only.
The marketer’s question is “which accounts do we share with our partners, and which targets does no partner touch?” Reach for this tool for account mapping and for placing an account in an account-mapping play. Follows the heyBTW MCP rules.

When to use it

  • “Which of our targets does Brightpath also work with?”
  • “Show me accounts shared by two or more partners.”
  • “Which declared targets does no partner touch?”
  • “Run the warm-intros play for the open house.”

Parameters

All optional.

Response

data[0] (note the camelCase keys, served as written): setCounts reflects the full matched set before min_confidence, partner_role and my_role narrow the returned rows. my_role narrows after the page is read, so a page can hold fewer rows than returned: follow next_cursor until has_more is false.

Plays

A real response from the heyBTW workspace scoped to the SF open house fixture, trimmed to two plays. The fixture partners have no managed or attributed account evidence yet, so no rows come back while 251 declared targets are uncovered:

Rules the agent must follow

  • partner_count, exclusivity and in_target are set facts. Nothing is ranked or rated: apply the user’s own CRM and ICP to prioritize.
  • my_role is maintained in heyBTW from Lists (provenance manual), not CRM-verified. Cross-check in the user’s CRM where it matters.
  • Join on company_domain (lowercase, without www) against the user’s CRM.
  • Follow next_cursor until has_more is false before stating a total from rows.
  • A failed read is always an error, never an empty set. An empty rows with status: "ok" is a real answer.

Errors and gaps