◆ Salesforce

Check parent availability in Process Builder

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 taskWhen a new opportunity is created, check if its parent account has a 'Preferred Customer'…+
When a new opportunity is created, check if its parent account has a 'Preferred Customer' status before assigning the premium sales team.
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 assigning a new opportunity to the premium sales team, verify that its parent account…+
Before assigning a new opportunity to the premium sales team, verify that its parent account exists and actively holds 'Preferred Customer' status. If the account is inactive or missing, assign it to the standard team instead.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA new opportunity just got assigned to the premium sales team, but I found out the parent…+
A new opportunity was assigned to the premium sales team, but the parent account was actually deleted last week.
A new opportunity just got assigned to the premium sales team, but I found out the parent account was actually deleted last week. Now the premium team is confused, and the opportunity is in limbo. I'm afraid we're misallocating resources and losing track of potential deals. What happened, and how do we ensure we always check the parent account's status before making assignments?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe frequently see automations make incorrect assignments or trigger the wrong actions because…+
Our automations often make decisions based on parent record data that is missing or outdated.
We frequently see automations make incorrect assignments or trigger the wrong actions because they're relying on parent record data that's either missing, deleted, or outdated. This leads to wasted effort and bad data. What habit can we change in our automation design to reliably check the validity and status of parent records?
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.