◆ Salesforce

Create LWC component as global action

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 taskSet up a quick action for sales reps to log a call directly from any opportunity record. It…+
Set up a quick action for sales reps to log a call directly from any opportunity record. It needs to be ready by end of day 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 rolling out this new 'Log a Call' action, make sure it's intuitive. What fields should…+
Before rolling out this new 'Log a Call' action, make sure it's intuitive. What fields should be pre-populated, and what validations are needed so reps don't accidentally log calls for the wrong opportunity or leave out critical details?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe sales director wants a 'Log a Call' action for opportunities, but I'm stuck on whether it…+
The sales director is pushing for a 'Log a Call' action, but I'm not sure where it should appear for maximum impact.
The sales director wants a 'Log a Call' action for opportunities, but I'm stuck on whether it should be on the record page layout or a global action. Reps are complaining about too many clicks, and I'm afraid of adding more clutter. What's the best placement to ensure high adoption and quick logging, given their current workflow?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently struggle with getting sales reps to adopt new quick actions I build, even when…+
New quick actions often get low adoption or are hard to find.
I consistently struggle with getting sales reps to adopt new quick actions I build, even when they ask for them. They often say they can't find them or they're not useful. What habit should I change to ensure new actions are always placed and designed in a way that reps actually use them, saving me rework and frustration?
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.