Library › Sales AI › Revenue operations
Turn a Slack request into a validation rule spec
- For Revenue operations
- You practice Asking for a format you can use
- Time about 5 minutes
- Level Beginner
About this exercise
Fill out a validation-rule spec from the Slack message as seven plain-text lines labeled exactly Object:, Rule name:, Fires when:, Blocks save if:, Error message:, Exceptions:, Open question:. Follow the naming convention. The error message is under 15 words and must not blame the user. If the request doesn't say, write "Not specified" for Exceptions. Under 100 words.
Common mistakes when you ask AI for this
- Ignoring the naming convention. The AI invents 'Close Date Required Rule'. Try: Add: "Rule name follows OBJ_Field_Description with OPP for Opportunity."
- Blaming error text. The AI writes 'You forgot to enter a valid Close Date'. Try: Add: "Error message under 15 words, neutral, no blame."
- Guessing exceptions. The AI invents exceptions like 'admins can bypass'. Try: Add: "Exceptions: Not specified, if the request doesn't say."
- Missing labels. The AI writes a paragraph or table. Try: Add: "Seven plain-text lines with exactly these labels."
What a strong prompt includes
- Lists the seven labels
- Follows the convention
- Neutral error
- Handles unknowns
- Plain text
Related exercises
- Accept the buyer's counteroffer on three stated conditions (Sales AI · Sales and customer success)
- Adapt one ad image to 3 sizes with Midjourney (Image & Video AI · Marketing and content)
- Age open requisitions as of today and flag the old ones (Finance AI · FP&A and financial analysts)
- Announce a discount-approval process change in three bullets (Sales AI · Managers and team leads)
- Announce a new regional structure with a reporting table (Leadership AI · Executives)