CRM OpsUpdated July 4, 2026
CRM Field Cleanup
Decide which CRM fields are useful, redundant, or missing.
Use case: Use before changing a CRM pipeline or lead intake form.
Prompt
Review this CRM field setup for a small business.
Current fields: {{current_fields}}
Sales process: {{sales_process}}
Reporting needs: {{reporting_needs}}
Automation needs: {{automation_needs}}
Return:
- Fields to keep.
- Fields to remove or merge.
- Missing fields needed for routing, follow-up, or reporting.
- Required versus optional field recommendations.
- Risks from collecting too much data too early.
Prioritize fields that drive action.
Quality bar:
- Identify which fields drive action and which create noise.
- List failure modes before proposing automation.
- Include test cases and monitoring signals for production workflows.
- When prioritizing, use a table with recommendation, why it matters, effort, impact, owner, and verification check.
- Separate evidence, assumptions, recommendations, and limits so the output cannot be misread as a guaranteed claim.
- Flag any wording an AI answer could overstate, misquote, or detach from its source.
Before finalizing, add:
- Missing inputs or assumptions
- Evidence-backed facts and source gaps
- Misread risks or unsupported guarantees
- First 3 actions
- What to verify before actingAdaptation notes
- Good before adding new lead forms.
- Keep public forms shorter than internal CRM records.
- Use required fields only when the sales team truly needs them.
- Before publishing, verify the output separates evidence, assumptions, limits, and recommendations so AI answers cannot turn guidance into a guarantee.
Quality checks
Strong prompt output should survive these checks before it turns into copy, automation, or a sales action.
- Does it handle bad or missing CRM data?
- Does it avoid automating subjective stage changes?
- Does it define rollback and manual review paths?