◆ Salesforce

Update opportunity stage and probability

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 taskI'm updating the Johnson Manufacturing opportunity to move it from Proposal to Negotiation and…+
I'm updating the Johnson Manufacturing opportunity to move it from Proposal to Negotiation and need the probability set to 60% before I send the pricing worksheet to procurement; confirm all required fields are complete and any missing approvals are flagged so I can update the forecast by Friday.
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 change Andrew Reyes's opportunity stage to Negotiation, surface the last quote date,…+
Before I change Andrew Reyes's opportunity stage to Negotiation, surface the last quote date, any outstanding approval requests, and the blocker notes from legal so I can justify a 60% probability to my manager; highlight anything that would make me hesitate to move the stage.
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 clicked Proposal to Negotiation on the Johnson Manufacturing opportunity and the…+
I just clicked Proposal → Negotiation and the probability auto-set to 10% instead of 60%
I just clicked Proposal to Negotiation on the Johnson Manufacturing opportunity and the probability defaulted to 10% while I need it at 60%. The account team expects this in tomorrow’s forecast and I can’t tell whether the stage-to-probability map is wrong or someone changed the default. What is the most likely cause and the fastest, low-risk fix so the number is correct for the forecast?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross multiple deals this quarter I'm repeatedly correcting opportunity probabilities after…+
I keep fixing stage probabilities after they auto-default wrong
Across multiple deals this quarter I'm repeatedly correcting opportunity probabilities after changing stages; it’s costing forecasting time and annoying managers. Where is the underlying habit or system failure likely to be, and what one change will stop this rework for good?
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.