FindingcurrentGTM data

A meeting linked to an account may have nobody from that account in it

CRM and calendar links tie a meeting to an account by id, leaving attendance as a separate fact that engagement scores usually ignore.

SymptomAn account shows a recurring monthly meeting and a high engagement score, but nobody from that account has ever joined the call.

Linking a meeting to an account by CRM id looks like a safe way to count touches, even though the link only says the meeting is about the account.

I score target accounts partly on how much recent meeting activity they have. The first design counted every meeting linked to the account by its CRM id. That is the standard join, and it looks right.

A recurring internal call can carry an account link, for example a monthly sync that a teammate titled with the account name. Only my own team attends. Each occurrence still counts as a touch, and a long run of them reads as a relationship.

A second condition fixes this by counting a meeting only when at least one attendee has an email at the account's domains and accepted or attended. A meeting that fails the test stays in the data but stops feeding scores and recurring flags.

Shared mailbox domains and subsidiaries can hide a real attendee, so review the zero-attendee meetings before you trust the exclusion.

Check your setup read-only

Take the account with the most linked meetings in the last 90 days. List those meetings. For each meeting, count attendees whose email domain belongs to that account.

Passes ifEvery meeting with zero attendees from the account is excluded from engagement counts and from recurring-meeting flags.

Access needed:call-datacontext-readlocal-config

If it fails: changes to make later (not part of the check)
  1. 01Pick one account with a high meeting count.
  2. 02List its linked meetings for the last 90 days.
  3. 03Count attendees from the account's email domains for each meeting.
  4. 04Mark each meeting with zero such attendees as internal-only.
  5. 05Compare the account's meeting count with and without those meetings.
Applies ifYour engagement or relationship score counts meetings linked to an account by id.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.