◆ Salesforce

Query records using NOT LIKE

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskFind all accounts that do not have 'Consulting' in their industry…+
Find all accounts that do not have 'Consulting' in their industry field.
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 acceptGenerate a list of all active opportunities where the 'Product Family' is not 'Software' or…+
Generate a list of all active opportunities where the 'Product Family' is not 'Software' or 'Hardware', so we can review these for potential miscategorization before the quarterly report.
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'm trying to get a list of leads that are NOT from our target industries: 'Retail' or…+
I'm trying to filter out specific records, but the results aren't what I expect.
I'm trying to get a list of leads that are NOT from our target industries: 'Retail' or 'Manufacturing'. The list I'm getting still includes some of them, and I'm afraid I'm missing potential high-value leads by misfiltering. Is there a nuance to how I should exclude multiple terms, or am I thinking about the exclusion logic incorrectly? What's the most reliable way to get this clean list for the marketing team by end of day?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself spending too much time trying to get accurate record lists when I need to…+
I frequently struggle to accurately filter records when I need to exclude certain criteria.
I often find myself spending too much time trying to get accurate record lists when I need to exclude specific terms or categories, especially if there are multiple. This leads to inaccurate reports and wasted effort. What habit should I change to ensure I'm always using the most precise method for excluding records, avoiding ambiguity in my queries?
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.