FindingcurrentGTM data

Being invited or mentioned does not mean someone attended a meeting

Calendar, RSVP and recording data each answer "who was there" differently.

SymptomAn AI-written profile says a person attended a meeting and holds the decision. The only evidence behind the claim is an invite or a mention in an email.

A meeting record looks like it answers who was there. The calendar, the RSVP and the recording each tell a different story, and the obvious join treats every listed name as an attendee.

The sources disagree in predictable ways:

  • A recorded call never marked as held.
  • One meeting split across several records with conflicting states.
  • A "declined" RSVP from someone the recording shows speaking.
  • Transcript participant lists that copy the invite list.

The invite list is the trap. On many calls, some listed people never joined. Gong's API reference for extensive call data marks each participant's methods as Invitee or Attendee, so being invited and having attended are separate values. Mention-only links are common too, such as an email that names someone who never joined the meeting.

Agents read tool wording literally. One loose sentence can make an agent count invitees as attendees. A single sentence saying everyone listed still counts can flip an agent's answers from right to wrong.

Check your setup read-only

Take the 20 most recent attendee claims in your agent's transcripts. Look for each person in the recording's speaker list or the CRM's held-meeting record. More than 3 of 20 found only on the calendar invite means the agent reads attendance from calendar invites.

Passes if17 or more of 20 sampled attendees appear in a recording's speaker list or a held-meeting record. A calendar invite alone does not count.

Access needed:agent-transcriptscall-datacrm-read

If it fails: changes to make later (not part of the check)
  1. 01Give every meeting one state: held, proposed, scheduled or canceled.
  2. 02Carry each person's strongest link onto the meeting: spoke on the recording, accepted, invited, or only mentioned.
  3. 03Let a transcript outrank weaker flags such as an RSVP or a missing held mark.
  4. 04Name invited-only people separately in tool output. Say plainly that invited-only people are not counted as attendees.
Applies ifYour jobs read calendar invites and call recordings for the same meetings, to back-fill the CRM or tell sellers who met whom.

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