◆ Salesforce

Manage reports and dashboards

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 taskUpdate the 'Q3 Pipeline Review' dashboard to include the new 'Enterprise Deals' report. Make…+
Update the 'Q3 Pipeline Review' dashboard to include the new 'Enterprise Deals' report. Make sure it refreshes hourly so the sales leadership team sees the most current numbers for their Monday meeting.
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 these Q3 sales figures to the board, refine the 'Regional Performance'…+
Before I present these Q3 sales figures to the board, refine the 'Regional Performance' dashboard. Highlight the top 3 and bottom 2 performing regions clearly, and add a trend line for the last four quarters so they can grasp the trajectory quickly.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just pulled the 'New Business Won' report for October, and the numbers are way lower than…+
I just pulled the 'New Business Won' report for October, and the numbers are way lower than what the team is reporting verbally.
I just pulled the 'New Business Won' report for October, and the numbers are way lower than what the team is reporting verbally. This isn't the first time. I'm afraid our forecast for next quarter is built on sand, and I'll look incompetent if I present these discrepancies without an explanation. What's the most likely reason for this gap, and how do I quickly verify the true number before Friday's leadership sync?
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 asked for custom reports that take days to build, pulling me away from proactive…+
I keep getting asked for custom reports that take days to build, pulling me away from proactive work.
I keep getting asked for custom reports that take days to build, pulling me away from proactive work. It feels like I'm always reacting to urgent data requests instead of building a robust reporting foundation. What habit should I change to anticipate these needs better and empower users to find answers themselves, reducing my bottleneck?
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.