FindingcurrentGTM data

Whether a meeting happened depends on which source saw it

"Took place" is an evidence rule over sources rather than a stored field.

SymptomMeeting counts include email threads that mention a date, past invites still marked scheduled, and transcript-born meetings with no state at all.

Most systems store a meeting state and trust it. Each source sets that state its own way, and none of them sees the whole meeting.

  • Email chatter about a call becomes a dated "meeting".
  • Calendar invites stay "scheduled" after the call happened.
  • Meetings created from a transcript carry no state at all.

So "took place" is a rule over evidence. A meeting happened if a recording shows an external participant speaking. One that started and was neither cancelled nor inferred counts as presumed held, labelled that way and ranked below a recording. Recording outranks calendar, and calendar outranks email.

A stored state field can miss a large share of the meetings that a recording or a started calendar entry shows were held.

In a synthetic test set where 136 meetings were held, the stored state field marked 52 of them held, plus 30 that were not; the evidence rule caught all 136 and also counted 5 presumed meetings that were not held. The set shows the mechanism, not how common it is.

Check your setup read-only

Take the rep with the most meetings last month, and that rep's last 20 past meetings. Count the meetings your stored "happened" field marks as held. Count the meetings with a recording of an external participant speaking, or a calendar entry that started and wasn't cancelled. A difference of more than 2 of 20 means the stored field is not the answer.

Passes ifThe evidence count covers meetings with a recording of an external participant speaking or an uncancelled calendar entry. For the sampled rep's last 20 past meetings, the stored held count is within 2 of the evidence count.

Access needed:crm-readcall-data

If it fails: changes to make later (not part of the check)
  1. 01Count a meeting as held when a recording shows an external participant speaking. Count a meeting as presumed held when it started and was neither cancelled nor inferred from email. Rank presumed held below a recording.
  2. 02Rank recording above calendar and calendar above email when sources disagree.
  3. 03Give transcript-born meetings a held state from the recording itself when it shows an external participant speaking.
  4. 04Compare your stored state against the evidence rule for one rep before trusting either.
Applies ifYou back-fill meetings as CRM activity, or report meeting counts per rep, from more than one source: calendar, recorder or email.

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