What This Domain Tells You
Missing names, email addresses, company domains and record associations can interrupt routing, follow-up and reporting. Exact duplicate matches are candidates to review, not proof that two records should be merged.
Before You Assess
Review the suggested contact, company and deal mappings. The standard checks require a name or first name and email for contacts, a company name and domain for companies, and the relevant deal fields. Owners are assessed in Routing & SLA.
Checks In This Domain
Your results cover only the checks selected for the assessment and supported by its evidence.
| Check | What It Looks For |
|---|---|
| Required Information Is Present | Contacts require name/first name and email. Companies require name and domain. All deals require name, pipeline and stage; won deals also require amount and close date. |
| Recorded Values Are Valid | Validate populated email/domain formats, dropdown internal values and stage membership in pipeline. |
| Potential Duplicate Contacts | Group contacts by normalized exact email. |
| Potential Duplicate Companies | Group companies by normalized exact domain. |
| Required Relationships Are Present | Contact requires >=1 company; company >=1 contact; deal >=1 company AND >=1 contact. |
| Company Hierarchies Are Structurally Valid | Detect self-parenting, cycles and more than permitted direct parents. |
How To Use The Findings
Complete missing information and verify associations in the affected records. Review duplicate candidates before merging. A populated value can satisfy a presence check without proving that it is factually correct.
Read The Outcome Correctly
A confirmed issue means a stated requirement was not met. A review indicator needs business context. Unavailable evidence or history means the outcome could not be established; it is not an automatic failure. Read coverage alongside any score.