# Call transcripts name the speaker without giving their side

Guessing a speaker's side flips the meaning of "we" in a call summary.

By Ki Moon · 2026-08-17 · finding · current
Canonical: https://kihmoon.com/bench-notes/p/transcripts-dont-say-which-side/

**Symptom:** A call fact credits the customer with a line the seller said, or gives a next step to the wrong company. The quoted words are correct.

Most conferencing tools don't send speaker side. Recorders that do derive it from email domain, so treat it as one input rather than the answer. A summarizer that writes "we agreed" or "they asked" has to decide whose "we" it is.

Side has to be derived from the person the speaker resolves to. That person is an internal user, a contact at the account, or nobody known. Gong's API reference lists each call party's affiliation as Internal, External or Unknown, and ties transcript speakers to parties through a speaker ID.

When side is guessed wrong, the verbatim quote stays right while the summary sentence around it hands those words to the other company.

Repair carries the same risk as the original error. A naive repair can flip facts to the wrong side.

Unknown is a better answer than a confident wrong side.

In a synthetic test set of call transcripts with 25 unresolved speakers, defaulting unresolved speakers to external filed 104 internal statements as customer-said; resolving each speaker first filed none and left 193 statements marked unknown. The set shows the mechanism, not how common it is.

## Check your setup (read-only)

Take the 10 most recent call facts in your fact store that say "we" or assign a next step. Find each speaker's side: your side if the speaker's email domain is your company's domain, the customer's side if not. With no email, use the account on the speaker's CRM contact record. Compare that side with the side the fact gives the speaker. More than 1 of 10 that differ means sides are being guessed.

**Passes if:** In 9 or more of 10 sampled call facts, the speaker's side matches their email domain or CRM contact record.

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

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

1. Resolve each speaker to a person first. Derive the side from that person: internal user, account contact, or unknown. Use any side label a recorder sends as one input, not the answer.
2. Decide the side before the model generates the summary sentence. Give the side to the model alongside the quote.
3. When a speaker can't be resolved, label the side unknown instead of defaulting to external.
4. Recompute the side of old facts with the same rule the extractor applies to new facts. Rewrite only the facts whose side differs.

**Applies if:** Your fact store or signal cards draw on call summaries from 2 or more recording or conferencing tools, attributed to companies.

**Skip if:** Your call summaries quote speakers verbatim and never paraphrase into "we" or "they".

Tags: meetings, identity, data quality
