◆ Salesforce

Solve common Salesforce problems

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 taskThe 'Sales Team Leaderboard' dashboard is showing incorrect figures for John Smith. Check his…+
The 'Sales Team Leaderboard' dashboard is showing incorrect figures for John Smith. Check his recent opportunities and ensure they are all linked to him, then refresh the dashboard so his numbers are accurate.
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 acceptOur sales reps are complaining about slow load times when opening opportunity records. Before I…+
Our sales reps are complaining about slow load times when opening opportunity records. Before I get a flood of support tickets, investigate the 'Opportunity' object. Identify any custom fields or related lists that are causing excessive queries and suggest ways to optimize them to speed up record access.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentSarah in sales just called, frantic because she can't log in and has a critical demo in 15…+
Sarah in sales just called, frantic because she can't log in and has a critical demo in 15 minutes.
Sarah in sales just called, frantic because she can't log in and has a critical demo in 15 minutes. She says she hasn't changed her password. I'm afraid she'll miss this demo, costing us a potential deal, and I don't know why her login is suddenly failing. What's the immediate action to get her back in, and what's the most likely cause I should check first to prevent this for other reps?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI spend too much time troubleshooting basic user issues like login problems or incorrect record…+
I spend too much time troubleshooting basic user issues like login problems or incorrect record visibility.
I spend too much time troubleshooting basic user issues like login problems or incorrect record visibility. It's distracting me from more complex projects and feels like I'm always putting out fires. What habit should I change to empower users to self-diagnose or resolve common issues, reducing my workload and improving their independence?
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.