◆ Salesforce

Audit field history and activity logs

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 taskAudit field history and activity logs for account 004928 (Harris Manufacturing) for the past 90…+
Audit field history and activity logs for account 004928 (Harris Manufacturing) for the past 90 days. Produce a concise list of who changed Opportunity Stage, Amount, and Close Date, include timestamps and the before-and-after values, and flag any activity that looks like a bulk update so I can bring it to legal by Thursday.
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 run the audit for the client, make the findings easy to act on — surface the biggest…+
Before I run the audit for the client, make the findings easy to act on — surface the biggest anomalies up front, show which user accounts account for most changes, summarize bulk edits versus single updates, and call out any changes that align with contract amendments so a reviewer can decide if escalation is needed.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentHarris Manufacturing called saying pipeline totals shifted since yesterday and their account…+
A client says their pipeline numbers changed overnight.
Harris Manufacturing called saying pipeline totals shifted since yesterday and their account exec, Malik, is upset. I pulled the activity logs and see many Stage changes after midnight across the account team. I don't know whether this was a bulk data cleanup, an integration job, or accidental edits. What's the most likely diagnosis and the fastest way to confirm the cause so I can tell Malik and leadership?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe repeatedly wake to unexpected field changes that erode trust with account teams and trigger…+
We keep chasing mysterious overnight data shifts.
We repeatedly wake to unexpected field changes that erode trust with account teams and trigger expensive audits. What one operational habit should we adopt to prevent silent overnight edits, who must own it, and what minimal monitoring or alert would catch most problematic changes before they damage relationships?
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.