◆ Salesforce

Set opportunity close date and amount

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 need the opportunity closed with the right number and day. Set the close date to June 30,…+
I need the opportunity closed with the right number and day. Set the close date to June 30, 2026 and the amount to $48,750 on the ACME Corp renewal opportunity, then save and leave a one-line note: "Updated close and amount per contract sent May 12." Confirm the record validates and the forecast category stayed the same before you finish.
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 lock the renewal amount and date on ACME Corp, make the key facts obvious to a…+
Before I lock the renewal amount and date on ACME Corp, make the key facts obvious to a reviewer: put the contract start and end dates and the original signed amount at the top, show the calculation that produced $48,750, and flag any discounts or pending legal approvals that would make a finance reviewer hesitate.
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 updated ACME Corp to close June 30, 2026 for $48,750 and saved, but I don't see the expected…+
I just changed the close date and amount but I'm not sure it mapped to the right forecast bucket
I updated ACME Corp to close June 30, 2026 for $48,750 and saved, but I don't see the expected booking in the forecast. I need to know whether the record failed validation, the opportunity record type moved buckets, or a required field is missing. What should I check first and what quick fixes are safe without breaking approvals?
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 I keep having to change close dates and amounts after finance rejects the…+
I keep correcting close dates and amounts after finance flags forecasts
Across multiple deals I keep having to change close dates and amounts after finance rejects the forecast. Where am I losing credibility: bad source documents, doing changes in the wrong field, or not validating with procurement? Recommend one habit to stop the back-and-forth and a single checklist item to run before I update any opportunity.
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.