Salesforce Flow and Automation Plan in Plain Language
Specify an automation before it is built.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a plain-language specification for a Salesforce automation that an administrator can build without guessing. The business need: [BUSINESS_NEED]. Objects and fields involved: [OBJECTS_AND_FIELDS]. When it should run (record created, field changed, scheduled): [TRIGGER]. Who is affected: [PEOPLE_AFFECTED]. What it must never do: [NEVER_RULES]. Prefer the simplest automation that meets the need and list alternatives you rejected. Write headings for purpose, trigger and entry conditions, decision logic as numbered if-then statements, actions in order, fields updated, notifications sent and to whom, error handling, how to avoid running twice or looping, volume expectations, test cases in a table (a normal case, an empty field, a bulk update, a user without permission), a sandbox testing plan, a deployment checklist [VERIFY], a rollback plan, and monitoring (who checks failures and how often). Mark any statement about order of execution, limits or automation types [VERIFY with the administrator]. Do not assume features in my edition that I have not mentioned.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.