◆ Salesforce

Build list view of open opportunities

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 taskBuild a list view that surfaces open opportunities for the west region. Create a list view…+
Build a list view that surfaces open opportunities for the west region. Create a list view named West — Open Opps showing Opportunity Name, Stage, Amount, Close Date, and Owner, filtered where Region equals West and Stage not equal Closed Lost and Stage not equal Closed Won. Make it visible to the West sales team and set default sort by Close Date ascending.
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 publish the West — Open Opps list, make it actionable: move Amount and Close Date to…+
Before I publish the West — Open Opps list, make it actionable: move Amount and Close Date to the left, add a filter shortcut for Stage equals Negotiation and Stage equals Proposal, and flag deals with Amount over $50,000. Also add an inline action link to open the latest quote so reps can update status 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 created West — Open Opps but it returns zero rows even though reps report active deals. I…+
List view shows zero rows for West
I created West — Open Opps but it returns zero rows even though reps report active deals. I think it's a region-mapping or owner-team filter problem and I'm unsure which filter broke. Reps need visibility by EOD. What's the likely cause and the fastest check to restore the list view for them?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery week reps ask me to create a new list view for slightly different slices of open…+
Reps ask for new list views weekly
Every week reps ask me to create a new list view for slightly different slices of open opportunities, and I end up with dozens that nobody standardizes. This fragments forecasting and wastes my time. What habit or governance rule should I introduce so reps use a small set of standardized, reusable views?
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.