Skip to main content

SC CRM Contact Data Hygiene Standard

Purpose​

Defines what a contact record in the Symphony Core sub-account must contain to be useful, and how to classify the ones that already exist. It is the record-level counterpart to the SC Lead Management Standard, which governs what happens to a contact once it is known to be a lead. This standard answers the question that comes first: what is this record?

Scope​

Covers: every contact in the Symphony Core GHL sub-account, whatever created it — the prospecting agent, inbound-call automation, form fills, manual entry, or a vendor snapshot.

Does not cover: client sub-accounts, opportunity and pipeline hygiene (see the GHL Prospecting Pipeline SOP), or suppression policy (see the SC Outbound Calling Compliance Standard and the TCPA SMS standard).


1. The one rule​

Every contact carries exactly one record-type: tag. Not zero, not two.

Everything else in this document follows from that. A record with no type cannot be safely included in a list, excluded from a campaign, or counted in a report, because nobody can say what it is.

The failure this prevents is concrete. Symphony Core's own clients live in the same sub-account as its cold prospects. Without a type on every record, "do not cold-call the clients" is a sentence in an onboarding document rather than a filter, and the SDR onboarding SOP says as much: it is a stated boundary, not an enforced one.


2. The six types​

The first three are the existing prospect / lead / client model from the Lead Management Standard — prospect until they respond, lead once they do, client once they sign. The other three name populations that model never covered but that exist in the data.

TagWhat it isOutreach
record-type:clientA signed engagement, or a person who works thereNever. Account management only
record-type:leadHas responded; a real conversation exists; being sold toSales conversation, not the cadence
record-type:prospectCold outbound, no conversation yetThe prospecting cadence
record-type:networkPersonal and professional network. BNI chapters, referral partners, peersNever. Relationship contact, not a sales target
record-type:internalSymphony Core team, test records, system addressesNever. Excluded from every count and every report
record-type:junkQuarantined. See §4Never. Excluded from every list

Precedence when a record fits more than one. Highest wins:

client  >  lead  >  prospect  >  network  >  internal  >  junk

A client who first arrived as a cold prospect is a client. A network contact who signed is a client. The type describes the relationship that exists now, not how the record was created.

2.1 Clients are identified by a human, never by string matching​

Check candidates against the client document kit manifest, which is the canonical client list, and have a person confirm each one.

Matching on company name or email domain is not sufficient and will fail in both directions. Client staff routinely use personal Gmail addresses, so domain matching under-finds. And organisation names collide — a "Rotary District" civic club is not the client "Rotary Ski and Sports".

Getting this wrong in the false-negative direction means cold-calling a paying client.


3. Completeness is judged against the type​

There is no single definition of a complete contact, and trying to write one is what makes hygiene feel impossible. A missing business name is fatal on a prospect and irrelevant on a spam caller.

TypeMust have
prospectA business name — Symphony Core sells to businesses, and a prospect without one cannot be qualified or researched — and at least one reachable channel
leadA person name — a conversation exists, so somebody had it — and at least one reachable channel
clientA person name and at least one reachable channel
networkA person name and at least one reachable channel
internalNothing
junkNothing

Reachable channel means a usable email address or a usable phone number. One is enough.

Two rules fall directly out of the table:

  • No name of any kind and no business name → junk, unless a human has typed it as client or lead. An unidentified record cannot be addressed, segmented or researched.
  • No email and no phone → junk, however complete the name is. A contact that cannot be contacted is not a contact.

A record that carries the right type but fails its completeness test is incomplete, not junk. Tag it with its type and fix it, or let it sit; do not quarantine it to make a number look better.


4. Quarantine, never delete​

Junk is tagged record-type:junk and removed from every smart list, workflow and campaign. It is not deleted.

Deletion looks tidier and costs more than it saves:

  • It is not reversible, and the judgement that a record was worthless is sometimes wrong.
  • A deleted record carries no memory of why it was removed, so the next import brings it straight back and someone re-litigates it.
  • The audit trail disappears, including the evidence that a number was flagged as spam.

Keep whatever tag recorded the evidence — a spam likely or equivalent marker is the reason, and it should survive alongside the type.

If the contact count itself becomes a billing or performance problem, purging quarantined records is a separate, deliberate decision with its own review. It is not part of hygiene.

4.1 Recorded exception: the 2026-09-29 deletion​

On 2026-09-29 the 338 records typed record-type:junk in the SC sub-account were deleted, not quarantined, by a deliberate decision during the account clean-up (issue #328). The count went from 817 contacts to 480. This was a one-time exception, and the rule above is unchanged. The consequences named above now apply to those records: they can't be restored from the CRM, the reason each was judged junk is gone with it, and so is the spam evidence. If one of those numbers calls again, it arrives as a new, untyped record, and it is typed again from scratch.

Any future purge is the separate decision described above, with its own review. It does not cite this exception as precedent.


5. Safety​

Three rules. None is optional, and the first two exist because of incidents already recorded.

Hygiene never changes suppression. DND flags, opt-outs and do-not-call markers are read-only to this work. Classifying a record must never resubscribe anyone. The GHL Sub-Account Structure Inventory §2 documents the DND findings and the records never to touch; the suppression-flag-downstream-check working rule requires enumerating what a contact becomes eligible for before clearing any suppression marker. Hygiene classifies. It does not re-enable.

Canary every bulk write. Apply the change to five records, read them back, confirm the result is what was intended, and only then run the rest. Bulk contact writes are the category where a wrong assumption becomes 800 wrong records in one call.

Never add a type by guessing. If a record cannot be typed from its own evidence, leave it untyped and route it to a human pass. An untyped record is visibly unfinished; a wrongly typed one is invisible and will be acted on.


6. Working an existing population​

The order matters, because each pass shrinks what the next has to look at.

  1. Type the unambiguous machine-readable cases first — records created by a known process, such as the prospecting agent, and records carrying an unmistakable marker such as an internal email domain or a spam flag.
  2. Type the clients, by human check against the manifest (§2.1).
  3. Apply the two junk rules from §3 to what remains.
  4. Route the rest to a human pass. Expect this to be a substantial minority. It is the real work and it does not automate.
  5. Verify the invariant: every record has exactly one type, and the type counts sum to the total.

7. What the current data looks like​

Baseline from the full export of 807 contacts, September 2026. Recorded so the next reader knows what "before" was; these numbers are a snapshot, not a target.

FindingCount
No person name and no business name283 (35%)
No business name617 (76%)
No email516 (64%)
Named, but no email and no phone60
No name, business, email or phone at all9
Internal and test records live in production16
Duplicate emails / duplicate phones1 / 0

Three things worth carrying forward:

Deduplication is not the problem. One duplicate email and no duplicate phones across 807 records. Neither is phone formatting: every number is already E.164.

Records made by a defined process are clean. All 104 prospecting-sourced records carry a business name. The mess is concentrated in records created by inbound-call automation, by a vendor snapshot, and by hand. That is the argument for classifying by origin rather than auditing field by field.

The largest single population was inbound-call residue — phone numbers with no name, generated by missed-call automation, a substantial share flagged as spam. Reviewed and judged to carry no value; typed junk, then deleted on 2026-09-29 under the §4.1 exception.



Document History​

VersionDateChanges
1.12026-10-09§4.1 records the 2026-09-29 deletion of 338 junk records as a one-time exception, so the standard and the account agree on what happened while the quarantine rule stands. §7 no longer says the inbound-call residue was quarantined
1.02026-09-26Initial version. The one-tag rule, the six record types and their precedence, completeness judged per type, quarantine-not-delete, the three safety rules, the ordered approach to an existing population, and the September 2026 baseline