FindingcurrentGTM data

One meeting can belong to several accounts

A single account field duplicates partner calls, and merging them loses all but one.

SymptomA partner or parent-and-subsidiary meeting appears twice, or on only one of the accounts it involved, and agents describe the linked account as attending.

The standard meeting record carries one account field. Partner calls and parent-and-subsidiary calls don't fit there, and neither do meetings with two customers.

The single field forces a choice. Sources pick different accounts, so the same meeting arrives as duplicates, and merging them keeps one account and drops the meeting from the rest.

Tool wording decides how an agent reads a meeting's account link. A loosely worded link can be read as attendance. A single wording change can lead an agent to state that the account's people attended a meeting that was only about the account.

The remedy is account membership per source, kept as separate links that survive merges, plus tool text that separates what a meeting is about from who attended.

In a synthetic test set of 150 two-account meetings, merging duplicates into one account field dropped every meeting from one of its accounts, 121 of them from an account whose people attended; keeping one link per source through the merge dropped none. The set shows the mechanism, not how common it is.

Check your setup read-only

List the 20 most recent meetings whose attendees come from 2 or more accounts. Count how many of those accounts show each meeting. More than 1 of 20 missing from an account its attendees belong to is a gap.

Passes if19 or more of 20 sampled multi-account meetings appear on every account their attendees belong to.

Access needed:crm-readcall-data

If it fails: changes to make later (not part of the check)
  1. 01Link a meeting to every account it involves, one link per source, instead of a single account field.
  2. 02Carry every account link through a merge, so merging duplicates never drops an account.
  3. 03Label the link in tool output as what the meeting is about. List attendees separately.
  4. 04Test each tool wording change over repeated agent runs. Count how often the agent states attendance it can't support.
Applies ifYou back-fill meetings or emails into the CRM against one account per activity, and you sell through partners or to groups whose people share calls.

← 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.