FailurecurrentGTM data

A prior-contact check on your CRM misses mail your sequencer sent

A check for earlier outreach can come back clean for people already mailed, because the sequencer keeps its own log and never writes to the CRM.

SymptomA prior-contact check on the CRM and the mailbox graph reports no earlier outreach for a person your team already mailed.

Before a campaign I check whether anyone on the list was contacted before, and a first design that reads the CRM activity history and the mailbox graph, the standard places to look, can come back clean for people a sequencer already mailed. A sequencer with its own send log never touches the connected mailboxes or creates a CRM activity. The CRM only holds mail that a sync or a person logged there, and a sequencer is a third writer with its own record.

The failure is quiet since the check does not error. It returns an empty result that reads as never contacted, so the people the check was built to protect can get a second cold message.

Mail from a sequencer often does not pass through the rep's mailbox. Because many setups log to the CRM only for connected mailboxes, the send exists in exactly one place, the sequencer's own log.

The remedy is to treat every tool that mails people as a source for the prior-contact check. Read the CRM, the mailbox graph and each sequencer's send log together, and match on the person instead of the mailbox. A check that skips one source answers a smaller question than the one you asked.

A send log shows what the tool attempted, not replies handled elsewhere, so read both before you call a person fresh.

Check your setup read-only

List the people your sequencer mailed in the last 30 days. Take the 10 most recently mailed. Look up each person in the CRM activity history and count the matches.

Passes ifEach of the 10 people has a CRM activity for the message, or the check also reads the sequencer log.

Access needed:crm-readlocal-config

If it fails: changes to make later (not part of the check)
  1. 01List every tool and mailbox that mails people for your team.
  2. 02For each one, find where it records a sent message.
  3. 03Pick 10 people the tool mailed in the last 30 days.
  4. 04Look up each person in the CRM activity history.
  5. 05Count the people with no matching CRM activity.
  6. 06Compare that count with the tool's own send log.
Applies ifYou use a sequencer or a separate sending domain and a prior-contact check reads only the CRM or the mailbox graph.

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