The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Build an automation that moves any Opportunity at 'Proposal Sent' to a devoted pipeline stage and…
Execute — do the immediate task
+Build an automation that moves any Opportunity at 'Proposal Sent' to a devoted pipeline stage and notifies the AE. If the opportunity stalls for seven days without activity, change its stage to 'Stalled' and add a task titled 'Follow up on proposal' assigned to the owning salesperson. Test with Minh's deal first and confirm the task appears in his queue.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I automate stage moves for Proposal Sent, make the rule safe: list the exact fields that…
Improve — make it easier to accept
+Before I automate stage moves for Proposal Sent, make the rule safe: list the exact fields that should trigger the automation, show example edge cases (renewals, partner-influenced deals), and recommend a suppress rule for opportunities that already have a task in the last three days. Also propose the user-facing task text so AEs understand required next steps.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I turned on an automation to create follow-up tasks when an opportunity hits Proposal Sent but AEs…
Decide — diagnose the stuck moment
+I created a rule that sent tasks for every 'Proposal Sent' and AEs complained
I turned on an automation to create follow-up tasks when an opportunity hits Proposal Sent but AEs say they were flooded with duplicates. I'm worried the rule is too broad and will annoy reps. I don't know how many exceptions to add or how to detect existing active tasks. What's the most likely cause and the minimal change to stop duplicate tasks while preserving the safety net for stalled deals?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the last year we keep adding workflow automations and they start by helping then create noise:…
Become — change the pattern
+Our automations keep generating noisy, duplicate tasks
Over the last year we keep adding workflow automations and they start by helping then create noise: duplicate tasks, inaccurate stage moves, and rule conflicts. This wastes reps' time and reduces trust in automation. Which three habits should we stop and which three checks should we add before deploying new automation so rules stay useful and low-friction?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other CRM work people do in Salesforce.
Create custom fields on objectsCreate custom report for accountsCreate new opportunity from contactCreate onboarding tasks for new repsCreate or update price book entriesEdit page layouts for usersEmail contact from recordEnroll contact in nurture campaignEscalate case to support teamExport report data to CSV
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.