# One meeting can belong to several accounts

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

By Ki Moon · 2026-09-18 · finding · current
Canonical: https://kihmoon.com/bench-notes/p/one-meeting-several-accounts/

**Symptom:** A 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 if:** 19 or more of 20 sampled multi-account meetings appear on every account their attendees belong to.

**Access needed:** crm-read, call-data

## If it fails (changes to make later, not part of the check)

1. Link a meeting to every account it involves, one link per source, instead of a single account field.
2. Carry every account link through a merge, so merging duplicates never drops an account.
3. Label the link in tool output as what the meeting is about. List attendees separately.
4. Test each tool wording change over repeated agent runs. Count how often the agent states attendance it can't support.

**Applies if:** You 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.

**Skip if:** Every meeting record in your CRM has attendees from exactly 1 outside account.

Tags: meetings, agents, crm
