CRM & sales ops21 categories
Write the data quality rules for this object
Deciding what "complete" means for a record, before arguing about it in a meeting.
Write data quality rules for the object and fields below. For each rule: the field, the condition, when it applies (creation, stage change, close), and the severity — block, warn, or report only. Be realistic about cost. A field required at creation slows every single entry; one required at a later stage usually gets filled properly. Say which of these rules would be resented and whether it is worth it anyway. Object and fields:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Data hygiene. Duplicates, inconsistent fields, messy imports, and records that technically exist but say nothing.
Related prompts
Find the duplicate accounts in this exportThe same company in the CRM three times, spelled three ways, with activity split across all of them.Map these columns to CRM fields before importingA spreadsheet from a trade show or an old system that has to land in the CRM without wrecking it.Which of these records are actually worth keepingThousands of contacts where most have a name, an email, and nothing else.Clean up this picklistAn industry or lead-source field with 60 values, half of them typos of the other half.Normalise these company namesA list to import where the same company appears as four different strings.Decide which value survives a mergeTwo records for the same company that disagree on half their fields.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free