◆ Salesforce

Query records by insertion order 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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGet me the IDs of the top 20 accounts created last month, ordered from newest to oldest. I need…+
Get me the IDs of the top 20 accounts created last month, ordered from newest to oldest. I need this by Friday for the Q3 review.
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 query that shows me all accounts created in the last 90 days, ordered by creation…+
I need a query that shows me all accounts created in the last 90 days, ordered by creation date, with their primary contact's email. Make sure it's easy to adapt for different date ranges next quarter.
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 director just asked for a list of 'new' accounts, and I'm not sure if he means last…+
The sales director just asked for a list of new accounts, but I'm not sure if 'new' means last 30 days or last quarter, and I don't want to over-promise. He needs it before his meeting with the board.
The sales director just asked for a list of 'new' accounts, and I'm not sure if he means last 30 days or last quarter. I'm afraid of giving him the wrong data and looking unprepared before his board meeting. What's the best way to get a quick, accurate list that he'll find useful, without having to ask him directly and show my uncertainty?
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 losing time whenever a manager asks for a list of records based on their creation date,…+
I keep struggling to quickly pull specific lists of records based on when they were added, especially when the criteria shift slightly.
I keep losing time whenever a manager asks for a list of records based on their creation date, especially when the definition of 'new' changes. I need a better habit for quickly generating these time-sensitive lists without having to start from scratch every time or guess the exact date range. How can I get ahead of this recurring request?
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.