◆ Salesforce

Qualify lead by updating status

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 have an unqualified lead, Javier Ramos at Summit Retail, who said pricing looks promising but…+
I have an unqualified lead, Javier Ramos at Summit Retail, who said pricing looks promising but budget is pending. Update his record: change status to Qualified — Needs Budget, set probability to 30 percent, add a note summarizing the budget timing (decision expected July 15), and set a follow-up task for me in ten days.
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 Javier Ramos’s status to Qualified, make the record easier to approve by…+
Before I change Javier Ramos’s status to Qualified, make the record easier to approve by procurement: surface the decision date and budget owner, make his estimated deal size and product interest visible, and flag any missing items that would make a reviewer hesitate to mark him Qualified.
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 updated Javier Ramos to Qualified — Needs Budget based on a call. The rep says the…+
I moved a lead to Qualified but the rep disagrees on timing and now finance is asking questions.
I just updated Javier Ramos to Qualified — Needs Budget based on a call. The rep says the budget owner wasn’t on the call and the timing may be two months out. I don’t know the true decision owner or the impact of classifying as Qualified. What’s the likely diagnosis and the best short next step so I don’t mislead pipeline reports?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery month we argue about whether a lead is Qualified and pipeline numbers swing. Where are we…+
We inconsistently qualify leads and pipeline accuracy suffers every month-end.
Every month we argue about whether a lead is Qualified and pipeline numbers swing. Where are we losing credibility and time in qualification, and what single habit change will make our lead-status decisions repeatable and defensible to finance? Recommend one concrete rule for status change plus how to enforce it quickly.
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.