FindingcurrentGTM data

The account owner of record is not always a working book

CRMs keep ownership on inactive users and park accounts on a default owner.

Symptom"My accounts" or "top AE by accounts" answers include people who have left, or a default user holding a large share of accounts.

Agents answer "my accounts" and "who covers this" from the account owner field. That is the standard reading, but the CRM doesn't keep the field current.

CRMs leave accounts on users after they're deactivated, and unassigned accounts get parked on a default owner. Neither is a working book. Salesforce Help's page on deactivating users advises transferring a deactivated user's records to an active user, because processes can't update records owned by inactive users.

So answers built on the field mislead. A "top AE" ranking can crown the parking user, and "my accounts" includes accounts nobody works.

Show the agent whether each person is active, and a last-interaction date on each stakeholder link, so it can tell an owner from someone working the account.

An owner-only reading also misses the deal team, which often sits in custom user-lookup fields instead of the owner field.

In a synthetic test set of CRM accounts, ranking owners by account count put a default owner first with 150 accounts, 2.7 times the top active rep's 55; leaving out inactive and default owners put an active rep first. The set shows the mechanism, not how common it is.

Check your setup read-only

Count accounts per owner on the account object. Compare each owner with the CRM user object's active flag. Count the accounts held by a single default owner. Any such account that your routing or owner-based answers treat as a working book is a gap.

Passes ifYour routing and owner-based answers skip or flag every account that an inactive user or a default owner holds.

Access needed:crm-readlocal-config

If it fails: changes to make later (not part of the check)
  1. 01Check the owner's active status before treating an owner as a working rep.
  2. 02Leave default or placeholder owners out of rankings and "my accounts" answers.
  3. 03Show a last-interaction date beside each owner or stakeholder link.
  4. 04Read the custom user-lookup fields for the deal team, not only the owner field.
Applies ifYou route alerts or tasks to sellers by the CRM account owner, or agents answer coverage questions from that field.

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