◆ Salesforce

Test AuraHandledExceptions

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 taskWhen the customer support agent tries to close this case, make sure any errors thrown by the…+
When the customer support agent tries to close this case, make sure any errors thrown by the system are handled gracefully, so they don't see a scary red message. We need to keep the customer's experience smooth.
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 we push this new feature live for the support team, review the error handling. I need to…+
Before we push this new feature live for the support team, review the error handling. I need to know that if something goes wrong, the system provides a clear, user-friendly message instead of a technical error code. This will prevent calls to IT and keep agents focused on customers, especially on busy Mondays.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA new custom button on the account page is giving some users a generic error message, but not…+
A new custom button on the account page is sometimes failing for specific users, but not consistently.
A new custom button on the account page is giving some users a generic error message, but not all of them, and I can't replicate it reliably. This is holding up our end-of-quarter reporting, and the sales team is getting frustrated. I'm afraid of pushing a fix that breaks something else. What's the most likely cause for an intermittent, vague error like this, and what's the safest first step to diagnose it without impacting other users?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur support agents often get vague system errors that don't help them or the customer. This…+
Our support agents frequently report getting vague system errors that don't help them troubleshoot.
Our support agents often get vague system errors that don't help them or the customer. This leads to wasted time escalating issues and makes us look unprofessional. What habit can I change in how I design system interactions to ensure that when something goes wrong, the error message always provides actionable information or a clear path to resolution, improving agent efficiency and customer trust?
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.