◆ Salesforce

Query records with 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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskFind all 'Opportunity' records where the 'Close Date' is in the next 30 days and the 'Stage' is…+
Find all 'Opportunity' records where the 'Close Date' is in the next 30 days and the 'Stage' is not 'Closed Won' or 'Closed Lost'. I need to see the 'Opportunity Name', 'Account Name', 'Amount', and 'Close Date' for each.
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 a list of all accounts where we have an open opportunity over $10,000, but haven't had…+
I need a list of all accounts where we have an open opportunity over $10,000, but haven't had any activity logged in the last 60 days. Prioritize accounts where the 'Account Owner' is currently 'John Smith' or 'Jane Doe'. This will help me identify at-risk deals for our weekly pipeline review.
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 VP just asked for a report on all opportunities stuck in 'Negotiation' for over 90 days,…+
Our VP of Sales just asked for a report on all opportunities that are 'Stuck' in the 'Negotiation' stage for more than 90 days.
The VP just asked for a report on all opportunities stuck in 'Negotiation' for over 90 days, and I'm not sure how to accurately define 'Stuck' beyond just the stage and date. Some might have legitimate reasons, others are truly stalled. I'm afraid of misrepresenting the pipeline and getting grilled in the next meeting. What's the best way to query this that gives a realistic picture of truly stalled deals?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly struggling to pull specific, nuanced data sets for ad-hoc requests from…+
I frequently struggle to pull specific, nuanced data sets for ad-hoc requests.
I'm constantly struggling to pull specific, nuanced data sets for ad-hoc requests from leadership, often missing critical details or taking too long. It makes me look slow and impacts my credibility. What habit should I change in how I approach these data requests, so I can quickly and accurately get the exact information needed without multiple revisions?
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.