Placeholder and junk value flag in name fields (test, n/a, asdf)

Outcome. Contacts carrying obvious placeholder or junk values in their name fields ("test", "n/a", "asdf") get flagged for cleanup instead of showing up in sales collateral, exports, or reports as if they were real names.

Workflow map Enrollment, branches and actions at a glance data-quality-013

flowchart TD
    A[First or last name known or changed] --> B[Custom code: check against placeholder list and heuristics]
    B --> C{Junk detected?}
    C -->|yes| D[Flag: Junk detected]
    D --> E[Add to review list + create task]
    C -->|no| F[Flag: Clean]

When to use it, when not to

• UseUse it on portals fed by public forms, where testers, bots, and impatient form-fillers commonly leave junk in required name fields to get past validation.
• UseUse it as a periodic sanity check after a bulk import from a source with unknown data quality.
• SkipDo not use it expecting it to catch every kind of bad data. This workflow matches a known list of placeholder patterns and a few structural heuristics (repeated characters, keyboard-row strings); it will miss creative junk it was not built to recognize.
• SkipDo not use it to validate that a name is a real person's name (as opposed to a business name typed in the wrong field, for example). That is a different check, out of scope here.