◆ Salesforce

Add validation rules to enforce data

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Salesforce tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSales reps are saving Opportunities without Close Date or Stage. Add a validation rule on…+
Sales reps are saving Opportunities without Close Date or Stage. Add a validation rule on Opportunity that blocks save when Stage is blank or Close Date is blank for any Stage beyond Prospecting. Return an inline error on the Stage field with message: Stage and Close Date are required for progressing the deal. Test as an AE and a Sales Ops user before enabling in production; schedule the rule to go live Monday morning.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore enforcing stricter saves on Opportunities, make approval easier for sellers. Draft a…+
Before enforcing stricter saves on Opportunities, make approval easier for sellers. Draft a validation rule that requires Stage and Close Date when Stage moves beyond Prospecting, but provide an exception for deals owned by Sales Ops or marked Internal. Surface the rule’s exact error message and list three scenarios that will trip it, so I can warn AEs and managers in the update email.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI enabled a validation rule to require Stage and Close Date and now several reps report they…+
I turned on a validation rule and reps can’t save Opportunity edits.
I enabled a validation rule to require Stage and Close Date and now several reps report they cannot save even small edits to won deals. The rule should have exempted Closed Won but apparently didn’t. I’m worried I’ve frozen essential updates and will anger leadership. What likely logic error caused this, which exact debug steps do I run now, and how do I revert the change safely while preserving data integrity?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEach release we push a validation rule that unexpectedly blocks a user workflow and produces a…+
Validation rules keep surprising users after releases.
Each release we push a validation rule that unexpectedly blocks a user workflow and produces a flood of support tickets. I need a process change to reduce these incidents. Which pre-deploy checks and stakeholder tests should become mandatory, who must sign off, and a simple rollback plan that avoids days of firefighting?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Salesforce's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.