CRM & sales ops21 categories
Document how this CRM is actually set up
An inherited CRM whose logic lives only in the head of someone who left.
From the configuration below, write documentation a new admin could work from. Cover: the objects and how they relate, custom fields and what each is for, the automations and their triggers, the integrations and which direction data flows, and the parts where the intent is unclear from the configuration alone. Be explicit about what you are inferring versus what the configuration states. End with the questions to ask before changing anything. Configuration:
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.Audit these automations for conflictsA CRM where several workflows have accumulated and something keeps overwriting a field.
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