◆ Salesforce

Negate compound condition in SOQL

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 taskWrite a SOQL query that returns all Contacts who are NOT associated with an Account named 'Acme…+
Write a SOQL query that returns all Contacts who are NOT associated with an Account named 'Acme Corp'.
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 acceptI need to get a list of all active opportunities that haven't been touched in the last 30 days…+
I need to get a list of all active opportunities that haven't been touched in the last 30 days AND are not in 'Closed Won' or 'Closed Lost' stages. Before I send this to the sales operations team, ensure it's easy to read and accurately captures only the truly stagnant opportunities for follow-up.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe sales manager needs a list of leads not contacted in 60 days, excluding 'Unqualified' or…+
The sales manager is asking for a list of leads that haven't been contacted in 60 days, excluding those marked as 'Unqualified' or 'Nurturing', but my query is too slow.
The sales manager needs a list of leads not contacted in 60 days, excluding 'Unqualified' or 'Nurturing', but my SOQL query is taking forever to run. I'm afraid I've got an inefficient subquery or a bad join. What's the most likely diagnosis for the slow performance, and what's the best next move to optimize this query without missing any leads?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep writing complex SOQL queries that are hard to debug or modify later, especially when…+
I keep writing complex SOQL queries that are hard to debug or modify later, especially when dealing with multiple exclusions.
I keep writing complex SOQL queries that are hard to debug or modify later, especially when dealing with multiple exclusions. This makes maintenance a nightmare and future changes risky. What habit should I change to structure my SOQL queries, particularly those with negated compound conditions, so they are clearer and easier to manage over time?
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.