CRM & sales ops21 categories
Audit these automations for conflicts
A CRM where several workflows have accumulated and something keeps overwriting a field.
Review the automations below and find where they collide. Look for: two automations writing the same field, loops where one triggers another, order-dependent results, rules that fire on every edit rather than on change, and anything still running for a process that no longer exists. For each problem: which automations are involved, what the user actually experiences, and the smallest safe fix. Rank by how much damage each is doing now, not by how untidy it is. Automations:
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.
Automation and admin. Workflows, validation, field design and the documentation nobody wrote at the time.
Related prompts
Design this HubSpot workflowAutomating something in HubSpot without discovering the edge cases in production.Write a Salesforce validation ruleStopping bad data at entry without blocking every legitimate edge case.Design the field before anyone creates itA request for a new CRM field, which is easy to add and very hard to remove.Write the lead routing rulesDeciding who gets which lead, including the cases nobody thought about.Define lifecycle stages that mean somethingWhen MQL and SQL are used differently by marketing and sales, and handovers keep failing.Document how this CRM is actually set upAn inherited CRM whose logic lives only in the head of someone who left.
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