◆ Salesforce

Turn off boxcarring for LWC imperative calls

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
See the prompt↓All Salesforce tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskInvoke the 'updateOpportunityStatus' Apex method with 'Opportunity ID' '006f4000004eRjP' and…+
Invoke the 'updateOpportunityStatus' Apex method with 'Opportunity ID' '006f4000004eRjP' and 'New Status' 'Closed Won'.
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 acceptI'm building a component that allows sales reps to quickly update multiple fields on an…+
I'm building a component that allows sales reps to quickly update multiple fields on an 'Opportunity' record. Before I deploy it, ensure that each update request for fields like 'Stage' or 'Amount' is processed individually by the server, rather than batched, so the reps get immediate feedback on each change and don't experience delays if one update fails.
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've deployed a new component for the sales team to update multiple 'Contact' records at once,…+
My component for bulk updates is performing slowly and sometimes failing without clear error messages.
I've deployed a new component for the sales team to update multiple 'Contact' records at once, but they're reporting it's very slow, and sometimes updates just don't stick without any error message. I suspect the platform is batching my imperative calls, which might be causing timeouts or silent failures. The sales manager is already asking why it's not working. What's the likely diagnosis, and what's the best next move to ensure each update is processed reliably and quickly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep running into situations where components that make several server calls feel sluggish or…+
I frequently encounter performance and reliability issues with components that make multiple server calls.
I keep running into situations where components that make several server calls feel sluggish or occasionally fail without clear reasons. It often feels like the platform is optimizing in a way that hurts my component's responsiveness or reliability. What habit should I change to better control how my components interact with the server, so I can build more predictable and performant user experiences?
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.