TechniquecurrentGTM data

A late transcript turns one meeting into two

Match a late recording to its meeting by time and shared external attendees.

SymptomThe same call appears twice on an account timeline as a calendar meeting and a recording with a different title.

One meeting reaches a revenue team's data from several sources, such as the calendar, the call recorder and the CRM. Each carries its own title, and the transcript often lands after the meeting.

Titles don't match across sources, so a matcher keyed on title sees two meetings where there was one.

A time-window match with no other condition is the obvious first fix, but time alone over-merges back-to-back calls with different buyers into one meeting.

Shared external participants gate the time match. Two records in the same window count as one meeting only if they share an external participant.

A recorder row with no content doesn't prove the meeting was held. Until a transcript arrives, the calendar rule decides on whether the meeting started and was not cancelled.

In a synthetic test set of 300 meetings with 20 back-to-back pairs, a title match left every meeting duplicated, a time window alone made 20 false merges, and time plus a shared external participant made none of either. The set shows the mechanism, not how common it is.

Internal-only meetings have no external participant, so the gate can't apply to them, and a time match alone can't be trusted there.

Check your setup read-only

Take the account with the most meeting records in the last month. List its meeting records with start times and attendees. Find pairs that start close together and share an external attendee. Any pair that is really 1 meeting is a duplicate your matching missed.

Passes ifA candidate pair is 2 meeting records that start close together and share an external attendee. Among the sampled account's meetings from the last month, no candidate pair describes the same meeting.

Access needed:crm-readcall-data

If it fails: changes to make later (not part of the check)
  1. 01Match records of the same meeting on a time window, never on title.
  2. 02Require at least one shared external participant before a time match counts.
  3. 03Do not treat a recorder record with no content as proof the meeting was held. Use the calendar rule until a transcript arrives. The calendar rule asks whether the meeting started and was not cancelled.
  4. 04Attach a late transcript that matches to the existing meeting instead of adding a new meeting.
Applies ifYour jobs back-fill meetings or call activity into the CRM from both a calendar and a call recorder.

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