◆ Salesforce

Query custom object history 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 taskPull all changes made to the 'Annual Revenue' field on the 'Account' object for the past 90…+
Pull all changes made to the 'Annual Revenue' field on the 'Account' object for the past 90 days, showing the old value, new value, and who made the change.
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 I present to the board on Friday about our customer churn, give me a report that shows…+
Before I present to the board on Friday about our customer churn, give me a report that shows every change to the 'Status' field on the 'Opportunity' object for closed-lost opportunities in Q3, along with the 'Reason for Loss' and the user who updated it. I need to spot trends in how our deals are failing.
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 sales rep just told me they updated a deal's close date and amount, but I'm not seeing it…+
A sales rep just told me they updated a deal's close date and amount, but I'm not seeing it reflected in the pipeline report.
A sales rep just told me they updated a deal's close date and amount, but I'm not seeing it reflected in the pipeline report. I'm afraid the data isn't saving correctly or someone else overwrote it. I need to know exactly what changes were made to Opportunity 'OPP-2023-00123' on Tuesday and by whom, so I can figure out why the report is wrong and if I need to re-enter anything.
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 getting questions about who changed what and when on critical fields like 'Stage',…+
I keep getting questions about who changed what and when on critical fields, and it takes too long to dig through individual records.
I keep getting questions about who changed what and when on critical fields like 'Stage', 'Amount', and 'Close Date' on opportunities, and it takes too long to dig through individual records. This happens daily and delays our pipeline reviews. What habit should we change to quickly get an audit trail for these key fields across all opportunities without manually checking each one?
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.