Contact Governance and Page Design Patterns
Overview
This guide captures practical patterns for Contact data quality and Contact record page usability. It is grounded in implementation notes where teams needed both:
- cleaner contact data over time, and
- record pages users can update quickly without hunting for key fields.
Contact Data Governance Patterns
Pattern 1: Organization-Linked Contacts
- Avoid private contacts for shared business processes.
- Require account linkage by policy and validation where appropriate.
- Define exception handling for legitimate standalone-person use cases.
Pattern 2: Duplicate Defense
- Enable Salesforce duplicate management baseline (matching + duplicate rules).
- Add stronger matching tooling when duplicate volume is high.
- Track duplicate remediation as an operational metric, not one-time cleanup.
Pattern 3: Naming and Key Fields
- Use practical naming conventions and keep them stable once deployed.
- Add help text for user-facing fields.
- Include provenance fields such as
DataSource__cand data-cleansing markers where needed. - Keep API names stable even when business labels change.
Contact Page Design Patterns
Pattern 4: Action-Oriented Layout
- Place high-frequency edit fields in predictable locations.
- Keep Highlights Panel focused on high-signal fields.
- Avoid overloading top-of-page with decorative components.
- Keep related lists curated and role-relevant.
Pattern 5: Progressive Disclosure
- Show core details first.
- Move secondary analytics/charts/history to tabs.
- Use conditional components for role-specific needs.
Pattern 6: Dynamic Actions First
- Prefer Dynamic Actions over large legacy button sets.
- Keep critical actions visible; move rarely used actions into overflow.
- Align action ordering with user task flow.
UX Anti-Patterns
- Massive contact pages that optimize for demo visuals instead of data maintenance.
- Too many above-the-fold components competing for attention.
- Over-reliance on highlights panel for fields users frequently edit.
- Mixing every related list into one page with no prioritization.
Contact Configuration Checklist
- Duplicate and matching rules configured.
- Required contact/account linkage policy documented.
- Help text applied for user-facing custom fields.
- Contact list views and search layouts reviewed.
- Contact page action set minimized and ordered.
- Related lists prioritized by business process.
- Contact fields reviewed for role-specific visibility.
Sources Used
Knowledge/Jodie Miners/TDD-Contacts.md- Contact setup and governance notesKnowledge/Jodie Miners/TDD-The-Fancy-Contact-Page.md- Practical contact page design critiques and patternsKnowledge/Jodie Miners/TDD-Objects.md- Object and contact setup conventionsKnowledge/Jodie Miners/TDD-Rules-for-Fields.md- Field naming/help text conventions and caveats